Repository navigation
v2.3.0 — Value Delivery System Upgrade
vNext connects template selection, project execution, governance, and ongoing delivery to measurable business outcomes.
🎯 Major Features
Value Delivery & Benefits
- Connect project outputs to business outcomes through benefits realization, KPI mapping, and value-stream guidance.
- Review benefits after delivery and carry learning into future decisions.
Template Selection & Navigation
- Find resources through six performance domains: Stakeholder, Team, Delivery, Planning, Uncertainty, and Measurement.
- Use role-based entry points and rules-based recommendations to select templates for your context.
- Choose project, product, or mixed delivery modes with supporting rationale.
Principles & Practical Guidance
- Understand which principles each canonical template supports.
- Use template-specific “When to Use” and “When NOT to Use” guidance.
- Identify common anti-patterns and assess alignment with the guiding principles.
Adaptive Governance
- Select light, standard, or rigorous governance according to context.
- Scale controls to risk and respond to defined events.
- Connect governance decisions with compliance responsibilities and evidence needs.
Product & Continuous Delivery
- Plan incremental releases, staged rollouts, readiness checks, and recovery.
- Establish stakeholder feedback loops and ongoing operational ownership.
- Use flow and delivery metrics to inform improvement beyond project closure.
🔧 For Maintainers
- Canonical asset locations, migration records, and cross-references provide a traceable maintenance baseline.
- Catalog-driven checks validate principle coverage as the collection evolves.
- Content-review and freshness checks detect drift while preserving original review dates.
🧪 Validation
At the reviewed implementation baseline:
- 83 focused regression tests passed.
- Principle coverage validated across all 139 canonical catalog entries.
- All 137 migrated assets passed review/freshness checks and migration post-checks.
These counts describe the verified baseline, not a fixed repository size. Acceptance and integration evidence is maintained in the vNext closeout record.
🔗 Compatibility
Migration-era legacy paths remain supported through vNext and at least the next major release. Existing bookmarks and integrations can transition under the documented compatibility policy.
🚀 Getting Started
- Follow the Getting Started Guide to customize your first template.
- Browse the performance domains.
- Explore the product-thinking framework and continuous-delivery guidance.
Version identity: v2.3.0 and vNext identify the same accepted commit febdf847cd8842fd3929973360b14d27b4513b81. The original release URL and publication date are retained.