5. Scope, planning and scheduling
Scope, planning and scheduling are critical enablers of successful project delivery, providing the structure and foresight needed to manage complexity, align resources, and meet strategic objectives. Effective planning ensures that project scope, timelines, dependencies, and risks are clearly defined and actively managed, while robust scheduling supports informed decision-making and timely execution. Strategic oversight of planning and scheduling is fundamental to ensuring that planning activities are realistic, aligned with strategic priorities, adequately resourced, and projects are set up for success.
This includes specifically the role of the SRO in championing early and ongoing planning efforts, fostering cross-agency coordination where relevant, and ensuring that key milestones, dependencies, and risks are visible and actively managed. A well-structured schedule is more than a delivery tool, it is a leadership instrument that drives informed decisions, proactive risk management, and sustained momentum. By embedding planning discipline into the project’s strategic framework, SROs can help mitigate delivery risks, support informed decision-making, and maintain alignment with delivery objectives.
For delivery teams, effective planning and scheduling require a balance of structure and flexibility, underpinned by clear assumptions, accurate estimates, and continuous monitoring. Challenges often emerge, particularly on complex multi-year transformations, when planning is treated as a one-off activity rather than a dynamic process. They also arise where schedules are developed in isolation from delivery realities where inadequate contingency planning or misaligned resource availability leads to slippage. In complex or fast-paced delivery environments, maintaining a living schedule that reflects actual progress and evolving priorities is essential to sustaining momentum and delivering value incrementally.
Key lessons
Delivery complexity
The amount of work involved to integrate a solution with other systems and processes was often underestimated. Integration is often more complex and uncertain than it first appears. Realistic scheduling depended on validating timeframes and resource estimates for integration, via consultation with technical experts, legal advisers and business owners.
Related actionable insights:
1 - Focus on strategic leadership | 2 - Manage replanning and slippage | 3 - Plan in stages | 5 - Enable interdisciplinary planning | 6 - Understand end user needs
Dependency management
Dependencies and interdependencies needed to be identified and sequenced from the start. Building them into the schedule supported active monitoring and management throughout delivery.
Real life learning
A large, multi-year program was initially structured for delivery as a loosely coupled portfolio of projects. As delivery progressed, it became clear that the work was highly connected and interdependent, and the agency took on the role of sole system integrator. The full complexity of system integration only became apparent after major vendor contracts had been issued and key technology choices had been made.
The team had to reflect on the program design and the relative merits of a consolidated “big program” approach, rather than dispersing projects across existing delivery teams. This highlighted the importance of early, detailed options analysis and deliberate consideration of program integration in program design, including the potential impacts on delivery structure.
Related actionable insights:
3 - Plan in stages | 5 - Enable interdisciplinary planning | 6 - Understand end user needs
Delivery flexibility
Embedding flexibility in schedules, release strategies and resourcing improved responsiveness to change. Acceptable contingencies in resource and time estimates helped teams respond effectively to changes in scope, demand or dependencies without losing delivery momentum. This could include buffers for critical milestones, surge capacity, contracts that allow resources to scale up or down, and contingency plans for key risks.
“Need to be able to look at the plan and the dynamic elements within that plan and see ‘if there’s a holdup in this area of the design and delivery, what other activities could I be doing at this time that would allow me to move forward?”
Related actionable insights:
2 - Manage replanning and slippage | 3 - Plan in stages | 4 - Run a pilot phase
Delivery planning
Thorough planning before the project start supported more effective and achievable delivery. Proper consideration to design, requirements, stakeholder input and effort estimates helped make milestones more achievable, manage risks and set up delivery for success.
Real life learning
A multi-year program adopted a tranched delivery approach to procurement as an effective means to limit up-front commitment, increase flexibility and provide on and off ramps. This delivered early wins, demonstrated the ability to deliver and supported confidence for future investment.
However, feedback indicated that Tranche 1 could have placed greater focus on business simplification, product planning, requirements gathering, design and procurement processes to better prepare the agency for upcoming platform builds. As a result, a substantial portion of the Tranche 2 schedule was consumed by these preconditions before build could commence, and that time was not recovered.
The experience highlighted that while tranching can increase flexibility and provide early proof of delivery, it requires careful sequencing of work across tranches so critical preconditions are addressed early. It also raised the question of whether a more consolidated program approach would have been more effective.
Related actionable insights:
3 - Plan in stages | 4 - Run a pilot phase | 5 - Enable interdisciplinary planning | 6 - Understand end user needs
Actionable insights
Stay strategic.
The SRO’s role is to lead, not manage at a detailed level. Rely on project manager (or director), the project management office and scheduling specialists for planning mechanics, but ensure their outputs support your strategic responsibilities. Avoid getting drawn too deeply into delivery detail, as this can dilute leadership focus and create bottlenecks.“Don’t take too much ownership of planning and scheduling – you’ve got experts in PMO and scheduling, get them in.”
Practitioner perspectiveDistinguish between replanning and slippage.
Not all changes to delivery timeframes are equal. Be clear about whether you are genuinely replanning based on new information or simply allowing the schedule to drift. This helps maintain control and credibility.“It’s important to distinguish what’s genuine planning rather than things just slipping to the right.”
Practitioner perspectiveDefine scope and schedule in staged increments.
Maintain a clear long-term vision, but break work into stages with defined timeframes, dependencies, and tangible outputs. This makes planning more realistic, supports sequencing of work, and helps maintain visibility of progress against the plan.“As you’re developing the timeframes and interdependencies be clear about ‘what’s the product we’re producing at various stages along the way?’"
Practitioner perspective- Include a proof-of-concept or a pilot phase in your delivery plan.
Use it to test functionality early, gather feedback and refine the solution before incremental or full rollout. This helps reduce risk and improve the user experience. Enable interdisciplinary planning.
Bring together project managers, architects and product managers to co-design delivery plans. Each brings critical insight into dependencies, feasibility and sequencing.“You can’t just ask a project manager ‘how long it will take to do this’ – you really need an interdisciplinary activity."
Practitioner perspective- Build a clear understanding of end use cases and critical business outputs.
This will improve planning, prioritisation, scheduling and dependency management.