Where Does Developer Testing End and Tester Testing Begin?
This is a trick question, right? In agile, everyone works on the same items together, at the same time. Yet, the reality is we’re not all interchangeable cogs. Developers and testers each bring their own, unique skills to the table. The key to effective agile is not minimizing our differences, but building upon the strengths each person brings to the team. Join us for this hands-on simulation and retrospective as developers and testers explore how agile teams build quality into their process, how each member contributes to that quality, and how we can avoid traditional testing pitfalls.
In this workshop, we’ll examine the various ways that agile principals and practices build quality into our process, and how these work best when programmers & testers work together. We’ll facilitate games and discussions on how traditionally cast “developers” and “testers” can use these techniques to best draw on their own unique strengths to ensure a quality product.
The workshop will be broken into 3 successive parts, moving from more traditional thinking (“developer testing vs tester testing”) into agile concepts (like “all together” and “stop the line”):
Mock development activity that simulates a traditional, sequential development approach to allow participants to experience the dysfunctions we tend to build into our processes in a context outside of software development. Have participants identify the dysfunctions they experienced and discuss whether we also see these same problems on software projects in the real world.
Using Lean Thinking as our compass, we’ll examine why many of the problems we encounter in software actually stem from the way our projects are organized, rather than being issues that are somehow inherent to the process of developing software.
Explore the various ways that agile principals and practices help us build quality into our process and show how, by having testers and programmers work together, we can overcome these dysfunctions to build software that delights our customers. We’ll demonstrate how there are many ways beyond traditional testing that agile uses to produce high quality, successful products that build upon the diverse skills and perspectives that each of us brings to the table. Finally, we’ll do one more mock development activity, this one simulating how we can break dysfunctions by working together.
We’ll conclude the workshop with a retrospective to learn from one another how we can make this work on our own projects, and ways we can improve.
- Articulate the various ways that agile teams build quality into their process (testing and otherwise)
- Explain concrete ways that “developers” and “testers” collaborate throughout an iteration, and how each brings their own unique strengths to the process
- Avoid common pitfalls of traditional testing on agile projects
- Understand how quality is everyone’s responsibility on agile teams