3.4 P2 Agile Guidance for process (4)

Question 1

Explain the P2 Agile guidance for the process ‘Starting up a project’

Answer 1

P2 sees upfront work as important and Agile can see it as not. Agile needs to be assessed for it’s suitability here using the Agilometer.

Question 2

Explain the P2 Agile guidance for the process ‘Starting up a project’

Answer 2

P2 sees upfront work as important and Agile does not. Use of Agile needs to be carefully assessed here using the Agilometer.

Question 3

Explain the P2 Agile guidance for the process ‘Initiating a project’

Answer 3

Same as ‘starting up a project’

Question 4

Explain the P2 Agile guidance for the process ‘Directing a project’

Answer 4

Use ‘management by exception’ to ensure whole team is empowered and self-organized. Decision making more based on info pulled out rather than formal reporting

Question 5

Explain the P2 Agile guidance for the process ‘Controlling a stage’

Answer 5

Stages are timeboxes, with sprints. Next work order based on SME (PO). Work packages, backlogs and retrospectives.

Question 6

Explain the P2 Agile guidance for the process ‘Managing product delivery’

Answer 6

Managing the interface between Project Management and Product Delivery. Work package at the centre - defined by PM + Team manager.

Question 7

Explain the P2 Agile guidance for the process ‘Managing a Stage Boundary’

Answer 7

Fire-breaks to compare what is happening outside. Review what’s been delivered v planned. Are the benefits being realised?

Question 8

Explain the P2 Agile guidance for the process ‘Closing a project’

Answer 8

Would have already been started due to frequent releases. Finalise documentation and training.