DetailsThis document has been superseded by C208.
- Additional Information
Reference S192 Published 23 Jul 2019 Pages 118 Superseded by C208 Type Snapshots Subject Agile Architecture
Customer Reviews 2 item(s)
- It's a good start, but could be both pruned and enhanced
It's much better than the TOGAF material in adapting to agile. I could spend many sentences complimenting the author. But, that would not help improve the product. So, below are my suggestions for changes and enhancements. However, there's too much development process content in relation to architecture content. It's highly likely that a reader of this work will have picked one of the many agile frameworks. It'd be better if this material avoided discussions of agile process and driving agile transformation and instead stated that it is designed to fit into most commonly practiced agile processes. Some issues, like balancing intentional vs evolutionary architecture and governance are largely left untouched. Similarly, there's no discussion of value streams vs value chains and the architectural differences of the two. It's likely that readers will need that described to be effective within their selected agile process. The coverage of CMMI adds little value here. The proposed maturity model is really one of the overall development process and not the architecture. (What does it mean to have an architecture maturity model?) But, if one is destined to exist, then I'd recommend "Business Agility" as the top level. That would imply that the business and technical architecture are working together to enable rapid response to a dynamic business environment. Last, the structure of the document might be improved if it was organized along the lines of defining an architecture in a green field and then refining it over time. That way, the reader will understand where in the process each method is applied, what the goals are, etc. The current document does a nice job of surveying many architectural skills and tools, but those new to agile architecture may not know where and how they apply. One option is starting with business architecture, moving to architectural evaluation of epics, roadmapping, governance, and then covering methods for structuring systems and build/deploy processes. Last, the managerial/inter-personal skills of an agile architect are worthy of mention. The final section might be on soft-skills demanded of the architect by an agile environment. I'll end as I started. The current document does a decent job at covering many items that must be addressed in agile architecture. With a few changes and enhancements, this could become a very solid addition to an agile architect's library.
- The content covers the application level with the new patterns, but lacks the integration with the others like Data Architecture (I mean not only Data Stores like RDBMS or NoSQL, but the domain from TOGAF)
In the next release I hope that the link to the ADM and architecture domaines from TOGAF will be well covered.