Agile Architect - Turning Followers into Leaders

© 2016 IHS Markit. All Rights Reserved.

The Agile ArchitectTurning Followers into LeadersChris Edwards P.Eng., Senior Manager

[email protected]

@AgileChrisYYC @ChrisSeanAgile

1

mailto:[email protected]




4

Is it OK that I just donated blood?


5

Doctor: There isn’t any reason it should interfere



7

Confession: I‘m terrified of needles


8


9


10

OUCH


11

Why is the doctor pressingright into where I just

had blood taken?


12

It‘s ok,she probably has

a really good reason


13

After all,she’s a doctor


14

Why didn’t Isay anything?


15

Disclaimer:This is not a talk about

architecture


16

What is the role of anarchitect in an agile

organization?


17

What are you hoping to getout of this talk?


18

Your mileagemay vary


19

Meet Our Protagonist


20


21


22


23


24

XKCD


25

I’d like to get to know you!


26

Setting the Stage

• 5 teams, 5-9 each (including QA)• Mix of Scrum/Kanban/Scrumban• Thick Client• C++• Mature Codebase• Oil & Gas Engineering Analytics• Recently Adopted Agile• Major Project – Client / Server


27

”“ The best architectures,

requirements, and designs emerge from self-organizing

teams.

Agile Manfesto


28

ArchitectureApproach 1:Laissez Faire


29

HELP!!!


30

”“ Build projects around motivated

individuals. Give them the environment and support they need, and trust them to get the job done.

Agile Manifesto


31

Empowerment is morethan just taking yourhands off the wheel


32


33

How do we incorporatean architect…

without sacrificing agile values?


34

We want to avoid this:Requirements

Design

Code

Test

Deploy


35

And this:

cliparthut.com


36

ArchitectureApproach 2:The Architecture Scout


37

I have a hypothesis!

An idea you can test!


38

My Hypothesis:

• If I feed the team’s a continuous stream of prototypes and examples

• Then they will have enough information to be productive• AND• They will take ownership over their designs


39

Architecture by Example


40


41

Problem 1:Mistakes everywhere!

© 2016 IHS Markit. All Rights Reserved. 42

IF YOU COULD JUST GO AHEAD AND REDO THE LAST 2 WEEKS OF WORK

THAT’D BE GREAT


43

Problem 2:Team disagreements


44

Too many classes makes the system

too complex!

Big classes make the system

unmaintainable!


45


46

WORK HARDER!


47

Problem 3: What if the architect is

WRONG?


48

How do you knowif the architect

is WRONG?


49

”“ No battle plan every survives

contact with the enemy

Helmuth von Moltke the Elder


50

”“ I thought you knew

something I didn’t


51

Epiphany: Architect is a leadership role


52

xkcd.com


53

Image Source: worklifematters.netSpotify Engineering Videos


54

How do I serve the teams without telling

them what to do?


55

Intent-Based Leadership

Rob van Hilten, Flickr


56

”“ Don’t move information to authority,

move authority to the information

David Marquet


58

”“ 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


60

I intend to…


61



62

ArchitectureApproach 3:The Architecture Coach

Rob van Hilten, Flickr


63

”“ Resist the urge to provide solutions

David Marquet


64

”“ Questions

communicatevalues

Sean Dunn


65

Spend time with the teams


66

https://www.youtube.com/watch?v=QaZ0L7aDx50

https://www.youtube.com/watch?v=QaZ0L7aDx50


67

Make it safe tospeak truth to power


68

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


69

Letting go is hard


71


72



75

Design Steps

• What is the problem you’re trying to solve?• What solutions should we consider?• What are the pros/cons of each solution?


76

Sources: Edward de Bono,retrospectivewiki.org


77

Create a common frameworkfor resolving conflict


78

Scenario

• Design problem with 2 options:>Enforce business rules in the database>Enforce business rules in the domain layer

• The design team unanimously agrees to put the business rule in the domain layer

• Tech lead brings it back to their team, and they decide to put it in the database


79

Disagreement is amechanism for

organizational clarity


81

The end?


82

Something interestinghappened


83

?


84

Do we still need an architect?


85

Final ArchitectureApproach:Architecting as a Team

Steve Jurvetson, Flickr


86



87

Imagine:You leave your team for 1 year


88

When you return, the architecture has changed

dramatically


89

How do you react?


“This is just too risky!”

Wouldn’t it be less risky to leverage the brainpower of your entire team?


“My Architect can’t learn this”

Leadership can be taught


98

Summary

• Empowerment is more than standing back• Lead through intent• Every moment is an opportunity to teach• Resist the urge to provide solutions• Let go!• Create a framework for disagreement• Disagreement is a mechanism for organizational clarity


99

Approach must evolveover time


100

Architect is aleadership role


101

And remember…


102


103

Thank You!

Chris Edwards

[email protected]@[email protected]

mailto:[email protected]

Date post:	16-Apr-2017
Category:	Leadership & Management
Upload:	christopher-edwards-peng
View:	170 times
Download:	3 times

Agile Architect - Turning Followers into Leaders

Leadership & Management