Agile Architecture

Striking the balance between emergence and intentionality

The role of the Architect and the emerging (or intentional?!) Architecture in the Agile world are never-ending subjects for debate. Nevertheless, if you try to develop a large, complex system in an Agile way, or an ever-evolving system, in sustainable way, and not incur a ton of technical debt, you need Agile / Lean architecture.

This course is designed on the foundation of Agile and Lean principles to: describe the role of Agile Architects and values of Agile Architecture; explain Agile Architecture practices for both small projects and complex programs; teach participants to assess and cater for architectural and technical debt; provide advice on how to evolve from emergent to intentional architecture; foster an engineering culture of getting things done with the right speed and without compromising on quality; identify and manage waste; and maintain a continuously testable quality attributes.


Included below are the main topics covered in this training. The duration is 2/3 days.

The case for Agile Architecture

  1. The need for Agility
  2. Understand your business!
  3. Lean, Agile and Craftmanship Principles
  4. Boundaries between requirements, architecture and detailed design & implementation
  5. The architectural landscape
  6. Understanding your stakeholders
  7. What do architects do?
  8. Values important to Agile Architects

Agile Architecture practices for small projects

  1. Functional and technical spikes
  2. Experimenting on branches
  3. Growing a framework to reduce repetitive or tedious programming
  4. Understanding problem buckets

Agile Architecture practices for large projects

  1. Conway’s law
  2. Dealing with decisions. The “most” responsible moment
  3. Programs and product roadmaps
  4. Defining and using Landing Zones
  5. Set based design
  6. Architecture risk reduction backlog
  7. Managing architectural tasks

How to manage risks

  1. Wayfinding
  2. Prototyping

Architecture and Technical Debt

  1. Technical Debt
  2. Architecture Debt
  3. Measuring Debt
  4. The Consequences of Ongoing Debt
  5. Debt Reduction Strategies

Testing architecture qualities

  1. What are Architecture qualities
  2. Writing Quality Scenarios
  3. Availability, Modifiability, Performance, Security, Usability…

Keeping architecture real, explaining system views

  1. Functional/ logical view
  2. The development/structural view
  3. Concurrency/process/runtime/thread view
  4. The physical/deployment/install view
  5. The operational view
  6. The information view
  7. Explaining and documenting the architecture

About the trainers

Florin Cardasim is a software architect and Agile coach. Beyond his technical skills, he gained a broad experience as a trainer for companies and speaker in conferences. Florin is passionate by technology and by working with people to construct amazing things; focused on client and team, quality and on-time delivery while carefully looking to keep inside the fun of the software development. He is fortunate to be part of the Microsoft Regional Director program, a group of technology experts recognized by Microsoft for their passion about sharing their knowledge with the community. Worldwide, there are less than 150 RDs.

Gabriel Enea is a Microsoft Most Valuable Professional with an experience of over 15 years in software development and one of those developers for whom work is an art. Along the way, he took different roles, from software developer to technical lead and he is a real advocate for good architecture and Agile practices. His specialisations include important areas such as enterprise web development, distributed systems, online payments, ecommerce, health care, and project management.