Difference between revisions of "Project Brief"

From PRINCE2 Agile wiki
Jump to: navigation, search
Line 4: Line 4:
 
* 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.
  
 
== See Also ==
 
== See Also ==

Revision as of 05:11, 11 September 2015

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.

See Also

External Links