Minimum Viable Process
summary
A concrete recipe: a Kanban board with WIP limit eight for in‑development and WIP limit four for ready work, daily 15‑minute cadence with a 15-minute stand-up that only reviews cards in development, demos triggered on deploy behind feature flags and continuous deployment, tiny user stories scoped to a couple of days, and enforced daily pair swapping using a simple randomizer like Parrit pair rotator. Work moves to validated within about validate within 12 hours, yielding lower cycle time and continuous delivery.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:30How we came up with this idea
- 2:47Stand up demo
- 11:03Feature Flags
- 12:35Include Everyone
- 13:35User Stories
- 21:32Backlog Grooming
- 24:03Whip Limits
- 25:58Team Meetings
- 26:41Pairing
- 31:07Daily Pairing
- 31:42Knowledge Silo
- 33:30Help Asking Questions
- 34:38QA Break
- 37:34Product Owner
- 41:54Prioritize over Process
- 44:59Outcomes
related talks
49mBaking Boards: Tweak the Recipe for Agile Development
38mExpect the Unexpected! A Method for Handling Unplanned Work
31mHow we used Kanban in Operations to Get Things Done
35mKanban, our way
01h 00mMob Programming, A Whole Team Approach
36mDEVELOPER ORIENTED PROJECT MANAGEMENT
50mMob Programming, A Whole Team Approach
52mShifting into continuous delivery