This is the end of section_26’s coverage of directing a project

Next section_27 covers how the official manual introduces the notion of agile contracts. We have 1 lesson there.

Agile Events and Artefacts mapped to PRINCE2 Processes and Information sets.

This Revision Aid covers CS, SB and CP. SU and IP are covered in Ss7 ra65-68, MP is covered by Ss16 ra126 and DP is not given a mapping by the official manual (although clearly every Event is decision making based on artefacts and DP is the home of decisions).

Alongside the mapping of Events to Activities and Artefacts to Information Sets is the 'Journey' or approximate steps with linked techniques and tool-sets. These are covered in Ss33 ra224 for all 7 prince processes.

An 'impromptu exercise' is to create a matrix of everything p2 on one axis, everything agile on the other and the nature of the intersection in the cells created.

Post your best to the disqus forum.

First CS

where ONLY what is involved is currently listed - that ISN'T the syntax I used after this...

CS Activities

•CS1 [ Authorize a Work Package [ 15.4.1 ]
•CS2 [ Review Work Package status [ 15.4.2 ]
•CS3 [ Receive completed Work Packages [ 15.4.3 ]
•CS4 [ Review the stage status [ 15.4.4 ]
•CS5 [ Set up the project controls [ 14.4.5 ]
•CS6 [ Capture and examine issues and risks [ 15.4.6 ]
•CS7 [ Escalate issues and risks [ 15.4.7 ]
•CS8 [ Take corrective action [ 15.4.8 ]

•Daily impediments CS8

Next SB

Where all the agile events and artefacts are listed but only those that intersect with SB have SB entries. If (When?) you create a matrix consolidate ALL the activities of all the processes with all the artefacts and events - The list below can be expanded depending on point of view Eg SPM-What/ SPM-How

SB Activities

• SB1 [ Plan the next stage [ 17.4.1 ]
• SB2 [ Update the Project Plan [ 17.4.2 ]
• SB3 [ Update the Business Case [ 17.4.3 ]
• SB4 [ Report stage end [ 17.4.4 ]
• SB5 [ Produce an Exception Plan [ 17.4.5 ]

SB Activities and prince management information sets mapped to agile artefacts and events

• Release planning = SB1, SB2, SB4, SB5
• Release review = SB1, SB2, SB3, SB4
• Release retrospective = SB1, SB4
• Sprint planning = (maybe) SB1, SB5
• Daily Stand-up =
• Sprint review =
• Sprint demo =
• User acceptance =
• Release Demo =
• Sprint retrospective =

• Product backlog status = SB1, SB2, SB4, SB5
• Product backlog value = SB3, SB4
• Release backlog status = SB1, SB2, SB4, SB5
• Release backlog value = SB3, SB4
• Shippable increment = SB1
• Information radiators = SB2, SB3, SB4
• Release backlog =
• Sprint backlog =
• Sprint backlog status =
• Burn charts =
• Impediments = SB5
  • Daily impediments
• •User story acceptance criteria =
• Outputs & decisions from retrospective & reviews = SB5

Next CP

Also with 'everything' listed but only relevant items mapped. This way you also see what IS NOT involved.

• Activities
  
  • CP1 [ Prepare planned closure [ 18.4.1 ]
  • CP2 [ Prepare premature closure [ 18.4.2 ]
  • CP3 [ Hand over products [ 18.4.3 ]
  • CP4 [ Evaluate the project [ 18.4.4 ]
  • CP5 [ Recommend project closure [ 18.4.5 ]
• •Events
  
  • Release planning =
  • Release review = CP1, CP2, CP3, CP4-final
  • Release retrospective = CP1, CP2, CP-Project
  • Sprint planning =
  • Daily Stand-up =
  • Sprint review =
  • Sprint demo =
  • User acceptance =
  • Release Demo =
  • Sprint retrospective =
• •Artefacts
  
  • Project vision = CP1, CP2, CP4
  • Product backlog status = CP1, CP2, CP3, CP4, CP5
  • Product backlog value = CP3, CP4, CP5
  • Release backlog status = CP1 final, CP2, CP4
  • Release backlog value = CP4
  • Shippable increment = CP1, CP2, CP3
  • Information radiators = CP1, CP2, CP4
  • Release backlog =
  • Sprint backlog =
  • Sprint backlog status =
  • Burn charts =
  • Impediments = CP2 outstanding
    • Daily impediments
  • User story acceptance criteria =
  • Outputs & decisions from retrospective & reviews = CP5

Recall DP is not given a mapping in the manual

but your real-world governance activities would benefit from one. Create?