the agile architect - agile india 2016
Post on 15-Apr-2017
348 Views
Preview:
TRANSCRIPT
Information | Analytics | Expertise
© 2016 IHS @AGILECHRISYYC
Chris Edwards P.Eng., Senior ManagerChris.Edwards@ihs.com @AgileChrisYYC
THE AGILE ARCHITECT
A Case Study in Transformational Leadership
MARCH 2016
2© 2016 IHS @AGILECHRISYYC
disclaimer:this is not a talk about
architecture
The Agile Architect / March 2016
3© 2016 IHS @AGILECHRISYYC
what is the role of anarchitect in an agile
organization?
The Agile Architect / March 2016
4© 2016 IHS @AGILECHRISYYC
your mileagemay vary
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 5
The Agile Architect / March 2016
Setting the Stage • 5 teams, 5-9 each (including QA)
• Mix of Scrum/Kanban/Scrumban
• Thick Client
• C++
• Mature Codebase
• Recently Adopted Agile
• Major Project – Client / Server
6© 2016 IHS @AGILECHRISYYC
The best architectures, requirements, and designs
emerge from self-organizing teams.
The Agile Architect / March 2016
Agile Manifesto
© 2016 IHS @AGILECHRISYYC 7
ArchitectureApproach 1:Laissez Faire
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 8
The Agile Architect / March 2016
HELP!!!
9© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get the job done.
Agile Manifesto
10© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
empowerment is morethan just taking yourhands off the wheel
11© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
how do we incorporatean architect…
without sacrificing agile values?
© 2016 IHS @AGILECHRISYYC 12
Wanted to avoid this:The Agile Architect / March 2016
Requirements
Design
Code
Test
Deploy
© 2016 IHS @AGILECHRISYYC 13
And this:The Agile Architect / March 2016
cliparthut.com
© 2016 IHS @AGILECHRISYYC 14
ArchitectureApproach 2:The Architecture Scout
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 17
The Agile Architect / March 2016
Architecture by Example
”“
© 2016 IHS @AGILECHRISYYC 18
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 19
The Agile Architect / March 2016
Too many classes makes the system too complex!
Big classes make the
system unmaintainable!
© 2016 IHS @AGILECHRISYYC 20
The Agile Architect / March 2016
WORK HARDER!
21© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
what if thearchitect isWRONG?
22© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
how do you knowif the architect
is WRONG?
© 2016 IHS @AGILECHRISYYC 23
The Agile Architect / March 2016
I thought you knewsomething I didn’t
”“
24© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
architect is a leadership role
© 2016 IHS @AGILECHRISYYC 25
The Agile Architect / March 2016
xkcd.com
© 2016 IHS @AGILECHRISYYC 27
The Agile Architect / March 2016
Image Source: worklifematters.netSpotify Engineering Videos
28© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
how do I serve the teams without telling
them what to do?
© 2016 IHS @AGILECHRISYYC 29
Intent Based Leadership
The Agile Architect / March 2016
Rob van Hilten, Flickr
© 2016 IHS @AGILECHRISYYC 30
The Agile Architect / March 2016
Don’t move information to authority,
move authority to the information
”“David Marquet
© 2016 IHS @AGILECHRISYYC 31
The Agile Architect / March 2016
Image Source: worklifematters.net
© 2016 IHS @AGILECHRISYYC 32
The Agile Architect / March 2016
two pillars that need to be in place: the technical competence …. and organization clarity.
… put those things in place and then you can give control.
”“
David Marquet
33© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
i intend to…
© 2016 IHS @AGILECHRISYYC 34
The Agile Architect / March 2016
Image Source: worklifematters.netSpotify Engineering Videos
© 2016 IHS @AGILECHRISYYC 35
ArchitectureApproach 3:The Architecture Coach
The Agile Architect / March 2016
Rob van Hilten, Flickr
© 2016 IHS @AGILECHRISYYC 36
The Agile Architect / March 2016
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
© 2016 IHS @AGILECHRISYYC 37
The Agile Architect / March 2016
Resist the urge to provide solutions.
”“David Marquet
38© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
questionscommunicate
values
39© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
letting go is hard
© 2016 IHS @AGILECHRISYYC 40
The Agile Architect / March 2016
Design MeetingChallenges
• Jealousy from those who cannot attend
• Conflict remains between teams
• Design group seen as new design authority
© 2016 IHS @AGILECHRISYYC 41
The Agile Architect / March 2016
organizations which design systems ... are constrained to
produce designs which are copies of the communication
structures of these organizations
”“
M. Conway
© 2016 IHS @AGILECHRISYYC 42
The Agile Architect / March 2016
© 2016 IHS @AGILECHRISYYC 44
ArchitectureApproach 3:The Architecture Coach
The Agile Architect / March 2016
Rob van Hilten, FlickrCoaching Agile Teams, Lyssa Adkins
© 2016 IHS @AGILECHRISYYC 46
The Agile Architect / March 2016
Design Steps • What is the problem you’re trying to solve?
• What solutions should we consider?
• What are the pros/cons of each solution?
© 2016 IHS @AGILECHRISYYC 47
The Agile Architect / March 2016
Sources: Edward de Bono,retrospectivewiki.org
48© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
create a common frameworkfor resolving conflict
49© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
disagreement is amechanism for
organizational clarity
50© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
the end?
51© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
something interestinghappened
© 2016 IHS @AGILECHRISYYC 52
The Agile Architect / March 2016
?
53© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
do we still need an architect?
© 2016 IHS @AGILECHRISYYC 54
Final Architecture Approach:Architecting as a Team
The Agile Architect / March 2016
Steve Jurvetson, Flickr
© 2016 IHS @AGILECHRISYYC 55
The Agile Architect / March 2016
Image Source: worklifematters.netSpotify Engineering Videos
57© 2016 IHS @AGILECHRISYYC
The Agile Architect / March 2016
approach must evolveover time
© 2016 IHS @AGILECHRISYYC 58
The Agile Architect / March 2016
Summary • Empowerment is more than standing back
• Lead through intent
• Resist the urge to provide solutions
• Create a framework for disagreement
• Disagreement is a mechanism for organizational clarity
© 2016 IHS @AGILECHRISYYC 59
Chris Edwards
Chris.Edwards@ihs.com
@AgileChrisYYC
The Agile Architect / March 2016
Questions?
top related