Build Quality In, workshop with Janet Gregory and Lisa Crispin at Agile Roots 2015
1. Build Quality In
Agile Roots 2015
Salt Lake City
Lisa Crispin Janet Gregory
@lisacrispin @janetgregoryca
Sharing Testing Expertise for Product Success
Copyright 2015
2. A little about us
Janet
First agile team: 2000
Currently coaching, training
Twitter: janetgregoryca
Email: janet@agiletester.ca
Agile Testing; 2009
More Agile Testing: Oct 2014
Website:
www.agiletester.com
www.agiletester.ca
Lisa
First agile team – 2000
Currently tester on Pivotal Tracker team
Twitter: lisacrispin
Email: lisa@agiletester.ca
Copyright 2015 : Lisa Crsipin, Janet Gregory – DragonFire Inc
2
3. Let’s find out about you!
Copyright 2015 : Lisa Crsipin, Janet Gregory – DragonFire Inc
3
What roles do you normally play?
Raise your hand if you are primarily a ……
• tester
• programmer
• business analyst / domain expert
• manager
• iteration manager / ScrumMaster
Did you bring your curiosity and problems
solving skills today?
4. If you’re sitting with a table group with several
people in your specialty, you might like to
switch tables to get the most value out of our
exercises.
Are you at the right table?
5. Ways to:
• Involve the whole team
• Identify skills needed to build your T-shaped
skill set
• Grow square-shaped team skill sets
• that enable the team to build quality in
• to transfer testing skills
“Give-aways”
6. Testing on agile projects is ……..
more than “just” testing code
It’s an activity - not a phase
6
8. Exercise - Your skills: ~5 minutes
• What’s in your testing toolbox?
• Write down the skills you can contribute to
your team that help build in quality
• ONE skill per sticky note
9. How do we define quality?
Copyright 2015 : Lisa Crsipin, Janet Gregory – DragonFire Inc
9
• "Quality is value to some person.”
– Jerry Weinberg
• Internal vs external quality
• What does it mean to you and your team?
10. What’s your team’s commitment to quality?
• Everyone will say they want
high quality…
• Get the team together to
discuss: what level of quality
can you commit to?
• Make the commitment mean
something
Copyright 2015 : Lisa Crsipin, Janet Gregory – DragonFire Inc
10
12. What might be in a team’s toolbox?
Group Exercise – 12 minutes
1. Put everyone’s sticky notes of skills on a
wall chart.
2. Group similar ones.
3. Discuss the skills each specialty can bring.
4. Who else on a software team might bring
additional skills that help build in quality?
5. Prioritize the skills needed (groupings)
12
13. Some collaborative techniques
Copyright 2015 : Lisa Crsipin, Janet Gregory – DragonFire Inc
13
Conversations
Use models
Use patterns
Pair
Brown bag lunches
Book clubs
Retrospectives
Show by example
Group exercises
Play games
Drawing (ex. mind maps)
Experiment
Learning time
Coaching
14. Patterns to affect change
Copyright 2015 : Lisa Crsipin, Janet Gregory – DragonFire Inc
14
Fearless Change (2008) &
More Fearless Change (2015)
by MaryLynn Manns and Linda Rising
#1 Just Enough:
To ease learners into difficult concepts of a new idea,
give a brief intro and make more info available when
they are ready
#2 Persistent PR:
Keep the new idea visible by placing reminders
throughout the organization, for example, the team
work area.
15. Exercise - Experiments: 20 minutes
Copyright 2015 : Lisa Crsipin, Janet Gregory – DragonFire Inc
15
Take top 2 prioritized skills from the last exercise
1. Identify possible collaborative solutions (5-10 min)
2. Try these out with other team members (10-15 min)
Debrief
• Did any work particularly
well?
16. Building Quality In
• You can be a change agent!
• Make them team problems to solve
• Bring up quality and testing issues in standups,
retrospectives
• Get the whole team involved
• Transfer skills
• Experiment!
16
17. There’s not one right way
Find ways that you can add value to your
team
And then …. keep learning
Copyright 2015 : Lisa Crsipin, Janet Gregory – DragonFire Inc
17
18. More Learning
• Knight, Adam P., "T-shaped Tester, Square Shaped Team",
http://thesocialtester.co.uk/t-shaped-tester-square-shaped-team/, 2013
• Lambert, Rob, "T-shaped Testers and Their Role In a Team",
http://thesocialtester.co.uk/t-shaped-testers-and-their-role-in-a-team/ , 2012
• Levison, Mark, "The Beginner's Mind - An Approach to Listening",
http://www.infoq.com/news/2008/08/beginners_mind, InfoQ, 2008
• McMillan, Darren, "Mind Mapping 101", for Testing:
http://www.bettertesting.co.uk/content/?p=956, 2011
• Fearless Change, 2008 and More Fearless Change, 2015, Mary Lynn Manns and
Linda Rising, Addison-Wesley
• Gärtner, Markus, ATDD By Example, Markus Gärtner, 2012, Addison-Wesley
• Adzic, Gojko – all his books! Some with David Evans and Tomm Roden.
• Henderson, Elisabeth, Expore It! 2013, Pragmatic Bookshelf
Copyright 2015 : Lisa Crsipin, Janet Gregory – DragonFire Inc
18
19. Agile Testing: A Practical Guide for Testers and Agile Teams
More Agile Testing: Learning Journeys for the Whole Team
By Janet Gregory and Lisa Crispin
www.agiletester.ca
www.agiletester.com
Contact info
www.janetgregory.ca
Email: janet@agiletester.ca
Twitter: janetgregoryca
19
lisacrispin.com
Email: lisa@agiletester.ca
Twitter: lisacrispin
Copyright 2015 : Lisa Crsipin, Janet Gregory – DragonFire Inc
Editor's Notes
3:30
Each of us introduces ourselves briefly
Janet
- quick raise of hands …
Animated slide
Janet
Give them a minute – I doubt whether any one will, but …
Lisa.
Explain the idea of “giveaways” instead of “takeaways”, from Fanny Pittack & Alex Schwarz’s keynote at ATD last year. We offer these ideas – participants can choose to take them.
End:337
Lisa
3:37
We mentioned this in the plenary talk, so only need to highlight …
End 3:42
Lisa
T-shaped skills are a metaphor to describe the abilities of an agile team member. Focus on skills, competencies rather than roles
The horizontal bar represents a broad skill set: the ability to collaborate across disciplines with experts in other areas and to apply knowledge in areas of expertise other than one's own. Generalizing specialist.
The vertical bar on the T represents the depth of related skills and expertise in a single field
Testers can indeed be proactive and learn many skills to add value to their team.
They will talk about how can testers can expand their roles rather than reduce them
<Thinking skills, honing your craft>
<Dev-Tester Pairing> <Product owners can accept a user story, seeing it does what she expected. However, she may not consider other areas important to customer – performance, risky edge cases, security – tell story of how our team has both PO and testers look at each story>
I think we can dilute our skills if we try to be everything. I was talking to someone the other day, who dropped out of programming because they couldn’t keep up with all the technical things they needed to know.
Story from agile testing group - once a dev has committed passing code, he coordinates with the tester to establish a window to push to the QA server, as well as the functionality of the code in the push. We're working toward involving the tester more in the design and test authoring phase so that she has a better understanding when she starts testing exactly what's going on.
Lisa -
3:42 – 3:47 debrief end 3:52
give examples of a couple of yours – domain knowledge, eliciting examples of desired behavior
For example , one of Janet’s might be facilitations skills, nothing to do with testing specifically
- Keep the stickies close – we will use them in the next exercise.
- what kind of debrief should we do here??? We’ve got 5 minutes, so maybe you ask for examples from people, and I write them down – sharing.
Janet
Explain internal vs external and that the customer gets to decide external…
Might be easy if you have predefined rules like in sports.
Janet’s daughter gave this explanation to my 6 year old grandson. I thought it was actually very good. “It the level of precision one hopes to acquire”. I think it about says it all… although I’d like a different word than precision – she was talking about quality of a video streaming.
3:52
What quality goals their team would really commit to – put it in writing, make it visible and obvious, make it realistic.
As the team improves, change the goals – strive for more.
Janet
Also on the plenary talk.. So just quick review
End 3:57
See links for more by Rob Lambert and Adam P. Knight at the end of the slide deck.
How is your team shaped, and who is on your team.
3:57-4:09
Debrief – get each team to talk about 2 of their groupings? - an extra 10 min ??
End debrief 4:17
Lisa
These are some techniques that could be used to help train, teach, mentor
Next slide will intro 2 patterns
Introduce 2 patterns – just to show them there are other places to look
END 4:24
Just Enough: Difficult, complex concepts can overwhelm novices. When introducing a new idea, concentrate on the fundamentals/big picture and give only a brief description of more difficult concepts. Spark interest. EG: you’re presenting an idea to upper mgt. Have a slide or two about more difficult concepts, but emphasize conclusions, benefits. Wait until they are ready to provide more info. Provide references for more learning. Show how it can be useful in their jobs.
Persistent PR: people may forget about the new idea. Post info about it around the team space where people are likely to see and discuss it. Use a graphic with bright colors, a memorable quote. Promote casual interaction about it. Information radiators (Alistair Cockburn). Lisa’s story: in our new office we have a huge whiteboard all along the work area, doing a story board exercise there makes it visible to others, they ask about it. Leave a book or magazine out where people may pick it up and glance through it.
Lisa,
The hope is to actually be able to try these ideas in the workshop itself so it is easier to bring back to your organization.
4:24 – 4:44
Debrief end 4:54
Janet
Yeah, let’s make a new list, these are from the advanced topics workshop.