This Crisp in Gothenburg course is in cooperation with AGREAT
One definition of software architecture is that it’s ”the bits of the system that are hardest to change”. This isn’t very helpful and also completely wrong!
In this workshop, we cover how good architecture can enable agility and how to do it in a development context where you can’t “set the architecture” as an initial step. Instead, you have to take an evolutionary approach. This means that the role of the system architect is different, and we dive into what technical leadership means in an agile organization.
- How architecture enables agility
- A useful definition of “software architecture”
- Working with architecture in an agile context
- Important useful practices
- The business value of architecture
- Documenting architecture (or not)
- The role of the architect
This workshop is for 1 or 2 days. The difference is how deep we dive into the topics above.
This class is suitable for:
- Anyone with the word “architect” in their title
- (Engineering) Managers
- Agile Coaches (including Scrum Masters)
Basic knowledge of agile and good understanding of software development.