© 2015 IHS @AGILECHRISYYC
what is the role of an
architect in an agile
organization?
1
The Agile Architect / October 2015
Information | Analytics | Expertise
© 2015 IHS @AGILECHRISYYC
Chris Edwards P.Eng., Senior Manager
Chris.Edwards@ihs.com
@AgileChrisYYC
THE AGILE ARCHITECT
Our Experience in Discovering a Successful Pattern
OCTOBER 2015
© 2015 IHS @AGILECHRISYYC
Architecture
Approach 1:
Laissez Faire
3
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
empowerment is more
than just taking your
hands off the wheel
4
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
how do we incorporate
an architect…
without
sacrificing agile values?
5
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
Wanted to avoid this:
6
The Agile Architect / October 2015
Requirements
Design
Code
Test
Deploy
© 2015 IHS @AGILECHRISYYC
And this:
7
The Agile Architect / October 2015
cliparthut.com
© 2015 IHS @AGILECHRISYYC
Architecture
Approach 2:
The Architecture
Scout
8
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC 9
The Agile Architect / October 2015
Architecture by Example
”“
© 2015 IHS @AGILECHRISYYC 10
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
what if the
architect is
WRONG?
11
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
how do you know
if the architect
is WRONG?
12
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC 13
The Agile Architect / October 2015
I thought you knew
something I didn’t
”
“
© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
xkcd.com
© 2015 IHS @AGILECHRISYYC
architect is a
leadership role
15
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC 16
The Agile Architect / October 2015
Image Source: worklifematters.netSpotify Engineering Videos
© 2015 IHS @AGILECHRISYYC
how do I serve the
teams without telling
them what to do?
17
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
Intent Based
Leadership
18
The Agile Architect / October 2015
Rob van Hilten, Flickr
© 2015 IHS @AGILECHRISYYC 19
The Agile Architect / October 2015
Don’t move information to authority,
move authority to the information
”
“ David Marquet
© 2015 IHS @AGILECHRISYYC 20
The Agile Architect / October 2015
These are the two pillars that need to be in place:
the technical competence …. and organization clarity.
And you put those things in place
and then you can give control.
”
“
David Marquet
© 2015 IHS @AGILECHRISYYC
i intend to…
21
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC 22
The Agile Architect / October 2015
Image Source: worklifematters.netSpotify Engineering Videos
© 2015 IHS @AGILECHRISYYC
Architecture
Approach 3:
The Architecture
Coach
23
The Agile Architect / October 2015
Rob van Hilten, Flickr
© 2015 IHS @AGILECHRISYYC
Daily Design Meeting • 30 minutes
• Technical lead from each team
• Discuss challenges that being encountered
• Exercise is repeated on the team that brought
the challenge
24
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
questions
communicate
values
25
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC 26
The Agile Architect / October 2015
Resist the urge to provide solutions.
”
“ David Marquet
© 2015 IHS @AGILECHRISYYC
letting go is hard
27
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC 28
The Agile Architect / October 2015
organizations which design systems ... are constrained to
produce designs which are copies of the communication
structures of these organizations
”
“
M. Conway
© 2015 IHS @AGILECHRISYYC 29
The Agile Architect / October 2015
Image Source: worklifematters.netSpotify Engineering Videos
© 2015 IHS @AGILECHRISYYC
Architecture
Approach 3:
The Architecture
Coach
30
The Agile Architect / October 2015
Rob van Hilten, FlickrCoaching Agile Teams, Lyssa Adkins
© 2015 IHS @AGILECHRISYYC
Focus on Interests
Rather than Positions
31
The Agile Architect / October 2015
Rob van Hilten, Flickr
© 2015 IHS @AGILECHRISYYC
Design Steps • What is the problem you’re trying to solve?
• What solutions should we consider?
• What are the pros/cons of each solution?
32
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
create a common framework
for resolving conflict
33
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
disagreement is a
mechanism for
organizational clarity
34
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
the end?
35
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
something interesting
happened
36
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC 39
The Agile Architect / October 2015
?
© 2015 IHS @AGILECHRISYYC
do we still need an
architect?
40
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
Final Architecture
Approach:
Architecting as a
Team
41
The Agile Architect / October 2015
Steve Jurvetson, Flickr
© 2015 IHS @AGILECHRISYYC 42
The Agile Architect / October 2015
Image Source: worklifematters.netSpotify Engineering Videos
© 2015 IHS @AGILECHRISYYC
Summary • Empowerment is more than standing back
• Lead through intent
• Resist the urge to provide solutions
• Build relationships between teams
• Create a framework for disagreement
• Disagreement is a mechanism for
organizational clarity
43
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
leadership skills are
vital to an architect’s
success
44
The Agile Architect / October 2015
© 2015 IHS @AGILECHRISYYC
Questions? Chris Edwards
Chris.Edwards@ihs.com
@AgileChrisYYC
45
The Agile Architect / October 2015

