Any phase · Ways of working
Plan with fixed milestones and agile delivery
Many organisations need fixed dates and approval points, but teams still work in short cycles. Plan so both work together.
About 1-2 daysEvergreenLast reviewed 5 November 2026
Who this applies to
- Skills it builds
- Delivery and executionPrioritisation and roadmapping
- PM types
- All
- Product types
- All
- Starting points
- All
- Ways of working
- Hybrid / stage gates
- Experience
- All
- Size of organisation
- All
Steps, by experience
Beginner (under 1 year)
- List the fixed milestones and approval points, and what each needs.
- Plan the work in short cycles that lead to each milestone.
- Agree what is fixed, such as the date, and what can flex, such as scope.
- Show progress against milestones in a way leaders understand.
- Raise risks to milestones early.
Intermediate (1 to 4 years)
- Map milestones and their requirements.
- Plan short delivery cycles towards them.
- Agree what is fixed and what flexes.
Experienced (5+ years)
- Negotiate milestone criteria that reward outcomes, not documents.
- Bridge agile reporting and governance needs.
- Reduce unnecessary approval steps over time.
Who can do this
Owner: Product manager
Can be delegated to
- Delivery Manager: Build and maintain the plan
- Business Analyst: Prepare milestone documents
Reviewed by: Delivery Manager
Tool examples
- Jira
- Use versions or milestones linked to sprints.
- Azure DevOps
- Use delivery plans with milestone markers.
- SharePoint / Word
- Keep governance documents in one place.
Definition of done
- Milestones and requirements mapped
- Short cycles planned towards each
- Fixed and flexible elements agreed
Common pitfalls
- Waterfall disguised as sprints
- Fixing date, scope and quality all at once
- Late surprises at milestones