Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Panel: Practical Open Agile Architecture standard and Domain-Driven Design @Xebia Academy Webinar Week 2020

João Rosa
December 08, 2020

Panel: Practical Open Agile Architecture standard and Domain-Driven Design @Xebia Academy Webinar Week 2020

The Open Group recently published the Open Agile Architecture™ standard, which offers an approach to architects at scale with agility. It provides guidance and best practices for Enterprise Architects seeking to transition into Agile and Digital contexts. It also puts a focus on Domain-Driven Design as an approach to software delivery. In this panel, our Xebia experts will discuss the importance of using this standard in any modern IT architecture. So curious why Enterprise Architecture and Domain-Driven Design are such a good match? Come join this panel and find out the value for your organisation and where to start using the Open Agile Architecture standard and Domain-Driven Design yourself!

João Rosa

December 08, 2020
Tweet

More Decks by João Rosa

Other Decks in Technology

Transcript

  1. Panel: Practical Open
    / Agile Architecture standard
    and Domain-Driven
    \ Design

    View full-size slide

  2. / Meet our Experts
    Thomas Kruitbosch,
    Kenny Baas-Schwegler,
    João Rosa, Edo Poll,
    Winfried Scheulderman
    Webinar
    / Week
    Connecting
    \ Expertise

    View full-size slide

  3. Enterprise Architecture trail through O-AA
    • Organization as a system: agent in a bigger system
    • Observe from the outside: product portfolio
    • Looking at a product
    • Products are delivered by value streams
    • Value streams mapped on business capabilities

    View full-size slide

  4. Enterprise
    Trail: organization
    Product
    Product
    Product
    Product
    Enterprise
    Capabty
    Capabty
    Capabty
    Capabty
    Capabty
    Capabty
    Customer
    Supplier

    View full-size slide

  5. Organization-as-a-system
    Open Agile Architecture™
    DEF 2.5. Architecture
    Ø Architecture of systems
    DEF 2.19. Ecosystem
    Ø Organization is an agent in a
    larger system …
    Ø …and adds value in a larger
    value chain
    Axiom 2. Outside-In Thinking
    Ø The product portfolio is what is
    seen from the outside
    Cinema
    Customer Supplier


    Products
    Products

    View full-size slide

  6. Product
    Product
    Product
    Product
    Trail: product
    Product
    Product
    Product
    Product
    Enterprise
    Capabty
    Capabty
    Capabty
    Capabty
    Capabty
    Capabty
    Customer
    Supplier

    View full-size slide

  7. Zooming in: a product
    Open Agile Architecture™
    DEF 2.40. Product
    Ø Bundle of services/goods offered
    to customers
    Axiom 1. Customer Experience
    Focus
    Ø Outside-in view to meet the
    expectations of customers
    BB 13. Experience Design
    Ø Iterate through design thinking
    cycles of customer research &
    product discovery
    BB 14. Product Architecture
    Ø Assign functional elements of a
    product to its building blocks or
    product components
    “A product includes the functionality – the features. But it also includes the
    technology that enables this functionality. It also includes the user experience design
    that presents this functionality. And it includes how we monetize this functionality. It
    includes how we attract and acquire users and customers. And it can also include
    offline experiences as well that are essential to delivering the product’s value.”
    — Marty Cagan

    View full-size slide

  8. Trail: value stream
    Product
    Product
    Product
    Product
    Enterprise
    Capabty
    Capabty
    Capabty
    Capabty
    Capabty
    Capabty
    Customer
    Supplier
    Capabty
    Capabty
    Capabty

    View full-size slide

  9. Value streams deliver products
    Open Agile Architecture™
    Axiom 5. Value Stream Alignment
    Ø Identify value streams from the
    customer’s standpoint
    BB 16. Lean Value Stream Mapping
    Ø Map end-to-end activities that
    deliver value to the customer
    DEF 2.2. Alignment Diagram
    BB 15. Journey Mapping
    Ø Relate customer journey to value
    stream
    BB 19. Event Storming
    Ø Elicit implicit knowledge about
    the value streams

    View full-size slide

  10. Trail: capability
    Product
    Product
    Product
    Product
    Enterprise
    Capabty
    Capabty
    Capabty
    Customer
    Supplier
    Capabty
    Capabty
    Capabty
    Capabty

    View full-size slide

  11. Business capabilities deliver value
    Open Agile Architecture™
    Axiom 8. Loosely-Coupled Systems
    + Axiom 11. Partitioning Over
    Layering
    + Axiom 12. Organization
    Mirroring Architecture
    + BB 12.2. Autonomy and Self-
    Organization
    Ø create an agile organization, an
    adaptive organization that can be
    resilient or even anti-fragile
    Capability
    Agility requires autonomy
    Explicitly defined boundaries
    Ø Have control on what’s inside
    Ø Align with what’s outside
    → Software architecture…
    Open Agile Architecture™
    DEF 2.8. Capability
    Ø A self-contained ability of an
    organization
    BB 19. Event Storming
    + BB 20.1.1. Domains and Sub-
    Domains
    Ø To find and define (domain)
    boundaries
    BB 17. Operations Architecture
    + BB 12.3. Team Taxonomy
    Ø Designs the Target Operating
    Model (TOM)
    DEF 2.42. Product-Centric
    Organization
    Ø Systems are part of TOM, operate
    by teams, not by projects

    View full-size slide

  12. Software Architecture trail through O-AA
    • Domain-Driven Design as first class citizen
    • Modelling relationships
    • Modelling behaviour not data
    • Ports & adapters pattern: agile software for an agile architecture
    • Implementation of the boundaries
    • Unit of consistency and unit of change
    • As opposed to unit of deployment

    View full-size slide

  13. Focus on the important bits!

    View full-size slide

  14. Ubiquitous language
    (a model for a purpose)

    View full-size slide

  15. Technical concerns on the
    outside

    View full-size slide

  16. How about interaction modes?

    View full-size slide

  17. To remember…
    • Modelling is crucial to discover what is the core
    • EventStorming, Example Mapping, Responsibility Mapping, CRC, and many more
    • Changing modelling tools allows insights to emerge
    • Software architecture is the game of trade-offs
    • Discuss what is in and what is out
    • Ports & adapters pattern allows to keep the focus on the problem
    • Abstracting from the implementation (technology)
    • Discuss the boundaries: what is the unit of consistency and the unit of change
    • Avoid breaking natural boundaries for the sake of technology

    View full-size slide

  18. But how to implement? Where to start?

    View full-size slide

  19. What the
    organization
    needs
    What architecture works on
    What
    architecture
    delivers

    View full-size slide

  20. Train
    architecture
    skills
    Apply skills learned
    Evaluate results

    View full-size slide

  21. Discussion
    What the
    organization
    needs
    What architecture works on
    What
    architecture
    delivers
    Train
    architecture
    skills
    Apply skills learned
    Evaluate
    results

    View full-size slide

  22. Check our trainings
    You can check our training portfolio:
    https://xebia.com/academy/en/
    We offer trainings ranging Agile Architecture, Domain-Driven Design and DevOps

    View full-size slide