- 10When are specifications not enough?
- 11Where is the state of the work kept?
- 12Who prepares a change before coding starts?
- 13What does impact analysis tell you, and when does it run?
- 14How do coding agents use the graph?
- 15How is each change checked, and how does the graph stay current?
- 16Who decides which work agents do?
- 17How do managers see what people and agents are doing?
- 18What happens across many products?
- 19What about existing systems and technical debt?
- 20What changes for the team?
- 21What results have teams seen?
Home / Follow the story / Scene 20: What changes for the team?
Loading the video
Transcript
20. What changes for the team?
The sprint, the ticket system and code review stay as they are. The team adds a spec sprint ahead of implementation. The team works in three layers: the custodians, the implementation teams, and an enablement layer from Accion Labs. Forward-deployed engineers from Accion Labs fill any custodian role the client cannot staff yet. Specialists work part-time across several workstreams, and one architect can cover two or three of them. The custodians stay human. Much of what the custodians know comes from customer calls, compliance decisions, vendor contracts and user research, which no agent can read. Agents draft updates to the graph, and the custodians approve them.
On the site: The Layered Team Structure · Forward-Deployed Engineers · Fractional Allocation
Choose a path
The full video in six parts and an appendix, one part at a time.