From talk to running system
The claim
Work becomes a system when a sentence in a document can still be found after it has passed through a plan, a cost and a ticket.
That join is where teams lose things. Somebody turns the requirement into a plan. Somebody else costs the plan. By the time an engineer opens a ticket the original sentence has been rewritten three times and nobody can point back at it. Nothing failed. It drifted, and a diff will never show you that.
This film runs the chain in one direction and does not cut back to explain itself. A client document, the plan it became, the drawings drawn from that plan, a cost built out of the same units, and issues on a customer’s own board.
Reading the film
0:28 — the product is named, and its first claim is about your process rather than itself. Your repositories, your issues, your board, your wiki. Everything after this beat has to land inside those four things, or the claim was broken in the first thirty seconds.
1:00 — the document is paraphrased for the last time. Twelve phases. Seventy work units. Five hundred and sixty hours, added up from the units. From here the film stops quoting the document and starts pointing at what came out of it. This is the twelve-phase plan the Unboxing takes apart, and the two hundred and ten questions it left open are settled there.
1:57 — every phase draws its own architecture before the code exists. What is on screen is a hospital cabling design: risers by floor, drop counts per telecom room, grounding busbars named to TIA-607-C. Nobody drew it, and the count of them is earned in article one, where the caption carries its own denominator.
2:09 — the same work units, costed. A statement of work beside the plan it came from, three roles, hours and a rate against each. No second estimate is made here. The commercial number is a view of the units already on screen, which is why it can be redrawn when the units move.
2:25 — the chain ends on somebody else’s board. Forty six of forty six issues in a customer’s own JIRA project, with a reporter and a priority on every one. This is where the film stops. There is no pull request in it and no merge, and no green tick at the end.
3:07 — take it away in a year. One card, and it is the question that decides whether any of the four minutes above is worth adopting. Article six answers it against running screens instead of asserting it.
What this costs, and what it does not do
The chain is not one customer from end to end. The plan, the drawings and the statement of work come from one estate; the issues come from another, and the film does not mark the change. Five hundred and sixty hours is a plan’s estimate. And it stops at issues on a board, so nothing here shows work merged or running. It shows the shape holding, not the shipping.
That chain assumes somebody is starting. Almost nobody is.
The foundation is already there →See it running
sue-quill in the Stellarverse index →The same film, next to every other one, with the evidence for each sitting under the film that pays for it. No price and no form on that site.