Post on 15-Apr-2017
transcript
1© 2015 IHS @AGILECHRISYYC
what is the role of an architect in an agile
organization?
The Agile Architect / October 2015
Information | Analytics | Expertise
© 2015 IHS @AGILECHRISYYC
Chris Edwards P.Eng., Senior ManagerChris.Edwards@ihs.com @AgileChrisYYC
THE AGILE ARCHITECT
Our Experience in Discovering a Successful Pattern
OCTOBER 2015
© 2015 IHS @AGILECHRISYYC 3
ArchitectureApproach 1:Laissez Faire
The Agile Architect / October 2015
4© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
empowerment is morethan just taking yourhands off the wheel
5© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
how do we incorporatean architect…
without sacrificing agile values?
© 2015 IHS @AGILECHRISYYC 6
Wanted to avoid this:The Agile Architect / October 2015
Requirements
Design
Code
Test
Deploy
© 2015 IHS @AGILECHRISYYC 7
And this:The Agile Architect / October 2015
cliparthut.com
© 2015 IHS @AGILECHRISYYC 8
ArchitectureApproach 2:The Architecture Scout
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
11© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
what if thearchitect isWRONG?
12© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
how do you knowif the architect
is WRONG?
© 2015 IHS @AGILECHRISYYC 13
The Agile Architect / October 2015
I thought you knewsomething I didn’t
”“
© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
xkcd.com
15© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
architect is a leadership role
© 2015 IHS @AGILECHRISYYC 16
The Agile Architect / October 2015
Image Source: worklifematters.netSpotify Engineering Videos
17© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
how do I serve the teams without telling
them what to do?
© 2015 IHS @AGILECHRISYYC 18
Intent Based Leadership
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
21© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
i intend to…
© 2015 IHS @AGILECHRISYYC 22
The Agile Architect / October 2015
Image Source: worklifematters.netSpotify Engineering Videos
© 2015 IHS @AGILECHRISYYC 23
ArchitectureApproach 3:The Architecture Coach
The Agile Architect / October 2015
Rob van Hilten, Flickr
© 2015 IHS @AGILECHRISYYC 24
The Agile Architect / October 2015
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
25© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
questionscommunicate
values
© 2015 IHS @AGILECHRISYYC 26
The Agile Architect / October 2015
Resist the urge to provide solutions.
”“David Marquet
27© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
letting go is hard
© 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 30
ArchitectureApproach 3:The Architecture Coach
The Agile Architect / October 2015
Rob van Hilten, FlickrCoaching Agile Teams, Lyssa Adkins
© 2015 IHS @AGILECHRISYYC 31
Focus on InterestsRather than Positions
The Agile Architect / October 2015
Rob van Hilten, Flickr
© 2015 IHS @AGILECHRISYYC 32
The Agile Architect / October 2015
Design Steps • What is the problem you’re trying to solve?
• What solutions should we consider?
• What are the pros/cons of each solution?
33© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
create a common frameworkfor resolving conflict
34© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
disagreement is amechanism for
organizational clarity
35© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
the end?
36© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
something interestinghappened
© 2015 IHS @AGILECHRISYYC 39
The Agile Architect / October 2015
?
40© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
do we still need an architect?
© 2015 IHS @AGILECHRISYYC 41
Final Architecture Approach:Architecting as a Team
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 43
The Agile Architect / October 2015
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
44© 2015 IHS @AGILECHRISYYC
The Agile Architect / October 2015
leadership skills are vital to an architect’s
success
© 2015 IHS @AGILECHRISYYC 45
Questions? Chris Edwards
Chris.Edwards@ihs.com
@AgileChrisYYC
The Agile Architect / October 2015