A one-size-fits-all method has a certain appeal. Everyone learns the same templates, the same gates, the same vocabulary. The cost shows up later, when a three-week internal change carries the same paperwork as a multi-year infrastructure program. The alternative is tailoring: choosing the approach for each project based on what that project needs. It takes judgment, but you can structure it.

Assess the project first

Before choosing a lifecycle, understand the work. We look at six factors:

1. Uncertainty. How well do we know the requirements and the solution?
2. Regulatory needs. Are there external rules, audits, or approvals that dictate evidence and timing?
3. Team experience. Has this team worked together, and with this kind of work?
4. Stakeholder involvement. Can the people who understand the need take part regularly?
5. Size. How many people, teams, and vendors are involved?
6. Criticality. What happens if it goes wrong, and how costly is a mistake?

Questions a PMO can use

A project management office (PMO) can turn these factors into a short intake conversation. Ask the sponsor and project manager:

• What do we know for certain, and what will we only learn by building?
• Which dates and deliverables are fixed by someone outside the project?
• Who will review the work, and how often can they?
• What evidence will auditors or regulators expect?
• How experienced is the team with this approach?
• What is the cost of failure, and how soon would we see it?

Don’t score the answers like an exam. Use them to start a conversation, and record the conclusion in a sentence or two.

Then choose three things

The answers guide three decisions. First, the lifecycle: mostly predictive, mostly iterative, or a blend. High uncertainty and frequent stakeholder access point toward iterative work. Fixed scope and heavy regulation point toward predictive. Second, governance: how often you review, who approves, and how you report. Third, artifacts: which documents and records are worth their cost.

Consider a small team updating an internal reporting tool. Uncertainty is moderate, stakeholders are close, and the risk is low. A short backlog, a review every two weeks, and a one-page charter are enough. Now consider a payment system change for a lender. The regulatory needs and criticality are high, so the team documents more, adds formal approvals, and still builds in iterations where requirements remain open.

This differs from hybrid delivery within one program. Here the question is which approach each project deserves, whether or not the program mixes them.

Try the six questions on your next three projects and compare the choices you’d have made by default. If you want a ready intake template for your PMO, we can share what we use.