Methods for Technical Program Managers
Delivery methods are the frameworks a TPM uses to organise work: waterfall for fixed, sequential phases, agile approaches such as Scrum and Kanban for iterative delivery, and scaled variants like SAFe for many teams. A good TPM picks and blends methods to fit risk, uncertainty and team maturity instead of following one by the book.
Stage: Role and Foundations · Part of the Technical Program Manager roadmap · Last reviewed 19 November 2026
What to learn in Methods
- Compare waterfall, Scrum and Kanban and pick one for a given program
- Run sprint planning, review and retrospective events with a team
- Use WIP limits and flow metrics on a Kanban board
- Explain how scaled agile frameworks coordinate many teams
- Adapt a method when the team or program context changes
Methods interview questions
When is waterfall still a reasonable choice?
Waterfall suits work with stable, well-understood requirements and high cost of change, such as hardware builds, regulated deliveries or fixed-date migrations. Even then, many programs mix phases with iterative feedback inside each phase to reduce the risk of late surprises.
What is the difference between Scrum and Kanban?
Scrum works in fixed-length sprints with defined roles, events and a sprint goal. Kanban is a continuous flow system that visualises work, limits work in progress and measures cycle time, with no required cadence. Kanban suits support or operations work with unpredictable arrivals.
Where Methods fits in the Technical Program Manager roadmap
Methods belongs to the Role and Foundations stage (intermediate level), which takes about 24 hours. What a TPM does.
Other units in this stage
Back to the full Technical Program Manager roadmap