What is AgilePM?

AgilePM (Agile Project Management) is a flexible project management methodology that combines an agile approach with proven traditional project management practices. The methodology was developed to enable organizations to deliver projects effectively in a dynamic business environment while maintaining control and structure. For IT companies managing complex projects with evolving requirements, AgilePM provides a structured framework that ensures both flexibility and governance.

Definition of the AgilePM Methodology

AgilePM is a project management framework that builds on the principles of agile software development but extends them to a broader project management context. The methodology emphasizes flexibility, collaboration, and iterative value delivery while providing a solid foundation for project control and risk management.

Unlike pure development methods such as Scrum, AgilePM offers a complete project management framework that also covers governance, business analysis, and stakeholder management. This makes AgilePM particularly suitable for larger projects and organizations with formal requirements for project steering.

History and Development of AgilePM

AgilePM traces its roots to the Dynamic Systems Development Method (DSDM), which emerged in the 1990s as a response to the need for a more flexible approach to software development. DSDM was one of the first agile frameworks and was developed in parallel with the Agile Manifesto.

Key milestones in its development:

• 1994: Founding of the DSDM Consortium
• 1995: Publication of the first DSDM version
• 2003: DSDM Atern released as a revised version
• 2010: The DSDM Consortium (now the Agile Business Consortium) published the AgilePM Handbook, formally introducing AgilePM as a standalone project management methodology
• 2014: AgilePM updated with improved focus on business agility
• Today: AgilePM is used in thousands of organizations worldwide, with over 100,000 certified practitioners

Eight Core Principles of AgilePM

AgilePM is built on eight fundamental principles that serve as guardrails for all project decisions:

1. Focus on the business need: Every decision must be aligned with business value
2. Deliver on time: Meeting deadlines is a high priority; scope is adjusted rather than timelines
3. Collaborate: Close, continuous cooperation among all participants
4. Never compromise quality: Quality standards are never lowered in favor of speed or scope
5. Build incrementally from firm foundations: A stable foundational architecture is established early
6. Develop iteratively: Continuous improvement through feedback loops
7. Communicate continuously and clearly: Open information flow at all levels
8. Demonstrate control: Progress is made visible and actively managed

These principles distinguish AgilePM from other agile approaches by explicitly addressing governance and business value.

Structure and Processes of AgilePM

Project Lifecycle

AgilePM defines a structured project lifecycle with seven phases:

Phase	Description	Key Deliverable
Pre-Project	Evaluate and approve the project idea	Draft Business Case
Feasibility	Assess feasibility	Feasibility Assessment
Foundations	Establish solid foundations	Prioritized Requirements List (PRL)
Exploration	Investigate and develop functionality	Evolving Solution
Engineering	Make the solution production-ready	Deployable Solution
Deployment	Deliver and deploy the solution	Deployed Solution
Post-Project	Measure benefits and capture learnings	Benefits Assessment

Timeboxing

A key element of AgilePM is the concept of timeboxes — fixed time periods (typically 2-6 weeks) during which the team delivers a defined set of functionality. Unlike Scrum sprints, AgilePM timeboxes are explicitly divided into three phases:

• Investigation: Understand and detail requirements
• Refinement: Develop and test the solution
• Consolidation: Ensure quality and assess outcomes

MoSCoW Prioritization

AgilePM uses the MoSCoW method for prioritizing requirements:

• Must have: Essential requirements (maximum 60% of planned effort)
• Should have: Important but not critical requirements
• Could have: Desirable features
• Won’t have this time: Consciously deferred requirements

This approach is critical because it explicitly builds contingency into the project plan. If the team encounters unexpected complexity, “Could have” and “Should have” items can be dropped without compromising the core delivery.

Key Roles in AgilePM

AgilePM defines clearly delineated project roles with specific responsibilities:

Business Roles

• Business Sponsor: Responsible for budget and strategic direction
• Business Visionary: Defines the product vision and communicates business value
• Business Ambassador: Represents end users in the project team (full-time commitment)
• Business Advisor: Provides domain expertise as needed

