47
© 2009 Perceptive Informatics, Inc. A PAREXEL ® Company From waterfalls to rapids an experience report

From waterfall to rapids - an experience report

Embed Size (px)

DESCRIPTION

Presented at SQGNE Jan 9th meeting.

Citation preview

Page 1: From waterfall to rapids - an experience report

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

From waterfalls to rapids

an experience report

Page 2: From waterfall to rapids - an experience report

2

Calm Serene Symmetry Beautiful Peaceful Inside ?

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 3: From waterfall to rapids - an experience report

3

Prelude

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 4: From waterfall to rapids - an experience report

4

Introductions

Me You Raise your hand if…

– You have little idea about Agile or scrum– You are working in Agile environment– You are a non-tester

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 5: From waterfall to rapids - an experience report

5

Interruptions solicited

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 6: From waterfall to rapids - an experience report

6

Agenda

why how where

© 2012 Perceptive Informatics, Inc. A PAREXEL® Company

Page 7: From waterfall to rapids - an experience report

7

Why ?

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 8: From waterfall to rapids - an experience report

8

Transparency

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 9: From waterfall to rapids - an experience report

9

Shorter release cycles

Reduce inventory Feedback Quality Reduce total time ?

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 10: From waterfall to rapids - an experience report

10

Inspect and Adapt

Retrospectives Customer feedback

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 11: From waterfall to rapids - an experience report

11

Dev-Test Silos

Who do you eat lunch with ? Two teams working as one team or one team ? Team interactions or individual interactions ?

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 12: From waterfall to rapids - an experience report

12

Dev-Test ratio

What is a healthy ratio ?

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 13: From waterfall to rapids - an experience report

13

Exclusive ownership

Who own the assets ? Do developers test ? Do Testers change code ?

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 14: From waterfall to rapids - an experience report

14

“Technical” test staff

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 15: From waterfall to rapids - an experience report

15

Long endgame QA phase

Lack of automation Lack of domain knowledge Cemented dev-qa silos QA documentation

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 16: From waterfall to rapids - an experience report

16

How ?

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 17: From waterfall to rapids - an experience report

17

Top to bottom

Management initiated Team initiated

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 18: From waterfall to rapids - an experience report

18© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 19: From waterfall to rapids - an experience report

19

Time and energy

Expensive Commitment

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 20: From waterfall to rapids - an experience report

20

Learnings

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 21: From waterfall to rapids - an experience report

21

Experimental

Processes Product

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 22: From waterfall to rapids - an experience report

22

Tools

Basecamp SeeNowDo Pivol Tracker Rally White-board

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 23: From waterfall to rapids - an experience report

23

Extreme Programming

Unit Testing Pair programming TDD BDD Continuous Delivery Code reviews

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 24: From waterfall to rapids - an experience report

24

Culture

Process or culture ?

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 25: From waterfall to rapids - an experience report

25

Where ?

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 26: From waterfall to rapids - an experience report

26

Success !

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 27: From waterfall to rapids - an experience report

27

Dev-QA ratio

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 28: From waterfall to rapids - an experience report

28

Shorter QA phase

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 29: From waterfall to rapids - an experience report

29

Self reliant teams

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 30: From waterfall to rapids - an experience report

30

Automation

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 31: From waterfall to rapids - an experience report

31

Joint ownership

Quality is everyone’s responsibility Joint exploratory testing Pairing

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 32: From waterfall to rapids - an experience report

32

Better collaboration

Developers <- Domain knowledge Testers <- Technical help

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 33: From waterfall to rapids - an experience report

33

crossover

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 34: From waterfall to rapids - an experience report

34

Limited success !

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 35: From waterfall to rapids - an experience report

35

Transparency ? Not so much

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 36: From waterfall to rapids - an experience report

36

Gimmickry of scrum

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 37: From waterfall to rapids - an experience report

37

Documentation burden

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 38: From waterfall to rapids - an experience report

38

Challenge of changing culture

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 39: From waterfall to rapids - an experience report

39

Too many meetings ?

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 40: From waterfall to rapids - an experience report

40

Lessons learned

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 41: From waterfall to rapids - an experience report

41

Lessons learned

Don’t follow scrum by book Don’t over sell it Be wary of vendors - but do seek help

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 42: From waterfall to rapids - an experience report

42© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 43: From waterfall to rapids - an experience report

43

Factors

The domain The customers Technology Nature of the application Your market Who initiated the transition Human factor

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 44: From waterfall to rapids - an experience report

44

Closing thoughts

Quite a ride Next job : Agile again Startup vs. Not-so-startup Developers ?

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 45: From waterfall to rapids - an experience report

45

Contact

www.rajivnarula.com

[email protected]

@rajivnarula

© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 46: From waterfall to rapids - an experience report

46© 2009 Perceptive Informatics, Inc. A PAREXEL® Company

Page 47: From waterfall to rapids - an experience report

47© 2009 Perceptive Informatics, Inc. A PAREXEL® Company