Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (20)
Semelhante a SQuAD 2013: Team Collaboration for Testing
Semelhante a SQuAD 2013: Team Collaboration for Testing (20)
Mais de lisacrispin
Mais de lisacrispin (20)
Último
Último (20)
SQuAD 2013: Team Collaboration for Testing
- 1. Lisa Crispin Copyright 2013 Co-author of Agile Testing: A Practical Guide for Testers and Agile Teams, Addison-Wesley 2009 (and now working on More Agile Testing) SQuAD Conference 2013 Denver, CO
- 5. Form teams of four: coder, tester, customer, and observer Coder faces away from customer and tester Customer tells the coder what to draw, all at one time. Coder draws the shapes based on what the customer explained. No talking during ‘coding’! Tester “tests” the drawing, writes down “bugs” Coder fixes the “bugs” How long did it take? Is the customer happy?
- 6. Collaborate! Customer and tester tell coder what to draw, and watch the coder draw, answer questions, point out ‘defects’ for programmer to fix immediately (Don’t show the coder the drawing, that makes it too easy, we’re trying to simulate real coding) How long did it take? Is the customer happy? How did that feel compared to Iteration 1? Thanks to the members of the agile-games group and Kane Mar for ideas & pictures for this game
- 7. √
- 9. • Examples provide common language • Shared vision • Coding and testing concurrently • Involves whole team • Shared definition of DONE Bonus: prevents defects! 9 Recommended books: Specification by Example, Gojko Adzic ATDD by Example, Markus Gaertner
- 10. • Why are we doing this? • Who can help? Hinder? Who is impacted? • How can they help or hinder? Impacts • What can we do to support impacts? Deliverables 10
- 11. 11 Based on example at http://impactmapping.org, Gojko Adzic Recommended book: Impact Mapping
- 12. 12
- 13. Copyright 2012 Lisa Crispin, Janet Gregory. From Janet Gregory & Matt Barcomb Jeff Patton: http://www.agileproductdesign .com/blog/the_new_backlog.ht ml
- 16. Collaboration helps simplify, deliver what customers want most
- 18. 18
- 19. 19
- 21. "An individual with a deep level of knowledge in at least one domain and a collaborative understanding of at least one other." Basics Advanced Meta
- 23. √
- 24. Your stories?
Notas do Editor
- And turtles!1:00
- How many of you…
- Let’s try a game to illustrate1:05
- Set a timer
- You can play this with your team
- We’ll talk about patterns and practices to do this1:15 – don’t spend long on this slide, just list the things
- AT = Acceptance testsAT – get shared common understanding – specification workshopsCollaborate at each levelSome of these things can be done in parallel Also known as example-driven development, story test-dd, quadrant 2 testing, driving dev w/ biz-facing tests, spec by example
- End by 1:20
- 1:20
- End by 1:25
- 1:30 Not implying our customers are jackasses! Donkeys are excellent listeners, and they can hear each other from miles away. We now have many ways to keep in touch with our customers. Take advantage. Get them in the loop. Customer support story - Hearing their frustrations first-hand, getting specific feedbackMining support tickets for most-requested features, most-encountered issues – using tags, community sites with votingUsability testing for new UI designs
- Diverse viewpoints help come up with better ideas. Visualization helps – after mind mapping for an hour w/ whole team incl PO, dev thought of a simplified data model that reduced 13 point story to 3.Similar design brainstorming meeting, a tester came up with a much simpler solution to an algorithm.Sometimes customers don’t even know what they’d like – Apple’s magnetic power cord, who asked for that? Use your marketing and sales people too!
- Be prepared for problems in specifying, developing, testing. We need to be ready for change! Need to find ways to think up lots of alternatives of simple solutions, try small experiments to learn whether they’re worthwhile, get fast feedback from MVPEnd at 1:35
- Yes, trying to be everything to everyone will dilute our skillsT-shaped skills are a metaphor to describe the abilities of an agile team member. Focus on skills, competencies rather than rolesThe 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.The vertical bar on the T represents the depth of related skills and expertise in a single fieldEnd at 1:45
- We’ll talk about patterns and practices to do this1:15 – don’t spend long on this slide, just list the things
- Would you be willing to share your own experiences?