Management Roles

• Project Manager: Coordinates the project and ensures governance
• Technical Coordinator: Responsible for the technical integrity of the solution

Delivery Roles

• Team Leader: Leads the development team within timeboxes
• Solution Developer: Develops and tests the solution
• Solution Tester: Responsible for quality assurance

Benefits of Implementing AgilePM

Adopting AgilePM can bring significant advantages to organizations:

• Increased flexibility: Rapid adaptation to changing requirements through iterative development
• Better control: Regular checkpoints and clear governance structures
• Higher stakeholder satisfaction: Continuous involvement and early, regular deliveries
• Reduced project risk: Early detection of issues through iterative approach
• Faster time-to-market: Usable results are delivered early and regularly
• Predictability: Through timeboxing and MoSCoW prioritization, schedules remain reliable

Research from the Agile Business Consortium shows that organizations using AgilePM achieve up to 36% higher project success rates compared to purely traditional methods.

AgilePM Compared to Other Methodologies

Aspect	AgilePM	Scrum	PRINCE2	Kanban
Scope	Entire project	Development process	Entire project	Workflow
Governance	Strong	Minimal	Very strong	None
Roles	9 defined roles	3 roles	7 roles	No fixed roles
Prioritization	MoSCoW	Product Backlog	Business Case	Pull system
Iterations	Timeboxes	Sprints	Phases	Continuous
Certification	Foundation & Practitioner	PSM, CSM	Foundation & Practitioner	Various

AgilePM can be combined with PRINCE2, which has been formalized as PRINCE2 Agile. This combination provides PRINCE2’s governance with the flexibility of agile methods, making it particularly attractive for regulated industries and government projects.

Challenges of AgilePM Implementation

• Cultural change: AgilePM requires a culture of collaboration and transparency that can be difficult to establish in hierarchical organizations
• Staff training: All project participants must understand and be able to apply the methodology
• Resistance to change: Employees accustomed to traditional methods may resist the transition
• Role availability: The Business Ambassador role in particular requires a full-time commitment from the business side, which organizations often struggle to provide
• Integration: Embedding AgilePM into existing organizational processes and PMO structures can be complex
• Certification costs: Foundation and Practitioner certifications require investment in training and examinations

Best Practices for Applying AgilePM

• Secure management commitment: Without leadership support, agile transformations will fail
• Invest in training: Certified AgilePM practitioners form the backbone of successful projects
• Start small: Begin with a pilot project before rolling out the methodology across the organization
• Ensure business engagement: Active participation from business representatives is not optional
• Use retrospectives: Regular reflection and adaptation of working methods
• Configure tools appropriately: Set up project management tools for AgilePM processes (Jira, Azure DevOps, MS Project)
• Define metrics: Establish clear KPIs for project success, quality, and stakeholder satisfaction
• Combine with complementary practices: Integrate Scrum ceremonies at the team level while using AgilePM for project-level governance

AgilePM Certification Path

The Agile Business Consortium offers a structured certification program:

• AgilePM Foundation: Covers the core principles, lifecycle, and techniques (1-day course, multiple-choice exam)
• AgilePM Practitioner: Advanced application of AgilePM in real-world scenarios (2-day course, scenario-based exam)
• AgilePM Portfolio and Programme Management: Extension to portfolio-level agile management

Certifications are recognized globally and are particularly valued in the UK, Europe, and Australia. They complement other certifications like PMP, PRINCE2, and Scrum Master.

AgilePM in the IT Consulting Context

For IT consulting firms and staff augmentation projects, AgilePM offers particular advantages. The clear role definitions facilitate the integration of external specialists into project teams. MoSCoW prioritization creates transparency around delivery expectations, and timeboxing provides a predictable framework for collaboration.

ARDURA Consulting supports organizations by providing experienced AgilePM practitioners and project managers. Our experts bring deep experience in applying agile methods and help deliver projects successfully while maintaining appropriate governance and control.