Agile Architect - Turning Followers into Leaders

Post on 16-Apr-2017

170 views 3 download

transcript

© 2016 IHS Markit. All Rights Reserved.

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

chris.edwards@ihsmarkit.com

@AgileChrisYYC @ChrisSeanAgile

1

© 2016 IHS Markit. All Rights Reserved.

© 2016 IHS Markit. All Rights Reserved.

© 2016 IHS Markit. All Rights Reserved.

4

Is it OK that I just donated blood?

© 2016 IHS Markit. All Rights Reserved.

5

Doctor: There isn’t any reason it should interfere

© 2016 IHS Markit. All Rights Reserved.

© 2016 IHS Markit. All Rights Reserved.

7

Confession: I‘m terrified of needles

© 2016 IHS Markit. All Rights Reserved.

8

© 2016 IHS Markit. All Rights Reserved.

9

© 2016 IHS Markit. All Rights Reserved.

10

OUCH

© 2016 IHS Markit. All Rights Reserved.

11

Why is the doctor pressingright into where I just

had blood taken?

© 2016 IHS Markit. All Rights Reserved.

12

It‘s ok,she probably has

a really good reason

© 2016 IHS Markit. All Rights Reserved.

13

After all,she’s a doctor

© 2016 IHS Markit. All Rights Reserved.

14

Why didn’t Isay anything?

© 2016 IHS Markit. All Rights Reserved.

15

Disclaimer:This is not a talk about

architecture

© 2016 IHS Markit. All Rights Reserved.

16

What is the role of anarchitect in an agile

organization?

© 2016 IHS Markit. All Rights Reserved.

17

What are you hoping to getout of this talk?

© 2016 IHS Markit. All Rights Reserved.

18

Your mileagemay vary

© 2016 IHS Markit. All Rights Reserved.

19

Meet Our Protagonist

© 2016 IHS Markit. All Rights Reserved.

20

© 2016 IHS Markit. All Rights Reserved.

21

© 2016 IHS Markit. All Rights Reserved.

22

© 2016 IHS Markit. All Rights Reserved.

23

© 2016 IHS Markit. All Rights Reserved.

24

XKCD

© 2016 IHS Markit. All Rights Reserved.

25

I’d like to get to know you!

© 2016 IHS Markit. All Rights Reserved.

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

© 2016 IHS Markit. All Rights Reserved.

27

”“ The best architectures,

requirements, and designs emerge from self-organizing

teams.

Agile Manfesto

© 2016 IHS Markit. All Rights Reserved.

28

ArchitectureApproach 1:Laissez Faire

© 2016 IHS Markit. All Rights Reserved.

29

HELP!!!

© 2016 IHS Markit. All Rights Reserved.

30

”“ Build projects around motivated

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

Agile Manifesto

© 2016 IHS Markit. All Rights Reserved.

31

Empowerment is morethan just taking yourhands off the wheel

© 2016 IHS Markit. All Rights Reserved.

32

© 2016 IHS Markit. All Rights Reserved.

33

How do we incorporatean architect…

without sacrificing agile values?

© 2016 IHS Markit. All Rights Reserved.

34

We want to avoid this:Requirements

Design

Code

Test

Deploy

© 2016 IHS Markit. All Rights Reserved.

35

And this:

cliparthut.com

© 2016 IHS Markit. All Rights Reserved.

36

ArchitectureApproach 2:The Architecture Scout

© 2016 IHS Markit. All Rights Reserved.

37

I have a hypothesis!

An idea you can test!

© 2016 IHS Markit. All Rights Reserved.

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

© 2016 IHS Markit. All Rights Reserved.

39

Architecture by Example

© 2016 IHS Markit. All Rights Reserved.

40

© 2016 IHS Markit. All Rights Reserved.

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

© 2016 IHS Markit. All Rights Reserved.

43

Problem 2:Team disagreements

© 2016 IHS Markit. All Rights Reserved.

44

Too many classes makes the system

too complex!

Big classes make the system

unmaintainable!

© 2016 IHS Markit. All Rights Reserved.

45

© 2016 IHS Markit. All Rights Reserved.

46

WORK HARDER!

© 2016 IHS Markit. All Rights Reserved.

47

Problem 3: What if the architect is

WRONG?

© 2016 IHS Markit. All Rights Reserved.

