architect in an agile organization 1 The Agile Architect November 2015 Chris Edwards PEng Senior Manager ChrisEdwardsihscom AgileChrisYYC The Agile Architect Our Experience in Discovering a Successful Pattern ID: 603929
Download Presentation The PPT/PDF document "what is the role of an" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
what is the role of anarchitect in an agileorganization?
1
The Agile Architect /
November 2015Slide2
Chris Edwards P.Eng., Senior ManagerChris.Edwards@ihs.com @
AgileChrisYYCThe Agile Architect
Our Experience in Discovering a Successful Pattern
November 2015Slide3
Setting the Stage5 teams, 5-9 each (including QA)Mix of Scrum/Kanban/
ScrumbanThick ClientC++Mature Codebase
Recently Adopted Agile
Major Project – Client / Server
3
The Agile Architect / November 2015Slide4
The best architectures, requirements, and designs emerge from
self-organizing teams.
4
The Agile Architect /
November 2015
Agile ManifestoSlide5
Architecture
Approach 1:
Laissez Faire
5
The Agile Architect /
November 2015Slide6
6The Agile Architect / November 2015
HELP!!!Slide7
empowerment is morethan just taking yourhands off the wheel
7
The Agile Architect / November 2015Slide8
how do we incorporatean architect… without sacrificing
agile values?
8
The Agile Architect / November 2015Slide9
Wanted to avoid this:9
The Agile Architect / November 2015
Requirements
Design
Code
Test
DeploySlide10
And this:10
The Agile Architect / November 2015
cliparthut.comSlide11
ArchitectureApproach 2:The Architecture Scout
11
The Agile Architect /
November 2015Slide12
12
The Agile Architect / November 2015
Understand the System
Research
Evaluate Different Approaches
Define Layers / Responsibilities
PrototypeSlide13
epiphany: architect mustbe connected to the code
13
The Agile Architect / November 2015Slide14
14
The Agile Architect / November 2015
Architecture by Example
”
“Slide15
15
The Agile Architect / November 2015Slide16
16The Agile Architect / November 2015
Too many classes makes the system too complex!
Big classes make the
system unmaintainable!Slide17
17The Agile Architect / November 2015
WORK HARDER!Slide18
what if thearchitect isWRONG?
18
The Agile Architect / November 2015Slide19
how do you knowif the architectis WRONG?
19
The Agile Architect / November 2015Slide20
20
The Agile Architect / November 2015
I thought you knew
something I didn’t
”
“Slide21
architect is a leadership role
21
The Agile Architect / November 2015Slide22
The Agile Architect / November 2015
xkcd.com
22Slide23
Programming
Tell Don’t Ask
23
The Agile Architect / November 2015
Leadership
Ask Don’t TellSlide24
24
The Agile Architect /
November 2015
Image Source: worklifematters.net
Spotify Engineering VideosSlide25
how do I serve the teams without telling
them what to do?
25
The Agile Architect / November 2015Slide26
Intent Based Leadership
26
The Agile Architect /
November 2015
Rob van
Hilten
, FlickrSlide27
27The Agile Architect /
November 2015
Don’t move information to authority,
move authority to the information
”
“
David
MarquetSlide28
28
The Agile Architect /
November 2015
Image Source: worklifematters.netSlide29
29The Agile Architect /
November 2015
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
MarquetSlide30
i intend to…
30
The Agile Architect / November 2015Slide31
31
The Agile Architect /
November 2015
Image Source: worklifematters.net
Spotify Engineering VideosSlide32
Architecture
Approach 3:
The Architecture Coach
32
The Agile Architect /
November 2015
Rob van
Hilten
, FlickrSlide33
Daily Design Meeting30 minutesTechnical lead from each team
Discuss challenges that being encounteredExercise is repeated on the team that brought the challenge
33
The Agile Architect / November 2015Slide34
34The Agile Architect /
November 2015
Resist the urge to provide solutions.
”
“
David
MarquetSlide35
questionscommunicatevalues
35
The Agile Architect / November 2015Slide36
letting go is hard
36The Agile Architect / November 2015Slide37
37The Agile Architect /
November 2015
organizations
which design systems ...
are constrained to
produce
designs which are copies of the communication structures of these
organizations
”
“
M. ConwaySlide38
38
The Agile Architect / November 2015Slide39
39
The Agile Architect / November 2015
Image Source: worklifematters.net
Spotify Engineering VideosSlide40
Architecture
Approach 3:
The Architecture Coach
40
The Agile Architect /
November 2015
Rob van
Hilten
, Flickr
Coaching Agile Teams, Lyssa AdkinsSlide41
Focus on InterestsRather than Positions
41
The Agile Architect /
November 2015
Rob van
Hilten
, FlickrSlide42
Design StepsWhat is the problem you’re trying to solve?What solutions should we consider?
What are the pros/cons of each solution?
42
The Agile Architect / November 2015Slide43
create a common frameworkfor resolving conflict
43
The Agile Architect / November 2015Slide44
disagreement is amechanism for organizational clarity
44
The Agile Architect / November 2015Slide45
the end?
45The Agile Architect / November 2015Slide46
something interestinghappened
46
The Agile Architect / November 2015Slide47
47
The Agile Architect / November 2015
?Slide48
do we still need an architect?
48
The Agile Architect / November 2015Slide49
Final Architecture Approach:Architecting as a Team
49
The Agile Architect /
November 2015
Steve
Jurvetson
, FlickrSlide50
50
The Agile Architect / November 2015
Image Source: worklifematters.net
Spotify Engineering VideosSlide51
knowing what we know todaywould we do it all again?
51
The Agile Architect / November 2015Slide52
approach must evolveover time
52
The Agile Architect / November 2015Slide53
SummaryEmpowerment is more than standing backArchitect must be connected to the code
Lead through intentResist the urge to provide solutionsBuild relationships between teamsCreate a framework for disagreement
Disagreement is a mechanism for organizational clarity
53
The Agile Architect / November 2015Slide54
leadership skills are vital to an architect’ssuccess
54
The Agile Architect / November 2015Slide55
55
www.synerzip.com
Hemant Elhence
hemant@
synerzip.com
469.374.0500
55Slide56
Synerzip in a Nutshell
Software product development
partner
for small/mid-sized technology companies
Exclusive focus on small/mid-sized technology companies, typically venture-backed companies in growth phase
By definition, all Synerzip work is the IP of its respective clients
Deep experience in full SDLC – design,
dev
, QA/testing, deployment
Dedicated team of
high caliber
software professionals for each client
Seamlessly extends client’s local team offering full transparency
Stable teams with very low turn-over
NOT just “staff augmentation, but provide full management support
Actually
reduces risk
of development/delivery
Experienced team – uses appropriate level of engineering discipline
Practices Agile development – responsive yet disciplined
Reduces cost
– dual-site team, 50% cost advantage
Offers long-term
flexibility
– allows (facilitates) taking offshore team captive – aka “BOT” option
56Slide57
Synerzip Clients
57Slide58
Next Webinar
Evolution of Configuration Management
Into a
DevOps
/Agile World
Complimentary Webinar:
Tuesday, December 15, 2015
@ Noon CST
Presented by:
Marisa
Sawatphadungkij
,
CM
& Test Manager
at
Drillinginfo
58Slide59
Hemant Elhence
hemant@
synerzip.com
469.374.0500
Connect with Synerzip
@Synerzip
linkedin.com
/company/
synerzip
facebook.com
/Synerzip
59Slide60
Chris Edwards
Chris.Edwards@ihs.com@AgileChrisYYC
60
The Agile Architect /
November 2015
Questions?