liveBook · Manning

Learning culture

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

A learning culture is an organizational environment that encourages continuous knowledge development, experimentation, and sharing.

A learning culture creates the conditions for technical excellence by making continuous practice, experimentation, and shared learning part of everyday work. It supports ambitious modernization without treating new ways of working as instructions that teams can adopt instantly. section 17.4

A practical learning loop combines:

  • Short standalone learning hours for focused exploration. section 17.4
  • Mob or ensemble sessions for collaborative application and reinforcement. section 17.4
  • Progressive adoption of practices such as test-first development, pair programming, and frequent trunk merging. section 17.4

CloudSuite’s bottom-up modernization

CloudSuite built engagement by starting with tactical software design and modeling rather than beginning with broad EventStorming. Developer interest led to a ubiquitous language, collaborative modeling, stronger vertical alignment, and teams organized around subdomains. section 17.4

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

How deep it goes
Explains learning hours and mob sessions as actionable practices but stops short of prescribing a fixed implementation process.
Examples
Uses CloudSuite’s learning hours, ensemble sessions, tactical modeling, ubiquitous language, and subdomain-oriented team organization.
What you can do after
Practice new technical approaches collaboratively and build engagement for incremental modernization.
How it connects
Connects technical excellence with test-first development, pair programming, trunk-based development, collaborative modeling, and domain-driven design.

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.