One of the things I’ve learned from Agile methods: Deliver Early, Deliver Often, Take Feedback, Iterate.
When you do, your perception of value goes up, and you build trust with the customer, especially if they are not sure you are doing what they want done.
Building an Enterprise Architecture, in a company that is not used to having an Enterprise Architecture, can sometimes be frustrating. Our team is constantly fighting the battle to be relevant, engaged, ‘actionable’ and yet still high-level enough to span the enterprise.
My one bit of advice, for any level of EA, comes from Agile methods: Deliver Early, Deliver Often, Take Feedback, and Iterate.
It is all too tempting to do the ‘waterfall’ thing: take a long time, deliver something you think is cool, and spend years selling it to people who don’t care. I’ve heard many stories told of that model. We avoid that by being Agile.
Nick,
This is a really great post. And let me just take the moment to publicly thank you for continuously putting out good material for the community. I’ve learned a lot, and I’m sure a lot of other people have as well. You Rock!
Evan
PingBack from http://msdnrss.thecoderblogs.com/2007/08/23/agile-enterprise-architecture/
PingBack from http://msdnrss.thecoderblogs.com/2007/08/23/agile-enterprise-architecture/
PingBack from http://msdnrss.thecoderblogs.com/2007/08/23/agile-enterprise-architecture/
I agree to you both. Good thought about EA+Agile (can be elaborated at length), and yes you often produce interesting new perspectives (like this one). Please, keep it up!
Enterprise Architecture Actionable Enterprise Architecture through Feedback Business Case for Integration, part two The One Business Case for Integration Agile Enterprise Architecture Master Data Management: Minimizing the Complexity Carnival of Enterprise