liveBook · Manning

Technical excellence

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

Technical excellence is a sustained level of software engineering quality that enables reliable delivery, maintainability, and further architectural change.

Technical excellence builds the day-to-day engineering foundation for sustainable velocity before teams attempt ambitious architecture modernization. It connects coding practices with reliable delivery, autonomous teamwork, and future change. section 17.4

Progressive practices include:

  • Make test-first development, pair programming, and frequent merging to trunk normal team practices. section 17.4
  • Create a learning culture through standalone learning hours and mob or ensemble sessions rather than relying on instruction alone. section 17.4

CloudSuite’s modernization sequence

CloudSuite improved coding practices first because its existing architecture slowed feature development. The team used collaborative learning to build engagement and prepare for broader architectural change, adapting the sequence to its organizational context. section 17.4

Figure 17.4 CloudSuite’s subdomains identified with a bottom-up modernization approach

Use the bottom-up modernization view to connect improved technical practices with the subdomains that later guide architectural change. section 17.4

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

How deep it goes
Defines test-first development, pairing, and frequent trunk merges, but stops short of prescribing implementation details.
Examples
Uses CloudSuite, test-first development, pair programming, trunk merging, learning hours, and mob or ensemble sessions.
What it assumes
Assumes teams can change coding practices; teaches the learning culture and collaborative sessions needed to make adoption work.
What you can do after
Apply it by cultivating learning, practicing collaboratively, and standardizing test-first development, pairing, and frequent trunk merges.
How it connects
Connects coding practices with sustainable velocity, autonomous teams, continuous delivery, learning culture, and architecture modernization.

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.