Agile architecture
- 1. Agile Architecture Resource: http://www.jrothman.com/ 2010/01/agile-architecture/
- 2. Iterate on the Architecture In a traditionally planned program: the architects get together and spend significant time developing architecture before starting any development. In an agile program: the architects are an integral part of the teams (they make decisions about the program’s architecture as the program proceeds)
- 3. Some Guidelines Helped the Architecture Never spend more than 15 minutes discussing the architecture. Everyone pair as often as possible so people could see evolving patterns as they proceeded. Developers use test-driven development (TDD) or behavior-driven development (BDD) approaches. If you are stuck for 15 minutes, ask for help.
- 4. Define a Program Team A program team is the risk-management body for the program. The program team can identify and lead the management of cross-program risks, make cross-program decisions and make sure the program meets its release criteria. The program team is responsible for the product achieving “done” for the release.
- 5. Refactoring the Program Team Software managers can decide if the program team has too many members. Project managers delegate one person to be their advocate to the program team. Break the time like this: one person for software project manager, firmware project manager, hardware project manager, marketing, architecture and the technical support manager.
- 6. Synchronize the Timeboxes Ifthe software teams chose two-week iterations and the hardware and firmware teams choose three-week iterations than this became a problem for managing the product backlog => difficult to synchronize the work.
- 7. Summary of Current State Programs are more difficult than projects. Any project or program of significant size will experience architecture problems. If you have a project larger than a couple of teams, consider program management. You can use agile approaches, and you will have to adapt them to your environment.