Transformation Program Design and Delivery: Agile vs. Waterfall
A logistics company is embarking on a transformation to digitize its order-to-cash process. The program includes process automation, a new customer portal, and integration with a transportation management system. The company has traditionally used waterfall methodology. The program leadership is considering an agile approach to accelerate delivery and improve stakeholder engagement. However, the organization has limited agile experience, and regulatory requirements demand thorough documentation. The program has a fixed budget and a 12-month timeline. The sponsor is risk-averse and wants predictability. What approach should the program leadership take?
1. What delivery approach should be recommended, and why?
Read the worked answer
A hybrid approach is recommended:
- Agile for development: Use agile for the customer portal and automation components where requirements may evolve and user feedback is valuable. This allows iterative development and faster delivery of usable features.
- Waterfall for regulatory documentation: Use waterfall or stage-gate for documentation and compliance aspects to ensure thoroughness and sign-off.
- Integration: Plan integration points carefully; use agile for TMS integration if vendor supports it, otherwise waterfall.
- Governance: Establish a governance model that accommodates both: stage gates for funding and compliance, and sprint reviews for development.
- Risk management: Address sponsor's risk aversion by providing transparency through regular demos and clear documentation; use a hybrid model to balance flexibility with predictability.
- Capability building: Provide agile training and coaching to build capability; start with a pilot to demonstrate success.
- Timeline and budget: Use agile to deliver high-priority features early, but maintain a fixed deadline by prioritizing scope; use a release plan that aligns with the 12-month timeline.
2. How should the program leadership manage stakeholder engagement and change in this hybrid environment?
Read the worked answer
Stakeholder engagement in hybrid:
- Identify stakeholders: Customers, internal users, regulators, IT, and operations.
- Communication: Regular updates through sprint demos for development progress and stage-gate reviews for compliance. Use a shared roadmap to show overall progress.
- Involvement: Engage users in sprint reviews to gather feedback; include regulatory stakeholders in documentation reviews.
- Change management: Develop a change management plan that addresses both agile and waterfall aspects; provide training on new processes and tools; use champions to support adoption.
- Transparency: Use visual management (e.g., kanban boards) to show progress and risks; ensure sponsor has visibility into both streams.
- Feedback loops: Establish mechanisms for continuous feedback and adjustment, while maintaining documentation for compliance.