48

How do you knowif the architect

is WRONG?

© 2016 IHS Markit. All Rights Reserved.

49

”“ No battle plan every survives

contact with the enemy

Helmuth von Moltke the Elder

© 2016 IHS Markit. All Rights Reserved.

50

”“ I thought you knew

something I didn’t

© 2016 IHS Markit. All Rights Reserved.

51

Epiphany: Architect is a leadership role

© 2016 IHS Markit. All Rights Reserved.

52

xkcd.com

© 2016 IHS Markit. All Rights Reserved.

53

Image Source: worklifematters.netSpotify Engineering Videos

© 2016 IHS Markit. All Rights Reserved.

54

How do I serve the teams without telling

them what to do?

© 2016 IHS Markit. All Rights Reserved.

55

Intent-Based Leadership

Rob van Hilten, Flickr

© 2016 IHS Markit. All Rights Reserved.

56

”“ Don’t move information to authority,

move authority to the information

David Marquet

© 2016 IHS Markit. All Rights Reserved.

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

© 2016 IHS Markit. All Rights Reserved.

60

I intend to…

© 2016 IHS Markit. All Rights Reserved.

61

Image Source: worklifematters.netSpotify Engineering Videos

© 2016 IHS Markit. All Rights Reserved.

62

ArchitectureApproach 3:The Architecture Coach

Rob van Hilten, Flickr

© 2016 IHS Markit. All Rights Reserved.

63

”“ Resist the urge to provide solutions

David Marquet

© 2016 IHS Markit. All Rights Reserved.

64

”“ Questions

communicatevalues

Sean Dunn

© 2016 IHS Markit. All Rights Reserved.

65

Spend time with the teams

© 2016 IHS Markit. All Rights Reserved.

66

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

© 2016 IHS Markit. All Rights Reserved.

67

Make it safe tospeak truth to power

© 2016 IHS Markit. All Rights Reserved.

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

© 2016 IHS Markit. All Rights Reserved.

69

Letting go is hard

© 2016 IHS Markit. All Rights Reserved.

71

© 2016 IHS Markit. All Rights Reserved.

72

© 2016 IHS Markit. All Rights Reserved.

© 2016 IHS Markit. All Rights Reserved.

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?

© 2016 IHS Markit. All Rights Reserved.

76

Sources: Edward de Bono,retrospectivewiki.org

© 2016 IHS Markit. All Rights Reserved.

77

Create a common frameworkfor resolving conflict

© 2016 IHS Markit. All Rights Reserved.

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

© 2016 IHS Markit. All Rights Reserved.

79

Disagreement is amechanism for

organizational clarity

© 2016 IHS Markit. All Rights Reserved.

81

The end?

© 2016 IHS Markit. All Rights Reserved.

82

Something interestinghappened

© 2016 IHS Markit. All Rights Reserved.

83

?

© 2016 IHS Markit. All Rights Reserved.

84

Do we still need an architect?

© 2016 IHS Markit. All Rights Reserved.

85

Final ArchitectureApproach:Architecting as a Team

Steve Jurvetson, Flickr

© 2016 IHS Markit. All Rights Reserved.

86

Image Source: worklifematters.netSpotify Engineering Videos

© 2016 IHS Markit. All Rights Reserved.

87

Imagine:You leave your team for 1 year

© 2016 IHS Markit. All Rights Reserved.

88

When you return, the architecture has changed

dramatically

© 2016 IHS Markit. All Rights Reserved.

89

How do you react?

© 2016 IHS Markit. All Rights Reserved. 91

“This is just too risky!”

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

© 2016 IHS Markit. All Rights Reserved. 93

“My Architect can’t learn this”

Leadership can be taught

© 2016 IHS Markit. All Rights Reserved.

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

© 2016 IHS Markit. All Rights Reserved.

99

Approach must evolveover time

© 2016 IHS Markit. All Rights Reserved.

100

Architect is aleadership role

© 2016 IHS Markit. All Rights Reserved.

101

And remember…

© 2016 IHS Markit. All Rights Reserved.

102

© 2016 IHS Markit. All Rights Reserved.

103

Thank You!

Chris Edwards

chris.edwards@ihsmarkit.com@AgileChrisYYC@ChrisSeanAgilewww.ChrisAndSeanAgile.com