Difference between revisions of "Project Brief"

From PRINCE2 Agile wiki
Jump to: navigation, search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
== Tailoring ==
 +
 
The following should be considered in Agile environments:
 
The following should be considered in Agile environments:
 
* The project definition should be more outcome-oriented rather than output-oriented, since the output (product) will evolve throughout the project.
 
* The project definition should be more outcome-oriented rather than output-oriented, since the output (product) will evolve throughout the project.
Line 4: Line 6:
 
* The role descriptions should explain the Agile roles and responsibilities involved in the delivery level.
 
* The role descriptions should explain the Agile roles and responsibilities involved in the delivery level.
  
The suitability of Agile for the project should be assessed during the pre-project period, through the [[Starting up a Project Process]], using [[The Agilometer]]. The results will be captured in the Project Brief, and later one, elaborated and moved to the [[Project Initiation Documentation]] in the [[Initiating a Project Process]].
+
The suitability of Agile for the project should be assessed during the pre-project period, through the [[Starting up a Project]] Process, using [[The Agilometer]]. The results will be captured in the Project Brief, and later one, elaborated and moved to the [[Project Initiation Documentation]] in the [[Initiating a Project]] Process.
 +
 
 +
== Process Model ==
 +
 
 +
{{pmodel|20}}
  
 
== See Also ==
 
== See Also ==
* [[Starting up a Project Process]]
+
* [[Starting up a Project]] Process
 
* [[Output vs. Outcome vs. Benefit]]
 
* [[Output vs. Outcome vs. Benefit]]
  

Latest revision as of 03:17, 13 September 2015

Tailoring

The following should be considered in Agile environments:

  • The project definition should be more outcome-oriented rather than output-oriented, since the output (product) will evolve throughout the project.
  • The project approach should explain how Agility will be implemented in the project and what kind of Agile delivery method will be used.
  • The role descriptions should explain the Agile roles and responsibilities involved in the delivery level.

The suitability of Agile for the project should be assessed during the pre-project period, through the Starting up a Project Process, using The Agilometer. The results will be captured in the Project Brief, and later one, elaborated and moved to the Project Initiation Documentation in the Initiating a Project Process.

Process Model

PRINCE2 Agile Process Model state20.png

Legend:

Notes:

  • The above image assumes that Scrum is used in the delivery level, which is not necessary.
  • The number of stages, releases, and Sprints are just examples, as well as the exception in the third stage.
  • The diagram is schematic and many details are not shown.

See Also

External Links