Architectural Envisioning on Agile Projects |
 |
| Tuesday, 08 April 2008 12:11 |
 One of
the common misperceptions with agile software development is that agilists
don't "do architecture." This completely
ignores the 11th principle of the Agile
Manifesto which states that the best architectures evolve over
time. More importantly, when you observe
agile teams in action, you find that the majority of them do some initial
architecture modeling at the beginning of the project. But, perhaps because agilists are not
creating detailed architectural specifications as the result of a "big design
up front" (BDUF) approach, many people think that we're not doing
architecture. Nothing can be further
from the truth, and in this article I overview an agile best practice called
"architecture envisioning" which enables you to gain the value from modeling
without the cost of needless documentation.
One of
the common misperceptions with agile software development is that agilists
don't "do architecture." This completely
ignores the 11th principle of the Agile
Manifesto which states that the best architectures evolve over
time. More importantly, when you observe
agile teams in action, you find that the majority of them do some initial
architecture modeling at the beginning of the project. But, perhaps because agilists are not
creating detailed architectural specifications as the result of a "big design
up front" (BDUF) approach, many people think that we're not doing
architecture. Nothing can be further
from the truth, and in this article I overview an agile best practice called
"architecture envisioning" which enables you to gain the value from modeling
without the cost of needless documentation.
Read more >>
Set as favorite
Bookmark
Email this
Hits: 1242 Trackback(0)Comments (0)
|
TrackBack URI for this entry
Subscribe to this comment's feed