Handbook

Project management (PM)

Reusable, **product-agnostic** blueprint for project management — the discipline of governing delivery: schedule, budget, resources, risk, and stakeholders. It answers **"are we delivering on time, on

Project management (PM)

Reusable, product-agnostic blueprint for project management — the discipline of governing delivery: schedule, budget, resources, risk, and stakeholders. It answers "are we delivering on time, on budget, within scope, with acceptable risk?" while SDLC blueprint answers "are we building the product right?" and Product development lifecycle (PDLC) answers "are we building the right product?"

PM provides the governance layer between product strategy (PDLC) and software delivery (SDLC). In small Agile teams, PM concerns are often absorbed into existing roles (PO, Scrum Master). In enterprise contexts, PM is an explicit discipline with dedicated roles, processes, and reporting structures.

Document Purpose
PM.md What PM is, roles, process groups, governance model, metrics
PM ↔ SDLC ↔ PDLC bridge How PM relates to SDLC and PDLC — three-domain comparison, nesting, role mapping, anti-patterns
approaches/ Deeper guides: PMI/PMBOK, PRINCE2, Six Sigma / Lean Six Sigma

Relationship to other packages

Package How PM relates
SDLC blueprint SDLC phases A–F execute inside PM governance. PM provides schedule, budget, and risk management around SDLC delivery. See PM ↔ SDLC ↔ PDLC bridge.
Product development lifecycle (PDLC) PDLC decides what to build; PM governs how the delivery is executed. Product strategy (P1–P3) feeds into project initiation; project outputs feed back into PDLC launch and growth (P4–P6).
Product functional documentation blueprint PM artifacts (project charter, status reports, risk register) complement product-functional docs.
Agents blueprint (automation) Automation recipes may support PM activities (status aggregation, risk dashboards, resource tracking).

Adopt in your repo

  1. Copy or submodule blueprints/disciplines/governance/pm/ alongside blueprints/sdlc/ and blueprints/pdlc/.
  2. Use PM.md to orient your team on where project governance lives relative to product strategy and software delivery.
  3. If you already use blueprints/sdlc/ and blueprints/pdlc/, read PM ↔ SDLC ↔ PDLC bridge to understand how the three domains interact.
  4. Choose an approach from approaches/ that fits your organizational context — or use the generic PM model from PM.md and tailor.

Canonical source is this repository on main. See Blueprint policy — do not change casually for change rules.

Canonical source

Edit https://github.com/autowww/blueprints/blob/main/disciplines/governance/pm/README.md first; regenerate with docs/build-handbook.py.