Philosophy and Fundamentals

From AgilePM wiki
Revision as of 10:19, 14 December 2016 by Frank (talk | contribs) (Understanding Project Variables)

Jump to: navigation, search


AgilePM adheres is a very simple philosophy and that is: “the best business value emerges when projects are aligned to clear business goals, deliver frequently and involve the collaboration of motivated and empowered people.”

There is a lot in statement: It says that the most value comes for the organization when • Projects are aligned to clear business goals (company strategy) • Project deliver frequently (deliver products often during projects) • And the correct people are engage and motivated in the project

This philosophy will work when all project stakeholders: • Are aware, understand and buy into the business vision and objectives • Are empowered to make decisions within their area of expertise • Collaborate to deliver fit for purpose products • Collaborate to deliver to agreed timescales in accordance with business priorities

A stakeholder is any person who is affected by the project.

The AgilePM approach is supported by a set of eight. The principles are supported by people (with defined roles and responsibilities), an Agile process, clearly defined document products and recommended practices.

Understanding Project Variables

Projects have to balance conflicting demands, and the main common demands are: time, cost, features and quality. Trying to fix all four at the start of a project is unrealistic but many projects still try. This may work in a perfect world where the requirements never changes.

This desire to offer everything is the cause of many project failures as people get excited about offering as much functionally as possible.


In the traditional approach to managing a project, the features content of the solution is fixed whilst time and cost are subject to variation. So if the project goes off track, more resources are often added which increases the cost and extends the delivery date. In many cases, adding new resources to a late project often makes it even and makes it worse for the project. And in such late projects quality is often affected as testing is rushed.


The AgilePM approach fixes time, cost and quality and features is flexible. So if the project is going over time or budget the lower priority requirements are dropped or deferred. Also notice that quality is also fixed, so you can be sure the features deliver will function as expected.

Therefore an AgilePM project will always deliver a viable solution, on time and on cost (on budget), as long as prioritization of features and time-boxing are followed. The delivery of a Minimum Usable Subset (minimal useable product) of requirements is guaranteed as a worst case scenario.

The quality requirements are included for each feature in the form of acceptance criteria. This make it easy for the delivery team to know when they have done what they needed to do and can move on to the next product. There is no need to add extra functionality that will is not required or will not be used. This is often referred to as gold plating.

The more important requirements are built to the agreed level of quality and after this has been achieved can development start on the less important requirements.

DSDM Delivers the Right Solution at the Right Time Delivery at the right time The AgilePM approach ensures solutions are delivered at the right time by breaking the project down into focused, fixed duration Project Increments, and within these into one or more timeboxes also of fixed duration and lasting typically, two to four weeks. It is agreed from the start that if necessary the lower priority items will be dropped so the timebox can complete as agreed.

Delivering the right solution The AgilePM approach delivers the right solution to the business because: • The project team and other significant stakeholders are focused on the business needs • The project team work collaboratively to achieve the outcome • Knowledge, experience and creativity of teams is allowed to work together • Work is prioritized according to business need • An iterative and incremental approach to development • Quality is fixed and is never allowed to become a variable


  • Agile is an adaptive way working or another style of working
  • Agile world consists of: frameworks, tools, practices and techniques.
  • AgilePM fixes Time, Cost and Quality at the early phases of a project
  • AgilePM does not fix Features, so if they are running out time, so of the less important features are dropped
  • This enables AgilePM to ship regularly and maintain quality.