This blog post is about a Test Project I am currently running. Although I am a supporter of Agile Methodologies like Scrum and Kanban there is still a need for traditional Test Projects especially when a client asks for help.
So how can we approach such a traditional Test Project with some aspects of the Agile Methodologies?
The first thing I introduced was a Kanban board in combination with strong exploratory testing. James Bach and Michael Bolton are a great inspiration when it comes to Exploratory Testing and the Rapid Software Testing framework.
Our Kanban board shows the next 3, 5, 8, 13 and 20 test areas. Yes! Test areas and not Test Cases. Initially we came up with a rough prioritization of the planned test activities. For each test activity we might perform one or more test sessions. Should the priority change, we just update the Kanban board. So we only put analysis effort into the next let’s say 8 test areas.
