Classic architecture usually fits in quite nicely into waterfall methodologies. It involves big design up front where all of the questions for a project’s life cycle are asked and answered. Design documents are written up and handed down from on high to be the sole source of technical specification for all things to come. Architects were looked at as being technical demigods whose authority you didn’t question when they carved their thoughts into UML.
This doesn’t work well in agile environments. It would seem that to be successful in an agile environment, an architect would need to change his or her practices… even give up some power and share it. How does an architect allow the team to take ownership of architecture and design… and still keep an eye on the big picture?
This discussion isn’t just for architects, though. Everyone in an organization will, or at least should, have contact with an architect from time to time. Come join the conversation to help us understand how the field of architecture has changed in agile environments.
Geoff Meyer, Test Architect, Dell
Jason Harmon, Senior Technical Architect, AT&T
Ryan Vanderwerf, Chief Architect, ReachForce
David Sheth, Chief Architect, Calavista Software
Eric Stewart, CTO, Agile Velocity
Date/Time: 11/13/12 6:00 pm – 9:00 pm
Venue: BancVue, 4516 Seton Center Pkwy, Suite 300, Austin, TX 78759
To Register (and for more info): http://www.eventbrite.com/event/4744437741.