what_is_the_difference_between_emergent_and_intentional_architecture
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| what_is_the_difference_between_emergent_and_intentional_architecture [2019/03/19 09:06] – created hpsamios | what_is_the_difference_between_emergent_and_intentional_architecture [2022/07/21 08:52] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Early implementations of agile often seem to hide the need for good design. Most of the time the assumption was that “if you have good people, with a good understanding of design principles then good design will follow.” The Agile Manifesto argued that | Early implementations of agile often seem to hide the need for good design. Most of the time the assumption was that “if you have good people, with a good understanding of design principles then good design will follow.” The Agile Manifesto argued that | ||
| - | <WRAP Box>“The best architectures, | + | > “The best architectures, |
| This has proven to be true - there is a huge benefit in having the Teams do design as they do the work (assuming Teams with strong technical skills). And it has worked for many situations. But as you have more and more Teams contributing to the single solution, or as people started to apply agile into more and more existing IT situations, it became increasingly clear that something more was required. The question then became | This has proven to be true - there is a huge benefit in having the Teams do design as they do the work (assuming Teams with strong technical skills). And it has worked for many situations. But as you have more and more Teams contributing to the single solution, or as people started to apply agile into more and more existing IT situations, it became increasingly clear that something more was required. The question then became | ||
| - | <WRAP box>“How do we leverage this emergent property of design, while also keeping overall guidelines in place and doing some level of look ahead planning? | + | > “How do we leverage this emergent property of design, while also keeping overall guidelines in place and doing some level of look ahead planning? |
| SAFe in particular recognized the problem and developed the notion of intentional architecture in addition to emergent architecture. One of the key ideas was that for a Train program that the System Architect works with the Teams to build an “architectural runway” of new “enablers” that enables the Train to develop new capabilities better, faster, and cheaper. | SAFe in particular recognized the problem and developed the notion of intentional architecture in addition to emergent architecture. One of the key ideas was that for a Train program that the System Architect works with the Teams to build an “architectural runway” of new “enablers” that enables the Train to develop new capabilities better, faster, and cheaper. | ||
| Line 27: | Line 27: | ||
| * De-centralized decision making: Understand when decisions need to be centralized versus de-centralized. | * De-centralized decision making: Understand when decisions need to be centralized versus de-centralized. | ||
| * Keeping options open: To maximize the data we have to make a decision and so reduce the risk of that decision. | * Keeping options open: To maximize the data we have to make a decision and so reduce the risk of that decision. | ||
| + | |||
| + | ====== Want To Know More? ====== | ||
| + | |||
| + | * [[https:// | ||
| {{tag> | {{tag> | ||
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/what_is_the_difference_between_emergent_and_intentional_architecture.1553011590.txt.gz · Last modified: 2020/06/02 14:25 (external edit)