Our organization just ended a successful pilot project using agile methods. As a result management has decided to introduce agile across IT. There are still questions about adopting agile across the organization:
- Who will ensure we have the “right” architecture for our future needs?
- Who is responsible for software quality reuse?
- Does agile work large-scale projects
- Who will focus on the big picture?
This talk will present patterns and methods about how an agile organization manages architecture concerns.
Process/Mechanics
The presentation, depending upon the number of attendees, can be conducted in at least 2 ways:
- More lecture-based
In this format I will explain concepts and interact with attendees through questions. This is not my preferred way but if we get over 30 people it may be the best way.
- Software as an asset
- Facets of architecture to consider
- Architecture support in Agile software development
- Infrastructure and practices to support architecture needs
- Team configurations to support architecture evolution
- Business language for architecture requirements
- What can be managed at the enterprise level?
- How can we help teams deliver good architectures
If there are 30 or less attendees we can run exercises and simulations for parts of the agenda which help reinforce concepts such as:
* Technical debt
* Facets of architecture
* Continuous integration
* Writing user stories for non-functional requirements