Agile Architecture

Architecture as a Structure Agile Architecture

No more No more
The organization of a system, Flexible structure
spaghetti code isolated &
& Big Ball Big Upfront its sub-systems created just in time
of Mud Design and their relations. to enable value flow.

in a Nutshell
To Architect Architect to Enable Value Flow The Architect
Version 1.0

In a step-by-step approach Architecture is an art of continually

improving value flow through
“Organizations, who design systems, are constrained to
produce designs which are copies of the communication
Emergent design can lead to
short lead times initially, but
Receiver
must
Visualizes It's creative
understand and fun!
technology, by balancing emergent structures of these organizations." disastrous consequences due to
Principles are guiding and intentional design, and realizing poor quality in the long run. Level of
stars to move from business value while overcoming abstraction
current state towards 1
constraints in the current situation. Intentional design can lead to Context
Principles the vision.
long lead times and design 2 Container
Without agile architecture, detached from reality, due to too 3
Constraints Business Value Intentional Component
there will be no business agility. Emergent much upfront design.
• Conway’s Law • Time-to-Market Design 4
design Code Draw architecture
• Tech Debt • Quality (NFRs) diagrams, and think
• New Tech like a developer
• Visualize together
Now Next Later Vision "We want

Take a Business & Product First Approach

"We must awesome • Create maps with different levels of details depending
Understand Next, "slice" to Hypothesis, not a Long-term re-organize!" products!" on the target group
current create customer detailed solution, architecture • Use a whiteboard and a common notation, e.g. C4 Model
architecture, value and to create value in vision, The BAPO Model states that the business & product strategy (B) should drive architecture and tech (A).
business establish new upcoming "slices" rather than a These should in turn drive process, ways of working & tooling (P). • Visualize “pain points” that inhibit flow first.
expectations, architecture, detailed target These should be used to define the organization (O) to realize the product and tech strategy.
pain points and
opportunities
step-by-step architecture
Managers Customers
Creates a Toolbox
Design the toolbox based on the needs of the
Larger technical leaps 4. “Let’s hope we get some 1. “A new organization 1. Begin with business & the awesome 4. Organize to create value, e.g. product,
organisation and the teams.
products & services out of this...” will solve our problems” products & services that customers love enabling, specialist and platform teams.
"We need Principles Shared rules and guidelines
help!" (6-9 months) Standards Preferred tech, e.g. Tech Radar
Now Leap Later B O B O
Reference Models Common language and concepts,
Customer value Customer value Customer value
e.g. C4 Model
Technical Debt

VS
A A Templates Decisions, principles, visuals, etc.
Product team 3. “But why is it so 2. Architect to
difficult? The tech enable these sweet Patterns Pre-tested design and tech combinations
is in our way!” products & services
Implementation guides Developer manuals (when needed)
OPAB BAPO
X-as-a-Service X-as-a-Service X-as-a-Service
Modernization Reusable components Repository of services, components
Platform team
Technical Debt "We're Organization Business and source code, e.g. Design system
happy
Process Architecture
"We're now!" P P
Is a Trusted Advisor
Technical Debt Architecture Process
coming to
Modernization Organization
theMindset
rescue!
Business
2. Implement process & 3. Establish process & Ways of Working
Technical Debt new Ways of Working.
Enabling team that continually increases flow An architect is a trusted advisor for
managers, product owners and
Adapt a Pace Layer Architecture
Now Leap Later
developers in architecture.
Product & Platform Temporary enabling Product & Platform
team struggle to team increases flow teams can focus A storyteller connecting the dots from business
deliver customer by reducing more on customer A Pace Layer Architecture is a Experience Experience
Customer focused products
value, services, technical debt and value and technical stack that enables efficient External APIs to develop and services. value to components and code, who:
technical debt & taking larger X-as-a-Service. digital products and services
development of digital products and in an ecosystem.
modernization. tehnical steps. Domains Domains Reusable business logic. • Is part of early stages of business strategy and planning.
services.
Alignment The layers encapsulates code that
Internal APIs to simplify data
exchange internally and an The gold of the digital age.
• Coaches teams to make them able to architect themselves.
• Is a tech advisor for urgent and complex architecture challenges.
Team Assessment Data Data
Teams assess themselves based on "We build
belongs together and is losely enabler to be data driven
• Fosters an agile mindset and encourages continually improving
shared values, principles & standards. green, coupled to underlying complexity
not red!" Developer portals and platforms flow, e.g. through DevOps.
to ensure correct, efficient, reusable, Platforms
Platforms Platforms to eliminate friction through
Coaching • Has deep insight into business, products, cloud, tech,
Architect works close to the teams
configurable development. standardisation & automation.
and educates and coaches them to development and operations.
increase flow through technology.
Encourage a DevOps Culture • Takes necessary decisions.
Self-service
An architect is an evangelist for a DevOps
The teams assess by using predefined Dev Ops Dev Ops DevOs
questionnaires and get support from culture and continually contributes to Infographic Poster by:
architect when needed. decreasing the divide and friction between robert.nordh@dandypeople.com
development and operations, by exploring new 1. Decreasing the divide 2. Bridging the divide 3. DevOps Teams with support from the Dandy team
Architecture Review Board
Try to avoid. Only for complex and Ways of Working, standardization, automation Encourage Dev & Ops to collaborate Automate, create developer services Establish teams that manage
unexplored architectural challenges. and establishing DevOps teams. upstream, standardize and share and establish fast feedback loops. development, infrastructure & Free download:
Must be solution oriented. knowledge. operations. dandypeople.com/blog

C4 Model by Simon Brown The BAPO Model by Jan Bosh