Agile Network India - Ahmedabad Title :Reaching the Podium by Robins Abraham Date: Feb 2024 Hosted by: Lucent Innovation

1. 𝓡𝓮𝓪𝓬𝓱𝓲𝓷𝓰 𝓽𝓱𝓮 𝓟𝓸𝓭𝓲𝓾𝓶
Agility in Project Management :
Navigating Change and Enhancing Delivery

2. If the project is going exactly as planned, you are in deep trouble

3. The Background
• MLE decides to rollout “Common Platform “ for 11 countries.
• MLE is using an international team to select the best technologies
from vendors around the world and deploy those technologies as
the global standard.
• Instead of having a hodgepodge of systems in each country—or
U.S.-mandated systems everywhere—Portals from respective
countries and its underwriting system from the U.S., and it built a
data center in Asia
• 25% customization of the global platform in different countries

4. The Background
• Decision to implement the system one country at a time
• Minor customization to account for Country’s different languages,
regulations and currency.
• Each country has its own legal, compliance, insurance, data laws
• Multiple vendors
• Multiple locations, time zone and languages

5. Reality check
• Culture
• Work culture
• Climate
• Food
• People
• Communication
• Time zone
• Language
• Different agenda
• Competitions

6. Project Management is common sense and common sense is very RARE

7. Problem statement
• After 40% of elapsed time
• Requirement was not captured
• Development was at halt.
• Teams were deployed.
• Budget wont be increased.
• Date wont be changed.
• Politically critical project
• Brand at stake

8. Problem statement
• Requirement inflow
• Unstructured or
• Different structure
• Different language.
• Perspectives
• Pile of information
• Print + forms + Hand written + Soft copies
• Incomplete requirement
• Development without proper requirement
• Testing mess , bugs
• Lot of patch work

9. Project Status

10. Root cause
• No Governance
• Non involvement of sponsors
• Body Shopping behaviors of vendors
• Vendor(s) discord
• Communications
• Complex architecture

12. Its not agile , its agility that matters.

13. Simplicity—the art of maximizing the amount
of work not done—is essential

14. How we used this principle
• Mark Incomplete % and person responsible and age of the task.
• Publish the report daily
• Incentivization of team and members
• Vendor progress to Sponsors
• Formed support group
• Added agents in team *

15. • Defect / issue injection phases
• Mapping requirements dependencies
• Involvement of end users and agents ( part of team)
• Improved governance.
• Incentivization
Focus area
Software
Development
Customer
Management

16. Out come
05
04
03
02
01
Least bugs
Reusable Library / Faster
development
Phase wise Signoff
Reduced Backlog
Launched on date Live on
national TV with first policy

17. 𝓡𝓮𝓪𝓬𝓱𝓲𝓷𝓰 𝓽𝓱𝓮 𝓟𝓸𝓭𝓲𝓾𝓶

18. thanks!