Software architecture for managers
Have you ever seen a system that was valuable, but that still was hard to change?
In a software development project, the functionality captures the attention. However, in the long run, the architecture of a system becomes critical. Software architecture is an asset, and it should be allocated proper attention.
While software architecture is a technical concern, understanding the nature of architecture is critical for the entire organization that depends on the development of software systems. Management decisions can affect architecture just as much as technical decisions do.
For example, the way of allocating the effort can direct technical teams on how to invest in architecture. Understanding the basic nature of software architecture can help in making those decisions.
Audience
The course is specifically targeted to non-technical people
Sample visuals
Course outline
Brief introduction in software architecture:
- The value of architecture
- The cost of architecture
- Paper architecture vs. real architecture
- Who should care about architecture?
- Architecture and architects
- Architecture and requirements
- Architecture and testing
Architecture and agility:
- Architecture as an emergent property
- Emergent properties and complex (as different from complicated) games
Architecture and technical debt:
- Architecture and quality
- The benefits and limitations of the technical debt metaphor
- Beyond technical debt: software habitability as a positive metaphor
Architecture as a collaboration:
- Architecture as a commons
- Architecture as a work in progress: dealing with the technical queue
- Architecture as a negotiation: dealing with the human aspects
- Small fixes and long term goals
The daily assessment game:
- The roles: stakeholder and facilitator
- Integrating daily assessment in the development process
- Dealing with the queue of technical tasks
- Examples of daily group decisions and actions