Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a2226c976d4a51a8

Jump to content

Product description

From Wikipedia, the free encyclopedia

In the PRINCE2 project management method, a product description (PDD) is a structured format that presents information about a project product. It is a management product (document), usually created by the project manager during the process of initiating a project in the initial stage of the PRINCE2 project management method. It is approved by the project board as part of the project plan documentation.[1]

It should not be confused with a project product description(PPD), which (in the PRINCE2 method) is generated in the start up process of the pre-project stage, and forms part of the Project Brief. While the PPD is related to "finalist products"—those delivered to the client at the end of the project—the PDD refers to all project products, including intermediate products necessary in the project life that need definition. For example, in a project to build a plane wing, the finalist product is the actual wing, and has acceptance criteria defined in the corresponding PPD. However, the project may require simulations, and even a wind-tunnel prototype and testing rig. Those are intermediate products, not handed or delivered to the client. However they are still subject to definitions and quality criteria that is detailed in the corresponding PDDs. Therefore, all product contained in the PPD are also in the PDDs, but not the other way.

The structure of product description, according to PRINCE2:

  • Identifier
  • Title
  • Purpose
  • Composition
  • Derivation
  • Format and presentation
  • Development Skill Required
  • Quality criteria
  • Quality tolerances
  • Quality method
  • Quality skills required
  • Quality Responsibilities

See also

[edit]

References

[edit]
  1. PRINCE2 Components Jay Siegelaub