Lesson 04: The Agile Manifesto
Based on AXELOS PRINCE2 Agile® material. Reproduced under licence from AXELOS. All rights reserved.
PRINCE2® 6th edition update:
1. "Benefits Review Plan" is now called "Benefits Management Approach"
2. all "_____ Management Strategy"'s are now called "_____ Management Approach".
- The history of the Agile Manifesto
- A retake on the Agile Manifesto - A YouTube video of a few people talking over the manifesto, including two of the original contributors.
- Why Agile need customer collaboration more than predictive systems?
- We don’t need documentation in Agile. (True/False)
- What are the prerequisites of being Agile?
- Because we don’t define everything upfront, and therefore limited access to the customer at the beginning of the project is not enough. We’re specifying and testing the features all the time, and it’s impossible without customer collaboration.
- We still have many forms of documentation in Agile. We don’t use it for certain purposes such as creating a mutual understanding between the customer and the supplier.
- You can answer such a question from multiple perspectives. This is how I see it: we need to have…
- an Agile development team, with enthusiastic people who know how to work in Agile environments, and
- an Agile performing organization, in which the senior managers support their Agile teams (e.g. by empowering them), and
- an Agile customer, who accepts the consequences of Agility (e.g. no upfront documentation, no fixed-price/fixed-scope contract, etc.)
Here you can submit your questions related to the content of the course. (For other questions, use the support system). The trainer's reply will be email to you in 48 hours.
This lesson is part of the first 30% of the course, which is available for free, even without registration.
You can purchase the course to access all lessons, additional material, and coaching:
More info and purchase options