Appendix E — Delivery method profiles
Bansat’s gates (G0–G4) say what must be true before a project moves on. A delivery method says how the team works in between. The two fit together: choose the method in 11.7, then read only the profiles it names (an outer method for approvals and an inner one for the build can both apply).
| Profile | Use it for |
|---|---|
| E1 Scrum | One team on complex work, where you learn as you build |
| E2 Kanban | A steady stream of requests and fixes, live apps and retrofits |
| E3 Stage gates | Fixed-price client work, a hard date with fixed scope, and anything that needs formal approval at each stage |
| E4 Shape Up | A product team that owns its roadmap, where the scope can flex to fit the time |
| E5 Solo loop | One person building on their own |
| E6 Scaled methods | Several teams on one product: LeSS, or SAFe® where the organisation already runs it |
Where each gate falls:
| Gate | Scrum | Kanban | Stage gates | Shape Up | Solo loop | Scaled |
|---|---|---|---|---|---|---|
| G0 Idea | A draft Product Goal | The first item, “Write the blueprint”, enters the board | The start-up request | A shaped pitch | An idea note | A product vision and one backlog |
| G1 Blueprint approved | Before the first Sprint; the FR list seeds the Product Backlog | The blueprint item is done, so build items may start | The end of initiation: the project is authorised | The first bet on a cycle | You sign the G1 row before writing production code | Before the first product-level Sprint, or PI Planning |
| G2 Data-ready | A Product Backlog item that must be Done before any real personal data | A policy: nothing that collects real data passes “Ready to release” before G2 | A stage boundary before real data | In the cycle’s scope before real users | A checklist before the first real user | A shared Definition of Done item for every team |
| G3 Release candidate | Whenever an Increment meets the Definition of Done and Part 13 is green; don’t wait for a Sprint Review | The release policy on the “Release” column | The last stage boundary before launch | The end of the cycle that ships | Launch-day checklist | The release of the integrated increment |
| G4 Post-launch | A Retrospective plus the 30-day review | A review of the four flow measures, plus the 30-day review | Closing the project, then the benefits review | The cool-down after launch | The 30-day review | An overall retrospective across teams |
The same documents in every method:
- The FR list (1.5) becomes backlog items, work items, products or pitches.
- Bansat’s Definition of Done (11.2) and the state matrix (10.7) join the method’s own Definition of Done.
- ADRs (Part 4) hold the decisions, including the choice of method.
- The gap register (14.4) becomes the backlog or board for a retrofit.
- Part 13 is the release criterion, whatever the method.
Sources, licences and trademarks. Each profile summarises its method in Bansat’s own words and links to the official source. None of their text is copied, because the Scrum Guide is CC BY-SA 4.0, the Kanban Guide names both CC BY 4.0 and CC BY-SA, and the others are all rights reserved.
- PRINCE2® and PRINCE2 Agile® are registered trademarks of the PeopleCert group.
- PMBOK® is a registered mark of Project Management Institute, Inc.
- SAFe® and Scaled Agile Framework® are registered trademarks of Scaled Agile, Inc.
- The Scrum Guide™ is by Ken Schwaber and Jeff Sutherland.
- Shape Up is © 37signals LLC, and the LeSS rules are © The LeSS Company B.V.