Agile Architecture Workshop: An Incremental Approach

Let your architecture emerge at Rebecca Wirfs-Brock‘s workshop.

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.

In this workshop, Rebecca Wirfs-Brock provided a hands-on experience applying practices and techniques for effectively defining (and refining) software architecture that support agile values. She focuses on methods for balancing software architecture activities with other ongoing development efforts. Learn tactics for creating just enough architecture at the most opportune time.

Why Attend

  • 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

Testimonials

“Great workshop Rebecca! Really good and new information here for me.” – Sorin O., Technical Architect

“There was an excellent presentation. I found it very interesting and help me a lot. Thank you Rebecca!” – Dana D., Team Leader

“Thanks a lot — the class and the organizing were excellent!!!” – Florin C., Technical Architect

Who Should Attend

  • Product Architects
  • Technical Architects
  • Program Managers
  • Testers
  • Developers
  • Team Leaders
  • Any interdisciplinary product or cross-functional team working in an agile way

Practical Details

  • Language: English
  • Experiential, hands-on, interactive online learning with practical examples
  • Participants will be awarded a Mozaic Works certificate of completion

This Learning Program is Available on Demand

    Agenda

    • Agile Values. Qualities of good architecture.
    • What is different about architecture on agile projects?

    Agile Architecture for Small Projects

    • Patterns for incremental architecture
    • Rhythms of development. Design spikes

    Agile Architecture for Larger Projects, Products, and Programs

    • Understanding project and system complexities. Using product and feature roadmaps.
    • Identifying risks and risk horizons. Critical decisions and “responsible” moments.
    • Options for fitting architecture activities into an agile project

    Architecture Practices to Reduce Risk

    • Wayfinding, exploration and prototyping. Testing system qualities
    • Monitoring and reducing technical and architecture debt

    Techniques and Practices for Projects and Programs

    • Defining and using a landing zone. Identifying risks and risk horizons.
    • Alternatives for fitting architecture activities into an agile project.
    • Backlogs, architecture tasks, architecture work queues, design spikes.
    • Kanban: A lean practice for agile tasks.
    • Defining acceptance criteria for architecture qualities.
    • Monitoring technical and architectural debt

    What Agile Architects Do

    • Balance, optimize, and align stakeholder goals.
    • Keep the system “soft” and able to absorb changes.
    • Identify architectural risks.
    • Develop common practices. Lead by doing—finding a balance

    Keeping the Architecture Alive

    • Explaining architecture to others. Selling architecture ideas.
    • Giving and receiving constructive design criticism.
    • Drawing and sketching for agile architects.
    • Architecture stewardship

    Approximately 50% of the time is spent doing and reviewing short exercises; 50% in short lectures. This course combines short presentations introducing new concepts and techniques with short, to-the-point exercises. In addition to course slides, attendees receive notes describing each technique, concept, or practice.

    Prerequisites

    Attendees should have familiarity with agile software practices and be experienced with software programming and development.

    Meet Your Trainers

    Rebecca Wirfs – Brock

    Rebecca Wirfs – Brock

    Mentor and Consultant on Responsibility-Driven Design, Architecture, Decision Making, Design Heuristics, Domain Modeling, and Agile Practices

    Rebecca Wirfs-Brock, president of Wirfs-Brock Associates and IEEE Software’s Design Columnist, is a well-known and respected object-oriented practitioner. She invented the way of thinking about objects known as Responsibility-Driven Design and is the lead author of Object Design: Roles, Responsibilities, and Collaborations (2003) and the classic Designing Object-Oriented Software (1990). Through her writing, teaching, consulting, and speaking she popularizes the use […]
    More about Rebecca Wirfs – Brock >
    0
      0
      Your Cart
      Your cart is empty
        Apply Coupon
        Scroll to Top