Tracking testing on the Scrum taskboard

Today, a colleague of mine, Norbert Hölsken, started off a discussion in our internal communication channel. He asked:

How do you treat bugs on the taskboard that are found during testing? Create a new test for each bug, and put the test task back in ToDo? Or create a bug, and a bug-follow-up testing task?

As it turns out there are a lot of valid reasons to do it one way or another. Yet, the answer “it depends” does not help – neither a Scrum Coach, nor a tester working in a Scrum environment. So, I started raising some of my experiences and concerns, and some of my other colleagues replied as well.

Skip forward three hours, and I am writing a blog entry on my thoughts about it.

Continue reading Tracking testing on the Scrum taskboard

Two problems with context-driven testing

Over the course of the Let’s Test conference in Runö, Sweden, I noticed a problem with context-driven testing. In the past one or two months this turned into two problems I see with context-driven testing. I finally decided to put them out there for further discussion. I hope a lot of you don’t agree with me – and I hope a lot of you folks speak up.

Continue reading Two problems with context-driven testing