“Architecture is the primary carrier of system qualities such as performance, modifiability, and security, none of which can be achieved without a unifying architectural vision” … SEI
Who can argue with those words?
Among the agile methodologies that emphasize architecture, in contravention of agile principle , which is pretty much nonsense, I like DAD (Disciplined Agile Delivery) which is more or less where Scott Adler's personal journey in agile has led him.
Architecture in DAD pretty much begins with the idea of “enterprise architecture”:
• Enterprise architecture (EA). An organization’s enterprise architecture consists of the various structures and processes of an organization, including both technical structures and processes as well as business/domain structures and processes. There is always an enterprise architecture, even when it isn’t documented.
Even though DAD allows for the EA not to be documented, a role is presumed called the Enterprise Architect who has responsibility for the enterprise architecture in whatever form it takes. Built into DAD is a purposeful collaboration between project architects—which could be a team of architects at both project office and agile teams—and the enterprise architect.
An architect team workflow is envisioned with four major tasks:
1. Envision initial architecture. The outcome is most often a model of the product or process as it will be integrated into the business. Although there could be iteration of this model, the initial model more or less sets the vision
2. Collaborate with business stakeholders. This task is an on-going level of effort which has communication at its core
3. Collaborate with IT stakeholders. Similar to step 3, but targeted more directly at those who have responsibility for the IT infrastructure which will support the product or process over the life cycle.
4. Evolve architecture assets. These assets could include artifacts architecture models, reference architectures, development guidelines, white papers, and structured analysis.
DAD architecture value-add
Architecture in DAD is perhaps best summarized by the value-add given as these five reasons for why have a planned project effort on architecture:
1. Common architecture enables agile teams to focus on value creation.
2. Common technical guidance enables greater consistency.
3. Agile architectures enable disaggregation
4. Common infrastructure enables continuous delivery
5. Enterprise architecture scales agile
Need more on agile architecture? Did I mention my upcoming 2nd edition to "Project Management the Agile way: making it work in the enterprise"?
Among the agile methodologies that emphasize architecture, in contravention of agile principle , which is pretty much nonsense, I like DAD (Disciplined Agile Delivery) which is more or less where Scott Adler's personal journey in agile has led him.
Architecture in DAD pretty much begins with the idea of “enterprise architecture”:
• Enterprise architecture (EA). An organization’s enterprise architecture consists of the various structures and processes of an organization, including both technical structures and processes as well as business/domain structures and processes. There is always an enterprise architecture, even when it isn’t documented.
Even though DAD allows for the EA not to be documented, a role is presumed called the Enterprise Architect who has responsibility for the enterprise architecture in whatever form it takes. Built into DAD is a purposeful collaboration between project architects—which could be a team of architects at both project office and agile teams—and the enterprise architect.
An architect team workflow is envisioned with four major tasks:
1. Envision initial architecture. The outcome is most often a model of the product or process as it will be integrated into the business. Although there could be iteration of this model, the initial model more or less sets the vision
2. Collaborate with business stakeholders. This task is an on-going level of effort which has communication at its core
3. Collaborate with IT stakeholders. Similar to step 3, but targeted more directly at those who have responsibility for the IT infrastructure which will support the product or process over the life cycle.
4. Evolve architecture assets. These assets could include artifacts architecture models, reference architectures, development guidelines, white papers, and structured analysis.
DAD architecture value-add
Architecture in DAD is perhaps best summarized by the value-add given as these five reasons for why have a planned project effort on architecture:
1. Common architecture enables agile teams to focus on value creation.
2. Common technical guidance enables greater consistency.
3. Agile architectures enable disaggregation
4. Common infrastructure enables continuous delivery
5. Enterprise architecture scales agile
Need more on agile architecture? Did I mention my upcoming 2nd edition to "Project Management the Agile way: making it work in the enterprise"?
Read in the library at Square Peg Consulting about these books I've written
Buy them at any online book retailer!
Read my contribution to the Flashblog
