Why is Testing/QA another lane on your card wall?

A typical story card wall on most Agile projects would have the following lanes

Ready for Development
In Development
Ready for QA
In QA
Ready for Customer Sign-off
Done

Having this lane structure gives the impression of the team working in silos. It feels like the developers work on developing the story and hand over an artifact to the QAs to now go and test and then whatever happens after that is their (QAs) problem.

In my previous projects, we have tried to combine the In Development, Ready for QA and In QA lanes to one "In-Progress" lane.

The benefits of doing this were

The responsibility to move a story to done was now owned by the team and not a specific role.
Developers, Business Analysts would help with testing if testing was a bottleneck.
We could set Work in-progress limits, so as to implement a pull model, where only as much work is done as can be consumed.

This approach helped the team manage the flow of stories across to Done in a more sustainable way.

Comments

How does one decide what to automate?

A question that has been troubling me for years is how much to automate. We all like to achieve maximum coverage and build a robust safety net where possible in order to give us confidence about the system under test. Given there is ample time i would like to automate almost everything, but in the real world, this isn't possible. This is when we introduced the concept of Value and Cost for a test scenario. Every test scenario would be assigned either of these attributes. Lets call the attribute automation classification High Value - Low Cost High Value - High Cost Low Value - Low Cost Low Value - High Cost What this translates into is we are associating business value and cost to automate to every scenario. So, when a test scenario is of high business value and the cost to automate it is low, then this becomes our ideal automation candidate. You would like to start automating all test scenarios that fit into the High Value - Low Cost category first. See picture below If tim...

Test your services and not your UI

As a tester, i have spent more than 6 years trying to automate tests at the UI layer. As years passed, better automation frameworks evolved resulting in writing more manageable and maintainable code, but the only thing that wasn't getting better was the cost of maintaining these tests, especially when the no. of tests were 500+. There are multiple reasons why i feel creating an automated regression suite of tests at the UI layer is not good. Some of them are Limitations on what the tool can do Time taken to execute these tests leading to longer feedback loop Success rate of tests is not 100% due to latency issues Change in UI and UI flow resulting in an increase in cost to maintain UI tests On the other hand, testing business logic without having to deal with the dumb UI was a concept that a friend of mine at ThoughtWorks, Chirag Doshi introduced to me. He sent me couple of blog links written by Alex Verkhovsky about why is it so hard to do functional test automation at th...

BDD is over-rated

Over the past few years, I have tried to justify the use of a BDD (Behavioral Driven Development) framework to express my tests, but not once have been able to say BDD has helped me address a problem which writing tests the non BDD way would not have addressed. I do understand the value BDD brings to the table, but in most projects that I have implemented BDD on, we have tried to provide a solution (BDD) to a problem that does not exist. Let me try and explain. Lets look at the key benefits of expressing tests the BDD way (There could be more) Collaboration between Business and Development Ubiquitous Domain Language Focus on the behavior of the application Now, more often than not unless your business is co-located with the team, collaboration is not the easiest. The value BDD brings here, is the business validating our understanding by reading our tests expressed in the Given When Then format (BDD) and providing feedback, as BDD expresses the behavior of the syst...

The Shaolin of testing

Search This Blog