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.
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.
where ONLY what is involved is currently listed - that ISN'T the syntax I used after this...
•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
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
Also with 'everything' listed but only relevant items mapped. This way you also see what IS NOT involved.
but your real-world governance activities would benefit from one. Create?