from waterfalls to rapids · factors ! the domain ! the customers ! technology ! nature of the...
TRANSCRIPT
© 2009 Perceptive Informatics, Inc. A PAREXEL® Company
From waterfalls to rapids
an experience report
§ Calm § Serene § Symmetry § Beautiful § Peaceful § Inside ?
2 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Prelude
3 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
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
4 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Interruptions solicited
5 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Agenda
§ why § how § where
6 © 2012 Perceptive Informatics, Inc. A PAREXEL® Company
Why ?
7 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Transparency
8 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Shorter release cycles
§ Reduce inventory § Feedback § Quality § Reduce total time ?
9 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Inspect and Adapt
§ Retrospectives § Customer feedback
10 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Dev-Test Silos
§ Who do you eat lunch with ? § Two teams working as one team or one team ? § Team interactions or individual interactions ?
11 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Dev-Test ratio
§ What is a healthy ratio ?
12 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Exclusive ownership
§ Who own the assets ? § Do developers test ? § Do Testers change code ?
13 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
“Technical” test staff
14 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Long endgame QA phase
§ Lack of automation § Lack of domain knowledge § Cemented dev-qa silos § QA documentation
15 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
How ?
16 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Top to bottom
§ Management initiated § Team initiated
17 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
18 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Time and energy
§ Expensive § Commitment
19 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Learnings
20 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Experimental
§ Processes § Product
21 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Tools
§ Basecamp § SeeNowDo § Pivol Tracker § Rally § White-board
22 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Extreme Programming
§ Unit Testing § Pair programming § TDD § BDD § Continuous Delivery § Code reviews
23 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Culture
§ Process or culture ?
24 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Where ?
25 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Success !
26 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Dev-QA ratio
27 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Shorter QA phase
28 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Self reliant teams
29 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Automation
30 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Joint ownership
§ Quality is everyone’s responsibility § Joint exploratory testing § Pairing
31 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Better collaboration
§ Developers <- Domain knowledge § Testers <- Technical help
32 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
crossover
33 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Limited success !
34 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Transparency ? Not so much
35 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Gimmickry of scrum
36 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Documentation burden
37 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Challenge of changing culture
38 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Too many meetings ?
39 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Lessons learned
40 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Lessons learned
§ Don’t follow scrum by book § Don’t over sell it § Be wary of vendors - but do seek help
41 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
42 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Factors
§ The domain § The customers § Technology § Nature of the application § Your market § Who initiated the transition § Human factor
43 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Closing thoughts
§ Quite a ride § Next job : Agile again § Startup vs. Not-so-startup § Developers ?
44 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
Contact
www.rajivnarula.com [email protected]
@rajivnarula
45 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
46 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company
47 © 2009 Perceptive Informatics, Inc. A PAREXEL® Company