liveBook · Manning

Continuous improvement

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

Iterative development is an approach that delivers a product or capability through repeated cycles of implementation, feedback, and refinement.

Continuous improvement means regularly reflecting on how discovery, design, and delivery work together, then adapting based on what teams learn. Too much discovery and design can delay delivered value; too little can lead to the wrong work or avoidable blockers. Feedback from delivery should shape future discovery and design. section 16.3.4

Use recurring questions to spot imbalances and guide adjustments:

  • Has the team delivered progress that people outside it can recognize recently? section 16.3.4
  • Are delivery roadblocks or shifting priorities revealing changes needed in discovery or design? section 16.3.4
  • Is design work happening far ahead of delivery that could instead be done later? section 16.3.4

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Explains recurring reflection and feedback loops, but provides no fixed method for finding an optimal balance.
Examples
Uses avoidable roadblocks, changing priorities, and visible progress as prompts for team reflection.
What you can do after
Evaluate work patterns and feed delivery lessons into future discovery and design.
How it connects
Connects discovery, design, delivery, feedback loops, and hierarchical roadmaps.

Also explained in

Compare how 30 books explain continuous improvement →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.