ipm2015 | day 0 | expa talk
Post on 16-Jul-2015
3.194 Views
Preview:
TRANSCRIPT
EXPA Talk :D
Let’s be on the same page!
EXPA Talk :D FLOW • Objectives • History • Current
State • Next Steps
EXPA Talk :D FLOW • Objectives • History • Current
State • Next Steps
Objectives
4
1. Understand the evolu2on of the project
2. Have clarity on the current state
3. Be on the same page about next steps
4. Give inputs for next steps OBJECTIVES
EXPA Talk :D FLOW • Objectives • History • Current
State • Next Steps
EXPA Talk :D FLOW • Objectives • History • Current
State • Next Steps
History
7 HISTORY
12-13
Process Optimization
Project Need to open our
opportunities Need to have a new information
system Development of OP
13-14
GIS
Dreaming about new features
Selection of the vendor
Beginning of system
development Evolution of the Customer Flow
14-15
Business Model Evolution
Impact of the Customer Flow
(OP, FIN, HR, Brand) Expectations
Setting towards the System Vendor
Relationship Improvement
History
8 HISTORY
GIS Customer
Flow Business
Model LDM, CF, S&S, FIN, HR
Learnings!!
Some Facts…
9 HISTORY
1. Why was the system launched without the big ideal plaQorm being there?
• Set clear expecta2ons with the network in the beginning of our term
• Had issues with Project Management from RDC • Changes happened in transi2on and start of our
term
• Contract with TCS+TCL had a termina2on date • Financial decision making of the investment
considered the new system running in 2015
Some Facts…
10 HISTORY
2. Why wasn’t financial investment considered before?
• Urgent needs from the project itself (stability and improvement)
• Time for a new developer to start working (keeping the system improvement in mind
• Main need would be if the waves of development need to be faster
EXPA Talk :D FLOW • Objectives • History • Current
State • Next Steps
EXPA Talk :D FLOW • Objectives • History • Current
State • Next Steps
Current State
13
1. System stable since early December
-‐ No down2me
2. Bugs connected to data migra2on
3. Analy2cs under feedback
-‐ Data since EXPA launch are accurate for People and Opportuni2es
-‐ Issues with migra2on is the reason for inaccurate data before EXPA launch
CURRENT STATE
Current State
14
5. Changes in the AIESEC – RDC coopera2on
-‐ New project manager, more consistent communica2on principles -‐ Project management & tracking tool – JIRA -‐ Frequent visits to London >> working on new func2ons specifica2on
6. Timeline of the second wave defined -‐ No2fica2ons -‐ TMP OP -‐ Analy2cs
CURRENT STATE
EXPA Support
15 CURRENT STATE
Team Structure
Description Response Time Gloal
Current Average Response Time
No. of tickets/month
Level 1 Frequently asked questions, known bugs and EXPA doubts
36 hours 31.2 hours 505
Level 2 Further investigation and confirmation of bugs
48 hours after assignment
36.5 hours 143
Level 3 Reporting bugs and follow up with developers
72 hours after assignment
25.3 hours 65
Developer GST
16 CURRENT STATE
Current Projects : • Live AFT (March 7th) • LinkedIn XML Feed (Feb 16th) • CRM App for EP & TN Managers (March 31st)
AI Developments
17 CURRENT STATE
Current Projects : • System NoLficaLons (32 types) – 6 done • System KPI Dashboard
• File MigraLon
• CorrecLng Invalid MyAiesec.net Data
• MigraLon Tracker – Done
• NewsleUer emailing system – Done
• Customized OP Invite Emails for MCs – Done
• Live AFT Database Update System
Development Process
18 CURRENT STATE
What is AGILE?
• Development is split into sprints that last 2-‐3 weeks • It is very feedback driven and adaptable to change • Changes can be implemented in a very short as the feedback and communicaLon loops are very short
IT AUDITOR Comments
19 CURRENT STATE
We are using newest possible technologies available right now. This is very positive.
EXPA, as any other IT product, has common bugs. The task is, find them sooner, then user does.
EXPA system itself is designed very well, UX is on high level with great product vision. With every coming month, I believe, it’s going to gain power and increase efficiency of our organisation.
EXPA is not a good system, it’s superior AIESEC platform!
Based on our meetings with the IT Auditor • System is using cutting edge technologies • Data security is well managed inside the system • Open API has huge growth potential
EXPA Talk :D FLOW • Objectives • History • Current
State • Next Steps
EXPA Talk :D FLOW • Objectives • History • Current
State • Next Steps
Next Steps – OUR GOALS UNTIL THE END OF THE TERM
22
Priority: Features acceleraLng & automaLng the process unLl match 1. Sending NPS surveys, basic NPS analy2cs 2. LDM assessment (par2ally dependent on IM) 3. First version of matchability 4. No2fica2ons & reminders 5. CRM & Shortlis2ng func2on improvements 6. OP improvements 7. Conversion analy2cs 8. TMP OP, very basic TMP analy2cs 9. User tes2ng & design improvements 10. Basics of internal communica2ons *Based on the progress of C-‐OP project, we will need to evaluate further integrate of the C-‐OP into EXPA. This will also take Eme.
CURRENT STATE
Development Resource Allocation
23 CURRENT STATE
Bug Fixing!20%!
Improvements!
30%!
New Featur
es!50%!
Estimated Timeline
24 CURRENT STATE
Constant CRM
+ Sho
rtlis2n
g Men
u + OP Im
provem
ents
top related