A practical reflection on moving from traditional stage-gated delivery toward Agile and MVP thinking without throwing away the controls that make enterprise change sustainable.
Process map
Business CaseWhy / value
investment
investment
PlanScope / risks
dependencies
dependencies
DesignRequirements
architecture
architecture
BuildIterate
configure / develop
configure / develop
ValidateQA / UAT / OAT
security
security
MVP / ReleaseSmallest useful
outcome
outcome
HypercareStabilise
learn / fix
learn / fix
BAUOwnership
improve
improve
Traditional project management still has value
- Business cases, decision gates, plans, RAID logs, budgets and clear accountability remain useful where risk, dependency and organisational coordination are high.
- The problem is not structure; it is when structure becomes a substitute for feedback and learning.
What Agile changed
- Shorter feedback loops make it easier to test assumptions before a full solution is locked in.
- Backlogs, iterative delivery and regular demonstrations improve transparency when they are tied to business outcomes rather than activity.
What MVP changed
- MVP thinking asks what is the smallest usable outcome that proves value or enables the next decision.
- It helps challenge 'everything is critical' requirements and reduces the risk of spending months perfecting low-value scope.
What should not disappear
- Security, architecture, data quality, testing, change management, documentation, cutover planning, support readiness and BAU ownership do not become optional because a team is Agile.
- The delivery model should be proportionate to the risk and complexity of the change.
A pragmatic hybrid
- Use enough governance to make decisions and risks visible.
- Use iteration to learn early.
- Use MVP to focus investment.
- Use formal validation and operational transition where failure would materially affect customers, staff or the organisation.
Key lessons
- Methodology is a tool, not an identity.
- Agile should increase transparency, not remove accountability.
- MVP means smallest valuable outcome, not lowest quality.
- Enterprise delivery still needs a clear path from business case to BAU.