The Agile Transition Dilemma
You are managing a large IT project in a traditional waterfall organization. The project is to develop a customer portal with a fixed deadline of 12 months and a budget of 3M EUR. After six months, the requirements have changed significantly due to new market demands. The steering committee suggests adopting agile practices to accommodate changes. However, the organization’s governance framework requires detailed upfront planning, stage-gate approvals, and formal documentation. The team is unfamiliar with agile, and the PMO is skeptical. You have a team of 15 developers, a business analyst, and a quality assurance lead. The sponsor is open to agile but concerned about losing control. The customer is demanding faster delivery of features.
1. Evaluate the feasibility of transitioning to agile mid-project. What governance and organizational changes would be necessary, and how would you manage the transition?
Read the worked answer
Feasibility: Possible but challenging due to fixed deadline, budget, and existing governance. A hybrid approach may be more suitable. Necessary changes: 1) Adapt governance to allow iterative delivery and flexible scope within budget and time constraints. 2) Establish a product owner role and prioritize backlog. 3) Introduce sprint cycles with reviews and retrospectives. 4) Negotiate with PMO to accept lighter documentation and stage-gate reviews at milestone levels. 5) Train team on agile principles and practices. 6) Define clear metrics for progress and quality. Transition management: 1) Communicate vision and benefits to stakeholders. 2) Start with a pilot sprint to demonstrate value and address concerns. 3) Gradually shift governance through pilot results. 4) Maintain transparency with steering committee through regular demos. 5) Address resistance through involvement and education.
2. The PMO insists on full compliance with the existing governance framework, which conflicts with agile principles. How do you resolve this conflict while ensuring project success?
Read the worked answer
Engage the PMO early to understand their concerns and explain the benefits of agile for this project (e.g., faster response to change, reduced risk). Propose a tailored governance model that satisfies essential control points: 1) Keep stage gates at major milestones but allow iterative development within stages. 2) Provide concise documentation focusing on value and decisions rather than exhaustive detail. 3) Use agile metrics (burn-down, velocity) to give visibility. 4) Offer to include PMO representatives in sprint reviews. 5) Escalate to sponsor if PMO remains inflexible, presenting a risk analysis of rigid governance on project outcomes. The goal is to balance control and flexibility, demonstrating competence in governance and stakeholder management.