Chaos Development, Agile and Scrum

Chaos Development is not a rejection of Agile. Agile stays the global structure. What the method replaces is the machinery many teams run Agile with: the ticket, the sprint, the estimate and the chart.

What stays from Agile

Read against the four values of the Agile Manifesto of 2001, this is where each one lives in the method:

  • Individuals and interactions over processes and tools. Work is pulled by the people who chose it, and meetings exist for decisions between people, not for reporting status.
  • Working software over comprehensive documentation. Specs are well described, not exhaustively described: invariants and acceptance, no procedures. Some questions of approach are settled by working code: two versions built on purpose and compared.
  • Customer collaboration over contract negotiation. The method says least about this value. What it keeps is the intent of a user story: what the work is for, in the user’s terms.
  • Responding to change over following a plan. A spec found wrong is changed by team decision at the next meeting, and the plan is re-read from artefacts rather than reported.

Same work, two ways to cut it

The same work, cut two ways
CaptureStatus: builtAHistoryStatus: builtBPanelStatus: builtCPasteStatus: builtDCaptureA3PanelC5HistoryB2PasteD3CaptureB2HistoryB3PasteA5CaptureA1PanelC3HistoryD2PanelD2CaptureC3PasteD2HistoryB5PanelC1PasteA3

An invented example using MojoPaste's four parts; MojoPaste itself was built by one person. On a sprint board, a seam can end up spread over several sprints and people, each piece with its own estimate. As trunks, each seam is one piece of work with one owner and a status line, and no estimates.

A sprint sizes work by the reporting cadence: whatever fits in a few weeks. A trunk is cut at the problem’s natural seam and is as big as that seam is. In the sprint view, one seam can spread across several people and sprints. The trunk view gives each seam one owner from start to finish.

Side by side

The Scrum Guide is short and leaves a lot open on purpose. Story points, velocity and assignees are not in it, and burn-downs appear only as one possible way to forecast progress. The table keeps the guide and common practice apart, so the comparison is with Scrum as written and with Scrum as it is often run.

Scrum and Chaos Development, side by side
TopicScrum Guide (2020)Scrum as commonly runChaos Development
Unit of workProduct Backlog items. Those that can be Done within one Sprint are ready for selection.User stories and tickets sized to fit a sprint.The trunk: cut at the problem's natural seam, as large as that seam is.
Who picks the workThe Developers select items in Sprint Planning, in discussion with the Product Owner.Each ticket has an assignee field.Pulled, never pushed. Whoever takes a trunk writes two or three sentences on why.
Time boxSprints of one month or less.Two-week sprints.No sprint boundary that work is expected to fit inside.
SizingThe Developers who will do the work size it. No method is prescribed.Story points, planning poker, velocity.No estimates. Each member declares the hours they intend to give, and nothing is measured against it.
Seeing progressA transparent Product Backlog, Sprint Backlog and Increment. Burn-downs are named as one possible way to forecast progress.Boards, burn-down charts, velocity charts.A status line inside each spec, and the map: every document a member works in, open to every other member. No secrets, and no record of the person.
The daily meetingA 15-minute Daily Scrum to inspect progress towards the Sprint Goal.A status round: yesterday, today, blockers.No status round, because the map answers that. A meeting adds detail to a spec or ratifies a change to one, or it did not need to happen.
Definition of doneA Definition of Done for the Increment. Where the organisation has one as a standard, every Scrum Team follows it as a minimum.One checklist every ticket must pass.Defined per trunk, by the people who will meet it, above a small safety floor that never moves.
PriorityThe Product Owner orders the Product Backlog.Priority kept on the ticket as well as in the order.The team decides what is important at the weekly. The order of the cards is the priority; there is no priority field.
Process roleThe Scrum Master is accountable for establishing Scrum and for the team's effectiveness.The Scrum Master runs the ceremonies.The chaos master keeps the board clean and in the order the team decided. Clerical, not editorial, and without power over the work.
Changing the planNo changes that would endanger the Sprint Goal. Scope may be clarified and renegotiated with the Product Owner as more is learned.New work waits for the next sprint.A spec changes only by team decision. Between meetings, write the finding down and keep building what it does not touch.
Two people, same thingNot addressed.Avoided as waste.Reuse is mapped first. Then duplication is chosen on purpose, compared, and the better version kept. The half-finished one still counts.
AINot addressed.Varies from team to team.An AI keeps status lines true and may propose changes to a spec. It never writes a claim, declared hours or a philosophy rule.

Scrum Guide: Schwaber and Sutherland, November 2020, scrumguides.org. Common practice: what many Scrum teams add to the guide; your team may differ.

Where the tracking lives

Where the tracking lives

Scrum as commonly run

Beside the work

  • Tickets moved across a board
  • Story points and velocity
  • Burn-down charts
  • A daily status round

Paid in behaviour: who moved what, and when.

Chaos Development

Inside the work

  • A status line in the header of each spec
  • The map: what exists in each member's folder

Paid in artefacts: what exists.

Small stories exist, at bottom, so that someone can see progress without asking. The map pays the same debt in a different currency. A burn-down chart pays it in behaviour: who moved what, and when. The map pays it in artefacts: what exists. Running both pays twice, and the second payment is taken out of autonomy.

What you give up

A fair comparison names what the method costs next to Scrum.

  • Early exit points. Small stories show a wrong direction within days. A wrong trunk can burn longer before anyone notices. The substitute is the map, and it only works if something lands on disk early.
  • A structure that depends less on who is in the team. The method assumes self-driven people who hold their own ideas firmly while respecting a colleague’s. Every rule trades supervision for trust, so a team that cannot carry the trust gets the chaos without the method.
  • Speed of one person’s decision. In Scrum, the Product Owner orders the backlog. Here, importance is decided at the weekly and no single person may change a spec, so a spec found wrong on Monday can wait until Thursday.

The rest of the method is on Chaos Development and Chaos Management. What the rules do to the people inside them is on the psychology page.