- 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 28: Two engagements
Transcript
28. Two engagements
Two anonymized engagements show the methodology at work on continuous SDLC. The first archetype is a live code base of more than two million lines, with five to six scrum teams. Extracting the graph from the code built all four layers in two to three weeks. On the extracted graph, impact analysis replaced three to five days of investigation by senior engineers. The second archetype is a new user-interface workstream that grew in complexity, and started with the design layer of the graph. In its first sprint under Semantic Engineering, the workstream reused 53 percent of its components from the existing design system. In both engagements, structured knowledge was added exactly where the specification alone was not enough.
On the site: The Archetypes · Brownfield Enterprise Modernization · What Changed in How the Team Works
Choose a path
The full video in six parts and an appendix, one part at a time.