PM Essence

Agile Methodology & Sports – Event Management in FIFA World Cup-2010

By - Shikha Vaidh, PMP
What/ Why is AGILE? Agile is an iterative and incremental mode of development wherein the entire development life cycle is broken down into small iterations. It involves continuous participation of the customer during the development phase. This approach allows the development team to moderate the effects of any kind of requirements or design refinement while the code evolves.

While Waterfall model has a plan driven philosophy, the Agile model is vision driven philosophy at its core as shown in given figure. While you do not get to do much research in Agile, what you do get is to see your work in action sooner.

Interaction Model

Mahindra Satyam provided IT services for the duration of the FIFA World Cup Football in 2010, and was the first Indian company to do so. Mahindra and the host country (South Africa) actively interacted with with the product owner. Product owner was the ‘body’ responsible for providing services to FIFA.The different modules that formed the deliverables were

• EMS - Event Management System
• ACR - Accreditation System
• SMP - Space and Material Planning
• VSM - Volunteers & Staff Management System
• GTS - Ground Transportation System

The system was used in its first major event Prelim-Draw on 25th Nov 2007 with EMS Core and ACR module, followed by FIFA confederation cup in Jun 2009 in Johannesburg, drawing of match fixture in Dec 2009 and the final world cup event in Jun-Jul 2010. The criticality of the system was in the fact that the events dates were rigidly fixed. Hence ‘ACR’ had to be delivered for Prelim draw, ‘VSM had to be delivered for Confederation cup and ‘GTS had to be delivered for the final draw and complete system had to be delivered for the final event. The 3 years of development period saw the planning for 50 Iterations which included 3000+ user stories. Sprint (Release) Duration was 1 month 15 days, ‘Release’ ends with ‘Gap week’ and scoping for the next release starts during the ‘Gap week’.

Iteration Duration: 2 weeks per Iteration

• Release Estimation done based on shirt sizing
• Shirt sizing parameters include (S, M, L, XL)
• Estimate reviews with customer for scoping a release.

Communication Model
• Module-wise daily scrums for tracking progress of work between offshore application leads and onsite customer application leads.
• Common scrums included status updates on open production support issues.
• Weekly status meetings with customer project manager and relevant stake holders.
• Monthly Steering Committee meetings with all stake holders.

Lessons Learnt
• Agile is better suited for Projects of this nature with a multiyear span
• Regression Testing in Agile projects has to be planned carefully.
• Effective planning, team motivation, proactive identification and mitigation of potential risks enable the team to deliver the modules effectively.