Agile Architecture by James Copien in Vienna January 16, 2008

Agile Architecture is not Fragile Architecture!

There is a popular misconception that Agile development means not doing architecture, yet every major school of Agile practice advocates architecture. You can do a great Agile architecture in one week or in a single sprint, and overwhelming industry experience with Scrum bears out a return on investment before the end of your third sprint! In this course, designed as a one-day addendum to the Scrum course, we'll teach you how great projects do architecture the Agile way.

The course focuses in interactive systems and draws from a broad range of sources including Trygve Reenskaug's work on architectural underpinnings of MVC, Jim Coplien's lightweight domain analysis, dressed-down Use Cases, CRC cards, and role-basesd development. The course is for architects, designers, and programmers, and is programming-language neutral.

You'll learn:

* Why architecture is perhaps more crucial to Agile development than to conventional development;
* How to adapt Agile techniques so that they are supported by a good architecture, rather than doing damage to the architecture
* How to sustain a business object architecture and domain object architecture that support each other
* An overall development framework that reduces cost and has prospects for increasing revenues
* How to reduce risk with eager decision-making strategies
* The importance of "factoring" and "re-factoring"

Outline

1. Introduction
2. Time and Time to Market: Motivating Architecture's Value
1. YAGNI Re-visited
2. Case studies and models of profitability with and without up-front work
3. Architecture and Technique
1. The Potential for TDD to erode architecture — and the remedy
2. Symbiosis between architecture and usability: MVC foundations and business objects
3. The link from architecture to functional requirements and Use Cases
4. Architecture and Maintainability
1. Lightweight Domain Modeling
2. How much architecture?
3. Software Families
4. Commonality and Variability Analysis
5. The MVC-U Four-Layer Architecture
1. Business Objects and Domain Modeling
2. Business Objects as Tools
6. Architecture in Process
1. Incremental Architectural Slices
2. How much architecture, and when?
7. Summary and wrapup

Official Website: http://www.sprint-it.com/index.php?action=training&id=92