Playbooks¶
This area contains Alescent Plays and Playbooks used to execute recurring Value Realization activities.
It applies the portable VRBoK distinctions among Effort, Play, Playbook, Effect, Practice, Project, Maturity Progression, Progression Pattern, and Progression Application.
Canonical Applied Definitions¶
Effort. A bounded intentional action, intervention, or coordinated set of activities undertaken to establish, change, protect, sustain, or evidence a realization condition or Effect.
Play. A reusable prescribed Effort that may be selected and applied within a Playbook, Maturity Progression, Progression Pattern, Initiative, or other governed context.
Playbook. A governed composition of Plays and supporting guidance used to pursue one or more Effects within a defined context.
Alescent Plays and Playbooks operationalize portable concepts. They do not redefine the VRBoK ontology.
Semantic Boundaries¶
- An Effect describes an outcome class. A Play or Playbook describes intentional intervention logic.
- A Priority is an Effect designated as a principal intended outcome in context.
- A Practice is a repeatable discipline or method system. A Play may invoke one or more Practices.
- A Project or Initiative is a governed work object through which Plays and other Efforts may be executed.
- A Maturity Progression defines an adjacent-state transition. It may cite Plays and Playbooks but is not itself a Playbook.
- A Progression Pattern is reusable prescribed transition logic. It may include or cite Plays.
- A Progression Application applies Progression Patterns, Plays, and other Efforts to a specific subject and scope.
Playbook Areas¶
Additional Playbook classes may be added where a governed composition of Plays is reusable across subjects or contexts.
Play Metadata¶
A material Play should identify:
- Play ID, name, definition, version, owner, and lifecycle status;
- intended Effect relationships, including Priority, contributing, protected, and trade-off Effects;
- applicable Value Realization Domains;
- triggering conditions and entry criteria;
- required Practices and Proficiencies;
- enabling Platforms, Products, Partners, information, and controls;
- Projects, Initiatives, or Progression relationships;
- expected evidence and Performance Measures;
- constraints, risks, exclusions, and stop conditions;
- related Playbooks, Progression Patterns, Offerings, Products, Proof, and derivative assets.
Playbook Metadata¶
A Playbook should identify:
- the Plays it composes;
- the context, Persona, Priority, Capability, Competency, Product, Platform, Partner, or scenario it addresses;
- sequencing, decision rights, dependencies, evidence, and adaptation logic;
- the Effects it seeks to influence and the trade-offs it must protect;
- applicable Progressions and Progression Patterns where maturity advancement is involved;
- ownership, supportability, repeatability, and commercialization readiness.
Relationship to Progression Patterns¶
A Progression Pattern may cite one or more Plays or Playbooks. The same Play may support several Progressions, Capabilities, Competencies, and Domains.
Alescent-specific Progression relationships are registered in Alescent Progression Pattern Registry.
Play execution or Playbook completion does not prove maturity advancement or realized value. The applicable evidence and exit criteria remain controlling.
Governance¶
Each Play and Playbook should be maintained as a structured Applied Value Library item using the library metadata model.
Playbooks may themselves become Products or support Products, Practices, Offerings, and Engagement delivery. That relationship must be explicit.
PDFs, decks, briefs, worksheets, assessments, and other channel-specific outputs are derivative assets governed through the Derivative Asset Register.