The Agile Architect - CAMUG - Oct 1, 2015

  • 1.
    © 2015 IHS@AGILECHRISYYC what is the role of an architect in an agile organization? 1 The Agile Architect / October 2015
  • 2.
    Information | Analytics| Expertise © 2015 IHS @AGILECHRISYYC Chris Edwards P.Eng., Senior Manager Chris.Edwards@ihs.com @AgileChrisYYC THE AGILE ARCHITECT Our Experience in Discovering a Successful Pattern OCTOBER 2015
  • 3.
    © 2015 IHS@AGILECHRISYYC Architecture Approach 1: Laissez Faire 3 The Agile Architect / October 2015
  • 4.
    © 2015 IHS@AGILECHRISYYC empowerment is more than just taking your hands off the wheel 4 The Agile Architect / October 2015
  • 5.
    © 2015 IHS@AGILECHRISYYC how do we incorporate an architect… without sacrificing agile values? 5 The Agile Architect / October 2015
  • 6.
    © 2015 IHS@AGILECHRISYYC Wanted to avoid this: 6 The Agile Architect / October 2015 Requirements Design Code Test Deploy
  • 7.
    © 2015 IHS@AGILECHRISYYC And this: 7 The Agile Architect / October 2015 cliparthut.com
  • 8.
    © 2015 IHS@AGILECHRISYYC Architecture Approach 2: The Architecture Scout 8 The Agile Architect / October 2015
  • 9.
    © 2015 IHS@AGILECHRISYYC 9 The Agile Architect / October 2015 Architecture by Example ”“
  • 10.
    © 2015 IHS@AGILECHRISYYC 10 The Agile Architect / October 2015
  • 11.
    © 2015 IHS@AGILECHRISYYC what if the architect is WRONG? 11 The Agile Architect / October 2015
  • 12.
    © 2015 IHS@AGILECHRISYYC how do you know if the architect is WRONG? 12 The Agile Architect / October 2015
  • 13.
    © 2015 IHS@AGILECHRISYYC 13 The Agile Architect / October 2015 I thought you knew something I didn’t ” “
  • 14.
    © 2015 IHS@AGILECHRISYYC The Agile Architect / October 2015 xkcd.com
  • 15.
    © 2015 IHS@AGILECHRISYYC architect is a leadership role 15 The Agile Architect / October 2015
  • 16.
    © 2015 IHS@AGILECHRISYYC 16 The Agile Architect / October 2015 Image Source: worklifematters.netSpotify Engineering Videos
  • 17.
    © 2015 IHS@AGILECHRISYYC how do I serve the teams without telling them what to do? 17 The Agile Architect / October 2015
  • 18.
    © 2015 IHS@AGILECHRISYYC Intent Based Leadership 18 The Agile Architect / October 2015 Rob van Hilten, Flickr
  • 19.
    © 2015 IHS@AGILECHRISYYC 19 The Agile Architect / October 2015 Don’t move information to authority, move authority to the information ” “ David Marquet
  • 20.
    © 2015 IHS@AGILECHRISYYC 20 The Agile Architect / October 2015 These are the two pillars that need to be in place: the technical competence …. and organization clarity. And you put those things in place and then you can give control. ” “ David Marquet
  • 21.
    © 2015 IHS@AGILECHRISYYC i intend to… 21 The Agile Architect / October 2015
  • 22.
    © 2015 IHS@AGILECHRISYYC 22 The Agile Architect / October 2015 Image Source: worklifematters.netSpotify Engineering Videos
  • 23.
    © 2015 IHS@AGILECHRISYYC Architecture Approach 3: The Architecture Coach 23 The Agile Architect / October 2015 Rob van Hilten, Flickr
  • 24.
    © 2015 IHS@AGILECHRISYYC Daily Design Meeting • 30 minutes • Technical lead from each team • Discuss challenges that being encountered • Exercise is repeated on the team that brought the challenge 24 The Agile Architect / October 2015
  • 25.
    © 2015 IHS@AGILECHRISYYC questions communicate values 25 The Agile Architect / October 2015
  • 26.
    © 2015 IHS@AGILECHRISYYC 26 The Agile Architect / October 2015 Resist the urge to provide solutions. ” “ David Marquet
  • 27.
    © 2015 IHS@AGILECHRISYYC letting go is hard 27 The Agile Architect / October 2015
  • 28.
    © 2015 IHS@AGILECHRISYYC 28 The Agile Architect / October 2015 organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations ” “ M. Conway
  • 29.
    © 2015 IHS@AGILECHRISYYC 29 The Agile Architect / October 2015 Image Source: worklifematters.netSpotify Engineering Videos
  • 30.
    © 2015 IHS@AGILECHRISYYC Architecture Approach 3: The Architecture Coach 30 The Agile Architect / October 2015 Rob van Hilten, FlickrCoaching Agile Teams, Lyssa Adkins
  • 31.
    © 2015 IHS@AGILECHRISYYC Focus on Interests Rather than Positions 31 The Agile Architect / October 2015 Rob van Hilten, Flickr
  • 32.
    © 2015 IHS@AGILECHRISYYC Design Steps • What is the problem you’re trying to solve? • What solutions should we consider? • What are the pros/cons of each solution? 32 The Agile Architect / October 2015
  • 33.
    © 2015 IHS@AGILECHRISYYC create a common framework for resolving conflict 33 The Agile Architect / October 2015
  • 34.
    © 2015 IHS@AGILECHRISYYC disagreement is a mechanism for organizational clarity 34 The Agile Architect / October 2015
  • 35.
    © 2015 IHS@AGILECHRISYYC the end? 35 The Agile Architect / October 2015
  • 36.
    © 2015 IHS@AGILECHRISYYC something interesting happened 36 The Agile Architect / October 2015
  • 37.
    © 2015 IHS@AGILECHRISYYC 39 The Agile Architect / October 2015 ?
  • 38.
    © 2015 IHS@AGILECHRISYYC do we still need an architect? 40 The Agile Architect / October 2015
  • 39.
    © 2015 IHS@AGILECHRISYYC Final Architecture Approach: Architecting as a Team 41 The Agile Architect / October 2015 Steve Jurvetson, Flickr
  • 40.
    © 2015 IHS@AGILECHRISYYC 42 The Agile Architect / October 2015 Image Source: worklifematters.netSpotify Engineering Videos
  • 41.
    © 2015 IHS@AGILECHRISYYC Summary • Empowerment is more than standing back • Lead through intent • Resist the urge to provide solutions • Build relationships between teams • Create a framework for disagreement • Disagreement is a mechanism for organizational clarity 43 The Agile Architect / October 2015
  • 42.
    © 2015 IHS@AGILECHRISYYC leadership skills are vital to an architect’s success 44 The Agile Architect / October 2015
  • 43.
    © 2015 IHS@AGILECHRISYYC Questions? Chris Edwards Chris.Edwards@ihs.com @AgileChrisYYC 45 The Agile Architect / October 2015