Architecture In An Agile Organization

Last night, my colleague Chris Sterling gave a presentation about Architecture In An Agile Organization. He raised several points I want to develop over the next few posts.

One of the most abused principles in agile software development is that of avoiding Big Design Up Front (BDUF). No BDUF does not mean NoDUF!

Architects are usually quite pre-occupied with ensuring that architectural guidelines and requirements are adhered to during development yet, always struggle to justify them. What does the customer think non-functional requirements mean? No, it's not just semantics.

Architecture is not all about technology. I'm going to start calling this the Paint Yourself Into The Corner pattern. You read it here, first.

Requirements are not specifications. Seriously, there is a difference!