PRINCE2 Product Delivery Pack

For detailed management product definitions, read ../../references/prince2-management-products.md when the user needs a complete PRINCE2 document set or asks what each artifact is for.

Use this workflow when a team manager or delivery team needs to accept, execute, and deliver a work package under PRINCE2 controls.

Inputs To Ask For

• Work package description
• Product descriptions and quality criteria
• Team capacity and delivery approach
• Dependencies and constraints
• Reporting cadence
• Quality review method
• Delivery acceptance route

Output Structure

1. Work Package Acceptance

• Products to deliver
• Acceptance criteria
• Quality method
• Constraints
• Reporting expectations
• Assumptions and dependencies
• Acceptance recommendation

2. Team Delivery Plan

• Activities
• Owners
• Dates
• Quality checks
• Dependencies
• Escalation points

3. Checkpoint Report

• Period covered
• Products completed
• Products in progress
• Forecast completion
• Risks and issues
• Help needed

4. Quality Evidence

• Product
• Quality criteria
• Review method
• Result
• Defects or follow-up
• Approval status

5. Delivery Handover

• Products delivered
• Acceptance evidence
• Open defects or exceptions
• Operational notes
• Recommendation to accept, accept with conditions, or reject

Quality Bar

• Do not accept vague work packages.
• Product quality criteria must be testable.
• Checkpoint reporting should be short and factual.
• Delivery is not complete until acceptance evidence is clear.