# PRINCE2 Managing Product Delivery > Draft Managing Product Delivery (MP) documents aligned with PRINCE2. Covers Team Plans, Product Descriptions, quality review records, Checkpoint Reports, and product handover documentation. Tags: Project Management, PRINCE2, Delivery, Quality ## Example Prompts - Create a Team Plan breaking down a Work Package into products, activities, and quality reviews - Write Product Descriptions with measurable quality criteria and review methods - Draft a Checkpoint Report showing actual vs. planned progress and tolerance forecast URL: https://rakenne.app/skills/prince2-managing-delivery/index.md Try this skill: https://rakenne.app/a/?skill=prince2-managing-delivery ## Overview Draft Managing Product Delivery (MP) documents aligned with PRINCE2. Covers Team Plans, Product Descriptions, quality review records, Checkpoint Reports, and product handover documentation. ## Getting Started Upload the Work Package authorization, any existing product descriptions, and team resource information to the workspace and activate the *PRINCE2 Managing Product Delivery* skill. The agent will help you create Team Plans, Product Descriptions, quality review records, and Checkpoint Reports. --- ## Example Conversation Below is an example of a typical session creating a Team Plan and Product Descriptions for a software delivery Work Package. The agent breaks down the work, defines quality criteria, and schedules checkpoints. > **You:** I've been assigned Work Package WP-009 for Stage 3 of our mobile banking app project. The Work Package covers the "Payment Module" — we need to deliver 3 products: a payment API, a mobile UI component, and an integration test suite. My team has 2 backend developers, 1 mobile developer, and 1 QA engineer. We have 6 weeks with a tolerance of +/- 3 days on schedule and +/- EUR 5K on cost. Checkpoint Reports are due every Friday. > > **Agent:** I'll create the Team Plan and Product Descriptions. Let me clarify a few points: > > 1. What technology stack? (e.g., Java/Spring for API, Swift/Kotlin for mobile, specific test framework?) > 2. Are there external dependencies — e.g., a third-party payment gateway sandbox? > 3. What quality method is specified — peer review, formal quality review, or automated testing? > > **You:** Stack: Kotlin/Spring Boot API, SwiftUI for iOS. Integration tests in JUnit with WireMock for the payment gateway. External dependency: the payment gateway (Stripe) sandbox needs API keys from the vendor — we've requested them but haven't received them yet. Quality method: peer review for code, formal quality review for the API specification, and automated test coverage minimum 80%. > > **Agent:** I've created the Team Plan and 3 Product Descriptions: > > **Team Plan** (`plans/wp009_team_plan.md`): > - **Week 1–2:** Payment API development (both backend devs), API specification formal review at end of Week 2 > - **Week 2–4:** Mobile UI component (mobile dev), concurrent with API finalization > - **Week 3–5:** Integration test suite development (QA + 1 backend dev) > - **Week 5–6:** End-to-end testing, bug fixes, product handover > - **Risk:** Stripe API keys not yet received — if delayed past Week 2, integration tests will use mock-only mode and real gateway testing shifts to Week 5 (consuming schedule tolerance) > - **Checkpoints:** Every Friday, covering products completed, test coverage metrics, and tolerance forecast > > **Product Descriptions** (in `products/`): > - **PD-031: Payment API** — RESTful API, 4 endpoints (initiate, confirm, refund, status), quality criteria: API spec reviewed, 80% test coverage, <200ms response time, PCI-DSS compliant data handling > - **PD-032: Mobile UI Component** — SwiftUI payment flow (card entry, confirmation, receipt), quality criteria: peer-reviewed code, accessibility compliance (WCAG 2.1 AA), UI tested on iPhone 14+ screen sizes > - **PD-033: Integration Test Suite** — JUnit test suite with WireMock stubs + live gateway tests, quality criteria: 80% code coverage, all payment scenarios covered (success, decline, timeout, refund), CI pipeline integrated > > All documents reference WP-009 and the agreed tolerances. Shall I adjust anything? --- ## Document Excerpt Below is a representative excerpt from a **Product Description** prepared with the skill. --- ### Product Description — PD-031: Payment API (Excerpt) **Work Package:** WP-009 (Payment Module) **Project:** Mobile Banking App — Stage 3 --- | Field | Detail | |---|---| | **Product Identifier** | PD-031 | | **Title** | Payment API | | **Purpose** | Provide a RESTful API enabling the mobile app to initiate, confirm, refund, and query payment transactions via the Stripe payment gateway. | | **Composition** | (1) API specification (OpenAPI 3.0), (2) Kotlin/Spring Boot service with 4 endpoints, (3) Stripe gateway integration layer, (4) Unit and integration tests, (5) API documentation | | **Derivation** | Payment requirements (REQ-044 to REQ-058), Stripe API v2024-12 documentation, PCI-DSS v4.0 requirements for cardholder data handling | | **Format and Presentation** | Kotlin source code (Spring Boot 3.x), OpenAPI 3.0 YAML spec, Markdown documentation | | **Development Skills Required** | Kotlin, Spring Boot, RESTful API design, payment gateway integration, PCI-DSS awareness | #### Quality Criteria | # | Criterion | Measure | Tolerance | |---|---|---|---| | 1 | API specification formally reviewed | Approved by Senior Developer and Architect | No tolerance — must pass | | 2 | Test coverage | >=80% line coverage (JaCoCo) | 78% minimum | | 3 | Response time | <200ms p95 under load (100 concurrent requests) | <300ms | | 4 | PCI-DSS compliance | No cardholder data stored in logs or database; tokenization verified | No tolerance | | 5 | Security review | OWASP Top 10 checklist passed | No critical or high findings | #### Quality Responsibilities | Role | Person | Responsibility | |---|---|---| | Producer | Backend Dev Team (A. Mueller, K. Park) | Develop, unit test, document | | Reviewer | Senior Developer (L. Fischer) | Peer review code, formal review API spec | | Approver | Team Manager (J. Santos) | Sign off on quality criteria met | --- *This excerpt is illustrative. Final content must reflect the specific project's products and quality standards.* --- Back to [Skill Library](https://rakenne.app/skills/index.md)