Tailoring Guidance For The Prince2 Products

Question 1

In Prince2 what are the 3 types of management product?

Answer 1

• Baseline
• Record
• Report

Question 2

In Prince2 list the Baseline Management Products

Answer 2

• Benefits Management Approach
• Business Case
• Change Control Approach
• Communication Management Approach
• Plan (Project, Stage & Team)
• Product Description
• Project Brief
• Product Initiation Documentation
• Project Product Description
• Quality Management Approach
• Risk Management Approach
• Work Package

Question 3

In Prince2Agile list the Management Record Products to be tailored.

Answer 3

• Configuration Item Record
• Daily Log
• Issue Register
• Lessons Log
• Quality Register
• Risk Register

Question 4

In Prince2Agile list the Management Report Products to be tailored.

Answer 4

• Checkpoint Report
• End Project Report
• End Stage Report
• Exception Report
• Highlight Report
• Issue Report
• Lessons Report
• Project Status Account

Question 5

How is the baseline management product “Benefits Management Approach” tailored for P2Agile,?

Answer 5

• Emphasis on how frequent release planning enables benefits
- May lead to early customer benefits
- Impact on on-going project viability
- Many benefits may be planned to be in effect before end date

Question 6

How is the baseline management product “Business Case” tailored for P2Agile,?

Answer 6

• Expressed in a way to allow Flexing on amount of deliverables
• MVP identified to allow raising of an exception if forecasted to be delivered late

Question 7

How is the baseline management product “Change Control Approach” tailored for P2Agile,?

Answer 7

• Nature of Agile means many versions of products created
- Therefore needs to embraced and supported
- Use of frequent releases and associated tools defined

• Consider project/management changes may affect baseline. But detailed changes may not.

Question 8

How is the baseline management product “Communication Management Approach” tailored for P2Agile,?

Answer 8

• Vital that Agile methods understood
(Informal interactions, daily stand-ups, prototyping, workshops etc)
• Appicable to all project levels
• Define approaches like how a sprint review takes place, and delivery team/PM communication via checkpoint reports

Question 9

How is the baseline management product “Plan” tailored for P2Agile,?

Answer 9

• Agile plans more informal/low tech
• Although more formality higher up in project levels of planning
• Possibly a creation of release plans
• Agile plans likely to show product features in order, their order, their dependencies for delivery team

Question 10

How is the baseline management product “Product Description” tailored for P2Agile,?

Answer 10

• Used interchangeably with User Stories/EPICs.
- Although Prod Des may contain more info.
• Can be product backlog items
- Describing who/what/why?
• Format could be an index card/document

Question 11

How is the baseline management product “Project Brief” tailored for P2Agile,?

Answer 11

• Informal format
• Project definition is more outcome- based than solution-based
• Outline areas of scope and quality criteria that have flexibility for prioritisation
• Describe use of Agile and its benefit
• Detail Agile delivery roles
• Impact on incremental delivery on operations and maintenance

Question 12

How is the baseline management product “Product Initiation Document” tailored for P2Agile,?

Answer 12

• Should be created with the view of “ enough and no more”. Concise and at appropriate level of detail
• May exist on an information radiator

Question 13

How is the baseline management product “Project Product Description” be tailored for P2Agile,?

Answer 13

• Focus on defining the Product with a close link to a desired outcome
• As part of a workshop
• Purpose clearly visible to all
• Defines ultimate output and outcome
• The composition will contain highest level of Product descriptions and respective priorities

Question 14

How is the baseline management product “Quality Management Approach” tailored for P2Agile,?

Answer 14

• Agile needs to be incorporated into the strategy to ensure quality
• De-scoping is not a reduction in quality
• The quality may start out to be low due to the work uncertainty
  
  • Early adopters would be the intended audience more interested in utlilizing the product than deficiencies.

Question 15

How is the baseline management product “Risk Management Approach” tailored for P2Agile,?

Answer 15

-An Agile risk assessment is used. Emphasis on Agile behaviour risks
- Everyone looks out for risks

Question 16

How is the baseline management product “Work Package” tailored for P2Agile,?

Answer 16

• Interface carried out in an collaborative way
• Negotiated between the PM, TM and possibly the delivery team as well
• 1+ maybe collaboratively defined as the output from a sprint planning meeting
• CSME may help with prioritising
• May include 1+ releases & sprints

Question 17

How is the Record management product “Configuration Item Record” tailored for P2Agile,?

Answer 17

• Cater for high levels of change as common with Agile
• Operational stakeholders may want to be involved

Question 18

How is the Record management product “Daily Log” tailored for P2Agile,?

Answer 18

• PM to use this to store information especially informal communications (face-to-face)

Question 19

How is the Record management product “Issue Register” tailored for P2Agile,?

Answer 19

• May be informal/low tech

Question 20

How is the Record management product “Lessons Log” tailored for P2Agile,?

Answer 20

• As continual improvement is important to Agile, this may be displayed in a very visible way
• Can be used to create quick working agreements
• Can be used in a retrospective

Question 21

How is the Record management product “Quality Register” tailored for P2Agile,?

Answer 21

• Maybe more low tech

Question 22

How is the Record management product “Risk Register” tailored for P2Agile,?

Answer 22

• Maybe more informal/low tech
• Include risks identified during the Agile Risk Assessment

Question 23

How is the Report management product “Checkpoint Report” tailored for P2Agile,?

Answer 23

• Typically in the form of an information radiator and/or burn chart
• Could be replaced by a daily stand-up/scrum meeting with agreement of delivery team
  > However it must be avoided to be seen as a “reporting” mechanism
• If info is transparent, it can be pulled” by the PM when needed

Question 24

How is the Report management product “End Project Report” tailored for P2Agile .
.

Answer 24

• Agile useage assessment included (referencing Agilometer)

Question 25

How is the Report management product “End Stage Report” tailored for P2Agile . .

Answer 25

• Could be built incrementally throughout a stage depending on frequency of timeboxes/releases
• May be part of a release review

Question 26

How is the Report management product “Exception Report” tailored for P2Agile

Answer 26

• Most likely to occur when the expected amount to be delivered exceeds tolerances
• Could be triggered by a burn chart showing how progress has gone outside tolerance
• May further result in a meeting where options are discussed before raising it with PB

Question 27

How is the Report management product “Highlight Report” tailored for P2Agile?

Answer 27

• May contain additional information about releases (what’s been released and benefits enabled)
• Could be delivered verbally
• Could be in the form of an information radiator and/or burn chart
  >if info is transparent, it can be “pulled” by the PB

Question 28

How is the Report management product “Issue Report” tailored for P2Agile?

Answer 28

• More low tech
• Produced/updated during a sprint/release review

Question 29

How is the Report management product “Lessons Report” tailored for P2Agile?

Answer 29

• Maybe low tech
• Handed to Project Support informally

Question 30

How is the Report management product “Product Status Account” tailored for P2Agile

Answer 30

• Cater for high levels of change to iterative development/delivery