• Understand what agile architecture is (and is not)
• Explore characteristics of an agile architecture role
• Learn techniques for planning and bounding architecting activities
• Communicate architecture to diverse audiences: The basics of communicating architecture goals and vision
• Recognize and manage architectural debt
Two commonly heard phrases in agile development are “Let your architecture emerge” and “Always implement what you actually need, never what you think you might need.” However, complex software systems have lots of moving parts, dependencies, challenges, and unknowns. Counting on the software architecture to properly evolve without any planning or design investigations can be risky. On agile projects, software architecture activities should not be pie-in-the-sky experiments that slow down the delivery of working code. Yet producing working code based on a shaky architecture isn’t sustainable either.
Effectively Define and Refine Software Architecture
Johanna Rothman and Rebecca Wirfs-Brock provide a hands-on experience applying practices and techniques for effectively defining (and refining) software architecture that support agile values. They focus on methods for balancing software architecture activities with other ongoing development efforts. Learn tactics for creating just enough architecture at the most opportune time.
Who Should Attend?
Enterprise architects, product architects, technical architects, program managers, testers, developers, team leaders, or any interdisciplinary product or cross-functional team working in an agile way
About the Instructors:
Johanna Rothman consults, speaks, and writes on managing high-technology product development. She has helped engineering organizations, IT organizations, and startups hire technical people, manage projects, and release successful products faster. Johanna is the author of the Manage Your Project Portfolio: Increase Your Capacity and Finish More Projects; 2008 Jolt Productivity Award winner Manage It! Your Guide to Modern, Pragmatic Project Management; Hiring the Best Knowledge Workers, Techies & Nerds: The Secrets and Science of Hiring Technical People; and co-author (with Esther Derby) of the pragmatic Behind Closed Doors: Secrets of Great Management. Johanna is a host of the Amplifying Your Effectiveness (AYE) conference.
Rebecca Wirfs-Brock is an internationally recognized leader in the development of practical design methodologies. She invented the set of development practices known as responsibility-driven design. Among her widely used innovations are use case conversations and object role stereotypes. Wirfs-Brock has written, lectured, and presented tutorials on object design, adaptive architecture styles, and management topics. She is lead author of Designing Object-Oriented Software and Object Design: Roles, Responsibilities and Collaborations. She served four years as IEEE Software's editor of the Design column and is a past board member of the Agile Alliance. She frequently helps product engineering, IT, and startup organizations with the technical bits as well as with effective teamwork and agile development practices. She consults, speaks, and writes on practical techniques for thinking about, designing, discussing, implementing, and describing software. Rebecca blogs about software design and agile practices at The Responsible Designer. You can find her design columns, papers, and presentations at wirfs-brock.com/Resources.html.
This course is conveniently located with the Better Software Conference. Register for Agile Architecture Workshop training for $1,495 or expand for a full week of learning by adding a Tuesday tutorial plus conference registration on Wednesday and Thursday and SAVE $500! Call the Client Support Group at 888.268.8770 or 904.278.0524 or email firstname.lastname@example.org for more information. Can’t attend the conference but want to attend this training? Click Here to be redirected.
Qualities of good architecture
What is different about architecture on agile projects?
Agile Architecture for Small Projects
Patterns for incremental architecture
Rhythms of development
The Architecture Landscape for an Agile Project
Understanding project and system complexities
Implementation and development support
Stakeholder values and needs
Techniques and Practices for Projects and Programs
Defining and using a landing zone
Identifying risks and risk horizons
Critical decisions and “responsible” moments
Alternatives for fitting architecture activities into an agile project
Backlogs, architecture tasks, architecture work queues, design spikes
Bounded design investigations and prototyping
Defining acceptance criteria for architecture qualities
Monitoring technical and architectural debt
What Architects Do
Balance, optimize, and align stakeholder goals
Communicate architecture to diverse audiences
Keep the system “soft” and able to absorb changes
Identify architectural risks
Develop prototypes and common practices
Sell design approaches to decision-makers
Mitigate technical debt