Project Learning Centre

Choosing an Appropriate Project Management Methodology

What is PRINCE2 Agile ?

 

I recently was asked: “Which type of projects are better suited for Agile, Prince2, Waterfall & mix model? How do you determine that? What factors will you need to consider?”

 

Choosing the appropriate project management methodology depends on factors such as project size, complexity, requirements clarity, and the organisation's culture and project management processes and systems. Here's a breakdown of which types of projects are better suited for Agile, PRINCE2, Waterfall, and a mixed model, along with factors to consider when you decide on an appropriate methodology to use:

 

Agile                                                                                                                                                                                                                  

Suitable Projects:

 

Projects with evolving requirements

Projects that require frequent feedback and iterations

Software development

Small to medium-sized projects

 

Factors to Consider:

 

Flexibility: Need for adaptability to changing requirements.

Customer Involvement: High level of stakeholder engagement and feedback.

Team Collaboration: Strong emphasis on teamwork and self-organizing teams.

Time to Market: Quick delivery of functional increments.

 

PRINCE2

 

Suitable Projects:

 

Medium to large, complex projects

Projects with clear, well-defined requirements

Projects that require strong governance and control

Projects with a focus on risk management

 

Factors to Consider:

 

Structure: Need for a structured, process-driven approach.

Governance: Strong emphasis on project governance and control.

Risk Management: Comprehensive risk management practices.

Documentation: Detailed documentation and reporting.

 

Waterfall

 

Suitable Projects:

 

Construction and large engineering projects

Projects with clear, stable requirements

Projects with sequential phases

Projects where changes are costly and difficult to implement

 

Factors to Consider:

 

Stability: Requirements are well-defined and unlikely to change.

Sequential Phases: Project can be broken down into distinct, sequential phases.

Risk Management: Risk is managed through detailed planning and documentation.

Complexity: Projects with low to moderate complexity.

 

Mixed Model (Hybrid)

 

Suitable Projects:

 

Projects that require a combination of structured and flexible approaches

Large-scale projects with both stable and evolving requirements

Projects with multiple stakeholders with varying needs

Projects that require both agility and strong governance

 

Factors to Consider:

 

Complexity: Projects with a mix of stable and evolving requirements.

Stakeholder Needs: Diverse stakeholder needs requiring both flexibility and control.

Risk Management: Balanced approach to risk management.

Team Capabilities: Team's ability to adapt to different methodologies.

 

Determining the Appropriate Methodology

 

Project Size and Scope: Larger projects may benefit from structured methodologies like PRINCE2 or Waterfall, while smaller projects may be better suited for Agile.

 

Requirements Clarity: If requirements are clear and stable, Waterfall or PRINCE2 may be appropriate. If requirements are evolving, Agile is a better fit.

 

Stakeholder Involvement: Projects requiring frequent stakeholder feedback are better suited for Agile.

 

Risk Management: Projects with high risk may benefit from the structured risk management practices of PRINCE2.

 

Team Expertise: It is worthwhile considering your team's familiarity and comfort with the different methodologies.

Organisational Culture and Processes: Often you won’t have much of a choice at your organisation. They might have a fixed methodology you have to follow. 

 

Remember to tailor the rigour of the methodology to the size of the project !!

  

 

What is PRINCE2 Agile® 

 

PRINCE2 Agile® combines the flexibility and responsiveness of Agile with the clearly defined framework of PRINCE2. New best practice guidance shows how this compatibility can be exploited by organisations harnessing both PRINCE2 and Agile, equipping them with the required skills and processes to successfully deliver projects to meet customer requirements in today’s fast paced and rapidly changing business environments.

 

Combining flexibility with pragmatism, PRINCE2 Agile gives you the best of both worlds, allowing you to scale for complete control and good governance.

 

PRINCE2 Agile is a hybrid methodology that combines the structured, process-driven approach of PRINCE2 with the flexibility and iterative nature of Agile. It is best suited for projects that require a balance between governance and agility. Here are the types of projects where PRINCE2 Agile can be particularly effective:

 

Suitable Projects for PRINCE2 Agile

 

Complex Projects with Evolving Requirements:

Projects where requirements are not fully defined at the outset but need to be managed within a structured framework.

 

Large-Scale Projects:

Projects that are too large for pure Agile methods but still require the flexibility to adapt to changes.

 

Projects Requiring Strong Governance and Control:

Projects where stakeholders need assurance of control and governance, but also require the ability to adapt to changing circumstances.

 

Projects with Diverse Stakeholder Needs:

Projects with multiple stakeholders who have varying needs and expectations, requiring both structure and flexibility.

 

Projects with Both Stable and Evolving Components:

Projects that have some stable, well-defined components and other components that are more fluid and subject to change.

 

Projects with High Risk:

Projects where risk management is crucial, and a structured approach to risk is needed, but the project also requires the ability to pivot quickly.

 

Requirements Clarity:

If requirements are partially clear but subject to change, PRINCE2 Agile can provide the necessary structure while allowing for flexibility.

Stakeholder Involvement:

Projects requiring regular stakeholder feedback and involvement can benefit from the Agile aspects of PRINCE2 Agile.

 

Risk Management:

Projects with significant risks that need structured risk management practices but also require the ability to adapt quickly to new risks.

Team Capabilities:

Teams that are comfortable with both structured and flexible methodologies can effectively use PRINCE2 Agile.

 

Organisational Culture:

Organisations that value both governance and agility can benefit from PRINCE2 Agile, as it aligns with their existing processes and culture.

 

Example Scenarios

 

Software Development Projects: Where the overall project structure is defined, but individual features and requirements are subject to change based on user feedback.

 

Product Development: Where the product vision is clear, but the specifics of the product features need to be iteratively developed and refined.

 

Organizational Change Projects: Where the overall change strategy is defined, but the implementation details need to be flexible to adapt to organizational feedback and resistance.

 

By combining the strengths of PRINCE2 and Agile, PRINCE2 Agile offers a balanced approach that can be tailored to a wide range of projects, providing the structure needed for governance and the flexibility required for adaptation.

 

Note: PRINCE2 and PRINCE2 Agile methodologies are owned by PeopleCert International Ltd.