Handbook

Adopting: path B (team lead / EM)

ICP path B: a shared vocabulary for phases, ceremonies, and discipline bridges across repos.

Adopting Blueprints — Path B (team lead / EM)

What it is

ICP path B: a shared vocabulary for phases, ceremonies, and discipline bridges across repos.

Parent page: Adopting Blueprints. Complete path A first; path B builds on it.

When to use it

When the decision guide points you to path B.

Prerequisites

  • Path A basics in place (submodule, project sdlc/).

Steps

Job to be done: “I need a shared vocabulary for phases, ceremonies, and discipline bridges across repos.”

Step Action Verify
1 Complete path A. Same checks as path A.
2 Point the team at the Software delivery overview and the methodology slice you follow (e.g. Scrum, Kanban, Forge) under blueprints/sdlc/methodologies/. Team can name your default methodology entry file.
3 Optionally wire Forge artifacts (forge/, ember-logs/) using templates under blueprints/sdlc/templates/forge/ in a consumer repo. forge/forge.config.yaml exists after Forge init.

Example scenario (path B)
Starting situation Three backend repos need the same phase names and ceremony language; one repo already completed path A.
Action taken EM anchors methodology reading on blueprints/sdlc/methodologies/ + Forge setup; standups reference the same SDLC README links.
Expected result Engineers can point to the same methodology entry and use sdlc/ for team-specific interpretation without forking blueprints/.
What to check Spot-check two repos: submodule pointers sane; Team rollout plan if alignment is still uneven.

How to verify success

Team can name your methodology entry point and (if using Forge) has a valid forge/forge.config.yaml. Use Team rollout patterns when more than one repo must align.

What to do next