Library
Every ingredient in the pantry
52 roles, events, artifacts, practices, metrics and models from 26 sources. Each one lists what it fixes, what it needs and what it clashes with.
5 Whys
Lean · ToyotaAsk “why?” repeatedly to get from a symptom to a root cause.
PracticeAsync Check-in
Remote-first teamsA written daily update in your chat tool instead of a live meeting. Works across time zones.
EventBacklog Refinement
ScrumOngoing work to split, clarify and size upcoming items so they’re ready to start.
EventBig Room Planning
SAFe · LeSSAll teams plan the next quarter together, find dependencies and agree shared objectives. SAFe calls it PI Planning.
PracticeBlameless Postmortems
SREAfter an incident, review what happened to improve the system, not to find someone to blame.
PracticeBuilt-in Compliance
SAFe · DevOpsCompliance checks (traceability, approvals, evidence) live in the Definition of Done and the pipeline, instead of a big audit phase at the end.
PracticeClasses of Service
KanbanExplicit policies for different kinds of work: expedite, fixed date, standard and intangible.
✓ In your recipePracticeContinuous Delivery
DevOpsEvery change that passes the pipeline can go to production at the push of a button.
PracticeContinuous Integration
XP · DevOpsEveryone merges to the main branch at least daily, with an automated build and tests on every change.
PracticeContinuous User Interviews
Product discoveryTalk to real users every week so decisions rest on evidence, not opinion.
ModelCynefin
Dave SnowdenA sense-making framework: clear, complicated, complex and chaotic work each need a different approach.
EventDaily Stand-up
Scrum · XPFifteen minutes a day to plan the next 24 hours and surface blockers.
ArtifactDefinition of Done
Scrum · XPA shared checklist every item must meet before it counts as done.
EventDesign Sprint
Google VenturesA five-day process to go from a big question to a tested prototype.
MetricDORA Metrics
DevOpsFour measures of delivery performance: deploy frequency, lead time for changes, change failure rate and time to restore.
PracticeEnsemble Programming
XPThe whole team works on one thing at a time, at one screen. Also called mob programming.
MetricFlow Metrics
KanbanTrack cycle time, throughput, work in progress and item age straight from your board.
PracticeHypothesis-driven Experiments
Lean StartupTreat features as bets with a measurable hypothesis, and build the smallest possible test.
ModelImpact Mapping
Gojko AdzicA map linking a goal to the people who influence it, the impacts you want, and the deliverables that might cause them.
PracticeLiberating Structures
Lipmanowicz & McCandless33 simple meeting formats, such as 1-2-4-All, that get everyone contributing instead of the loudest few.
MetricMonte Carlo Forecasting
Kanban · #NoEstimatesForecast delivery dates from past throughput instead of estimating every item.
ArtifactNow / Next / Later Roadmap
Product managementA roadmap that shows priorities without fake dates: what we’re doing now, next and later.
ArtifactOKRs
Intel · GoogleQuarterly objectives with measurable key results that connect team work to company goals.
ArtifactOne Backlog for All Teams
LeSSSeveral teams pull from a single ordered backlog owned by one Product Owner, so priorities are set once for the whole product.
PracticePair Programming
XPTwo people work on one task at one screen, swapping roles often.
RoleProcess Facilitator
Scrum · KanbanSomeone who keeps the process healthy: runs events well, removes blockers and coaches the team. Scrum calls it Scrum Master; Kanban calls it Flow Manager.
ArtifactProduct Backlog
ScrumA single ordered list of everything the product might need. Detailed at the top, rough at the bottom.
✓ In your recipeArtifactProduct Goal
ScrumThe longer-term objective the backlog works toward.
RoleProduct Owner
ScrumOne person accountable for what the team works on next and why. Owns the order of the backlog and talks to stakeholders.
EventReplenishment Meeting
KanbanA short regular meeting where stakeholders choose what enters the team’s ready queue next.
EventRetrospective
Scrum · XP · LeanThe team regularly looks at how it works and picks one thing to improve.
✓ In your recipePracticeRotating Interrupt Shield
XP · SREOne team member per week handles all incoming interruptions so everyone else can focus.
✓ In your recipeEventScrum of Scrums
Scrum@ScaleA representative from each team meets a few times a week to clear cross-team blockers.
EventService Delivery Review
KanbanA regular look, with customers, at how well the team delivers: speed, predictability and quality.
RoleService Request Manager
KanbanOwns the intake of incoming requests: triages them, sets expectations with requesters and orders the queue.
EventSix-week Cycles
Shape UpShaped pitches are chosen at a betting table for fixed six-week cycles, then two weeks of cool-down. Scope flexes; time does not.
MetricSLOs & Error Budgets
SREAgree a reliability target. When the error budget runs out, feature work pauses for reliability work.
ArtifactSprint Goal
ScrumOne objective per sprint that gives focus and room to adapt the plan.
EventSprint Planning
ScrumAt the start of each sprint the team agrees a goal and picks the work that achieves it.
EventSprint Review
ScrumAt the end of each sprint, show working results to stakeholders and adapt the plan from their feedback.
EventSprints
ScrumWork in fixed cycles of one to four weeks. Each sprint has a goal and ends with something usable.
✓ In your recipeMetricStory Points & Velocity
Scrum · XPSize items relative to each other and track how much the team finishes per sprint, to forecast.
ModelStream-aligned Teams
Team TopologiesEach team owns one flow of value end to end, such as a product or customer journey, with the skills to deliver it without hand-offs.
PracticeSwarming
Kanban · LeanWhen an item is stuck, people pause new work to help finish it.
PracticeTeam Health Check
SpotifyThe team rates itself on areas like speed, fun, learning and mission, then tracks the trend.
ArtifactTeam Working Agreement
Team coachingA short set of norms the team writes itself: how we meet, communicate, decide and handle conflict.
✓ In your recipePracticeTest-Driven Development
XPWrite a failing test, make it pass, then tidy up. Repeat in small steps.
ModelUser Story Mapping
Jeff PattonLay out the user’s journey left to right, then slice thin releases top to bottom.
ModelValue Stream Mapping
LeanMap every step from idea to customer, showing working time against waiting time.
ArtifactVisual Work Board
KanbanAll work on one board, with columns that match how work really flows.
✓ In your recipeEventWalk the Board
KanbanA daily check that goes through the board right to left, focusing on finishing what’s closest to done.
✓ In your recipePracticeWIP Limits
KanbanA cap on how many items can be in each stage at once. Stop starting, start finishing.
✓ In your recipe