Behaviors
PRINCE2 Agile mentions a number of “behaviors” required for Agile environments:
- Transparency
- Collaboration
- Rich communication
- Self-organization
- Exploration
The first three are general behaviors expected in every project, but more emphasized in Agile. Self-organization, the way it’s defined in PRINCE2 Agile (as opposed to pure Scrum) is also applicable to every project. Exploration, the way it’s defined in this context, is the only concept that is specifically for Agile projects and their adaptive lifecycles. More information about it is available here: What is Agile?
Transparency
Transparency creates opportunities for improvement both in the product, and in the way we work, because Agile projects are highly dependent on generating feedback, and having transparency increases the reliability of the feedback.
Collaboration
Two types of collaboration is important in Agile:
- Among team members, for improving the performance. The Collective Code Ownership practice is an example of approaches that enables collaboration.
- Between the customer and the supplier, because adaptation is not possible without it. The customer should spend more time with the supplier, compared to a predictive project.
Rich Communication
Communication, like transparency, is important for enabling adaptation. See also the Rich Communication focus area to learn more about what PRINCE2 Agile considers important in this area.
Self-Organization
The team is self-organized when it finds its own way instead of receiving orders. A complete self-organization is not possible with a governance system that PRINCE2 brings to the project, but we still expect to have an empowered team that can decide on details. See also the Organization theme and the Manage by Exception principle.
Exploration
Exploration represents the adaptation concept, where we allow the product to evolve throughout the project based on the feedback, instead of being created based on an upfront plan/design. See also: What is Agile?
Written by Nader K. Rad
This is (and will be) a work in progress: More details will be added in the future, depending on the feedback.
This wiki is developed and managed by an accredited trainer, independent of AXELOS. While aligned with their guidelines, it’s not an official resource.