EXPA project
EXPA project PROJECT/SUBTEAM BOTTOMLINE 1.Finish the building & execute the implementation of a new information system which enables us to be fast & efficient to achieve 2015 2. Implement a new customer flow which makes us able to automate our processes where human interaction can be lowered.
PEOPLE INVOLVED Gabi. Main responsible for CFs implementation, network & RDC communication, etc Mike. Main responsible for system development. Emre GIP features, matchability, profile fields. Younes. GCDP features, matchability, sign up, network comm support. Anasof. TMP-TLP features. Mila. Network communications. Gianca. Marketing perspective, network communications. Orion. BD features. AIESEC International Q4 2014 Report
efforts GENERAL COMMENT In the begining of Quarter 4 we spent a lot of time on development specifications, after the launch our focus turned more into network communications, RDC communications and firefighting
INDIVIDUAL EFFORTS GP RDC comm (35%) Network communication (35%), CF mgmt&summit (15%) SOGA&AI report (5%) General AI todos – team mgmt, ST etc (10%) MKV RDC mgmt + bug fixing and development tracking (30%) Development (15%) Myaiesec.net and TCL/TCS backups (5%) TCS management (10%) GST and Zendesk mgmt (15%) AI team support (15%) General AI to dos (10%) Emre ~35% of his time (estimate) Younes. ~50% of his time (estimate) Anasof. ~30% of her time (estimate Mila. ~20% of his time (estimate). Gianca. ~40% of his time (estimate). Orion. ~10% of his time (estimate. For the people invoved in the project apart from the IM team the main efforts were already listed in the previous
slide so the number refers to an estimate of how much the person spent on the Massive project from his/her overall time
OUTCOMES Q4 MILESTONES CHECK myaiesec.net is shut down
Operations are running fully on the new GIS
The network’s operation’s are based on the new customer flow
All data in our posession (from TCS, TCL, CG)) All security activities connected to the shut down happened)
Migration is still causing issues for normal usage Analytics fulling working is still needed
On a basic level all the network understoon but there needs to be more effort to implement the customer flow summit out put and financial changes
MAIN KPIs MONITORING KPI Name
Planned
Achieved
my@net switched off
Y
Y
Users in the system
-
47k
weekly
weekly
Frequency of network comm.
AIESEC International Q4 2014 Report
% delayed
Challenges we Faced •
• • • • • •
• •
Launch date needed to be changed from 22nd of October to 6th of November due to § Challenges in the migration methodology § Late changes requested in the specifications § Delay in the development timeline On the day of the launch (6th of November) we needed to delay the launch time (1 day) due to § Migration challenges The system became stable 6 hours after the launch In November we had 3 downtimes of the system (no downtime since 26th of November) Bugs stopping (or causing huge problems) to exchange operation flow were handled with highest priority and resolved in a maximum of 3 days Analytics menu and migration completion was hugely delayed Communication and project management methodology with Rockstar was improved in the course of December with § Project management tool started to be used (JIRA) § New project manager assigned to the project The above mentioned point resulted in huge improvements in the communication flow with RDC During December due to the huge number of tickets the support GST was heavily overloaded § Solution: New GSTs selected, 2 level structure implemented, Slack communication implemented
AIESEC International Q4 2014 Report