Shape → sign off → build → land → try

Shape → sign off → build → land it → try it

For work the person who asked will sign off on themselves, without reading code. It brings its members with it (planner, designer, lead, builder, sprinter, scout, reviewer and tester), and everything the person sees is in their words, with a picture.

What happens, step by step

1. Work out the plan — the planner writes a plain-language brief of what will change.
2. Draw what it will look like — the designer draws a picture of the result.
3. Ask you — you sign off on the brief and the picture, in Bloom or on your phone. Request changes and the plan is revised.
4. Split it into pieces and Build it — the lead splits the work, the builder builds it.
5. Run the checks — the project's tests run; a failure goes back to the build.
6. Look it over — the reviewer reads it as an engineer.
7. Look at it as the user — the tester tries it the way you would and reports what you would trip on first.
8. Save the work, open a pull request and wait for its checks.
9. Merge it and wait for the deploy — the change reaches your application the way every change does.
10. Try it in a browser — the crew tries the deployed application the way a user would.
11. Ask you again — you try the real thing yourself. Your approval accepts the work and it reads Live; a request for changes goes straight back to the build.

Where you weigh in

Twice: at the plan, with a picture in front of you, and at the end, with the deployed application in front of you. Everything in between runs on its own, and the board, the release line and the Feature Brief follow every step.

What install does

Adds this bloom and its members to your org; every station in the org pulls them down. A member your org already has is reused. Turn on auto-update to follow this listing; an edit you make pauses it.

What to customize

• The picture: drop the drawing step for changes nobody will see.
• The second sign-off: keep it for anything a customer touches; remove it for internal work you are happy to review from the card.
• Pair it with Plan → approve → build → review → merge for the engineering-only work on the same voyage.