• Português
  • 简体中文
  • 繁體中文
  • Deutsch
  • English
  • Español
  • Français
  • 日本語
  • Latviešu
  • Lietuvių
  • Русский

Submitted Conference Content

Full name

Peter Duelen

Job Tester
email peter [dot] duelen [at] gmail [dot] com
Skypeid vatvondel
Phone number +32 496 53 15 66
Company Agilar
City (Country) Belgium
Time 45'
Type of Conference Conference < 40 attendees
Level Sensitized

The scrum board mystery files: To post-it or not to post-it


Back in the days when CD-I was supposed to be hot and you needed 2 persons to lift a PC, I started my career as a tester for multimedia, games and educational software. These first experiences quickly turned into a love for testing and the sense that the “scripted” testing within various teams really needed to be complimented with an exploratory approach and I have been hooked on this approach ever since. For the past 5 years, I have been involved in a series of agile transitions moving testing out of the pre-scripted and “end of the line” activities and into a mindset for the team where improving and experimenting are key to successful and fun testing.


The scrum board mystery files: To post-it or not to post-it Everyone who has walked past a scrum board has noticed them: “Please Test” post-its. They seem a normal part of our daily way of working. But are they really? Are we not, agile or not, still confronted with the evils of perceived quality and having to test in part of our quality in the end? There are a lot of testing issues we constantly grind through to get rid of these hidden assumptions, to prove our work is invaluable to the team. And it’s never as easy as moving a post-it from left to right. But why do we limit ourselves to using this 1 note when we have the perfect visualization tool, the scrum board; at our disposal. It can do a lot; I just think we’re not using it to its full potential. Over the past years, I’ve learned 2 important lessons on creating a common ground for testing when using the scrum board : • What you don’t know, is what you don’t get. and • What you don’t see is what you don’t get. Teams have a lot of information and ideas about visualization and what to show when but as Gojko Adzic already stated in his blog “If it were easy we’d all be doing it already”. So how can we pinpoint bottlenecks, bug clusters, structural issues, … and make sure we can put out some work fixing them ? The scrum board mystery files shows the outcome from a series of testing experiments in agile with regards to getting feedback from teams and managers and improving our way of working in current and new projects.

Go to the submission page!