Delivery Standard: Library Microsite (Static Content Simulation)

✅ Put Simply

Build an interactive, searchable library of all PwC Delivery Standards — reusable frameworks that define how world-class work is delivered — aligned to the PDM lifecycle.

✅ Why It Matters

Delivery Standards represent the gold standard for delivery across PwC. They provide structure, repeatability, and rigor to how client work is scoped and executed. However, there's currently no centralized, navigable home for these assets. A formal DS Library allows teams to:

• Easily reference Delivery Standards during pursuit to inform proposals.

• Explore structured delivery approaches tied to Offerings.

• Navigate each Delivery Standard visually, with Frameworks aligned to the stages of PDM.

• Ensure global consistency while enabling teams to reuse trusted assets during scoping and delivery.

This isn't just about knowledge management — it's about powering how PwC scales consistent, high-quality delivery across engagements.

✅ What’s Needed (Static Prototype Data)

• JSON representing each playbook object with fields for title, purpose, building block, roles, use cases, stage, WBS ID, tags

• Static filters to simulate search and facet filtering

• Hardcoded "linked deliverable" and "framework" references

✅ High-Level Acceptance Criteria (MVP)

1. Given a user accesses the Delivery Standard Library,
   When they browse or search,
   Then they should see a list of Delivery Standard, associated Offerings, Role(s) and other metadata.

2. Given a user opens a Delivery Standard,
   When viewing its contents,
   Then they should see a canvas-style diagram of the PDM lifecycle with Frameworks arranged across the four stages.

3. Given a user interacts with the PDM diagram,
   When clicking on a Framework,
   Then they should be taken to a Framework page that details associated Activities, Deliverables, guidance content, and linked assets.

4. Given a pursuit team is scoping a new engagement,
   When relevant Offerings are selected,
   Then applicable Delivery Standards should be automatically inferred and suggested for reference.

5. Given a user is preparing a proposal,
   When viewing a Delivery Standard or Framework,
   Then they should be able to export or copy relevant content to inform their pitch materials.

6. Given Delivery Standards are centrally maintained,
   When updates are made by content owners,
   Then changes should be version-controlled and reflected across all views of the library.

Not in Scope:

• Real-time search indexing

• Content management UI or backend updates

Related Functional Requirements: FR1.1, FR1.2, FR1.3, FR1.4