Difference between revisions of "Behaviors"

From PRINCE2 Agile wiki
Jump to: navigation, search
m (Nader moved page Bahaviors to Behaviors)
 
Line 3: Line 3:
 
== Transparency ==
 
== Transparency ==
  
 +
Transparency creates opportunities for improvement both in the product, and in the way we work.
  
 
== Collaboration ==
 
== Collaboration ==
  
 +
Two types of collaboration is important in Agile:
 +
* Among team members, for improving the performance. The [https://en.wikipedia.org/wiki/Extreme_programming_practices#Collective_code_ownership 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 ==
 
== Rich Communication ==
(see also the [[Rich Communication]] focus area)
 
 
  
 +
Communication, like transparency, is important for enabling adaptation. See also the [[Rich Communication]] focus area.
  
 
== Self-Organization ==
 
== Self-Organization ==
  
(see also the [[Organization Theme]])
+
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]].
 
+
  
 
== Exploration ==
 
== Exploration ==
  
(represents the adaptation concept. see also the [[Agile]] article)
+
Represents the adaptation concept, where we allow the product to evolve through the project based on the feedback, instead of being created based on an upfront plan/design. See also the [[Agile]] article.
  
 
[[Category:Concepts]]
 
[[Category:Concepts]]

Latest revision as of 12:13, 24 August 2015

PRINCE2 Agile mentions a number of "behaviors" required for Agile environments.

Transparency

Transparency creates opportunities for improvement both in the product, and in the way we work.

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.

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.

Exploration

Represents the adaptation concept, where we allow the product to evolve through the project based on the feedback, instead of being created based on an upfront plan/design. See also the Agile article.