Mapping lean principles to testing
Do’s and don’ts for testers is my most viewed post so far. Because of that (and because it’s always better to leave various doors open) I wouldn’t focus on technical posts only. Time for something my colleague accurately calls computer science belles-lettres.
If you had read my Management 3.0 reviewyou know that I like to get familiar with views on software testing not only from our (QA’s) side, by also from our peers (team members, managers, project stakeholders, and clients) perspective. Actually, in my opinion, focusing only on the testers’ view is probably ISTQB’sbiggest flaw. Never mind ISTQB, and let’s move to the business.
Today I gave myself rather ambition task to map Lean principlesto testing activities. Why lean? I read recently Mary & Tom PoppendieckLean Software Development - an Agile Toolkit and Aaron Hodder blog postwhich inspired me. Also, I like how lean practitioners focus on system thinking, trying to optimize the whole instead of a single activity.
So how we, as testers, can adopt lean principles?
Anything that does not add value to a customer is a waste. In many old software testing books, we can read that every release candidate has to be blessed by testers, and deployment to production without manual regression is not acceptable. If you are familiar with the Netlflix deploymentcycle you know that smart deployment is possible without any testing at all. However, in most cases, that’s not possible, so how do we decide when to go live?
I think we should measure two things - the cost of delayed-release (due to testing) and the cost of finding a bug in production. I can’t tell you how to measure it, because it depends on your type of business. Make sure you’re not delaying your awesome feature release because you want to find all bugs in the manual regression process. We can’t find 100% of bugs anyway. Simple as that.
So to summarise it I suggest:
- expanding automated checks suite (according to test pyramid)
- hiring skilled exploratory testers which can quickly find flaws in release candidates
- automating deployment and measurement how it’s working on production (all those continuous delivery and DevOps stuff)
- calculating costs of activities which I bolded above
This one is simple and hard simultaneously. Software testing is a technical activity that requires more and more skills. You may like it or not, but the best testers I had encountered in my short career had a broad knowledge of almost every do’s from my post. So the recipe here is simple: learn, analyze, make mistakes, fix, learn. Adopting the right mindset may be helpful here ( see my ‘Obstacle is the Way review’).
I’m planning to write a post ‘Recommended resources for testers’ soon. This may be helpful for you. Stay tuned :)
Decide as late as possible
Throughout every software project, the product under development changes considerably (if you don’t believe just see screenshots from an alpha version of video game - Starcraft for example). Because of that preparing, detailed scripted test cases before is a waste of time. We should focus on building a common understanding of business goals. If you are a BDD practitioner you probably know that’s the key to success.
The most popular testing design style - Page ObjectPattern was implemented to simplify maintenance work. When you write automated tests have in mind not only stability but and maintainability. The product will change eventually.
Deliver as fast as possible
Make successful delivery of the right product (and in the right quality) your goal. We shouldn’t block release just because we think more will help us find more bugs. I had discussed it already in point 1. Testers should not be considered as project bottleneck, because smart people tend to focus on them. Yahoo probably thought that, and they fixed it spectacularly. Once again, because I think it’s important: make successful delivery of the right product (and in the right quality) your goal.
Empower the team
That’s right, the team. Not developers, not managers, the team. This means that lean practitioners want to empower you. All you need to do it to take this responsibility. In healthy companies, power depends on knowledge and experience. So, theoretically, a tester can be the most important person in a team. Because why not?
Build integrity in
According to Poppendieck team, we have two types of integrity:
Perceived integrity - a system is perceived to have integrity when a user thinks, ‘Yes! That is exactly what I want. Somebody got inside my mind!’
Conceptual integrity - a system has conceptual integrity when it’s stable, expandable, fast, releasable, meets legal constraints and all those
*ilitytesting types you may have encountered in books
It’s tester job to think about that and ask developers unwelcome questions during standup meetings. :)
See the whole
Last but not least. As I said before, we should always try to optimize the whole project, not just testing. This means that tester should do some quality control (QC) work too. If the process is inefficient, if we build a bad product it’s our job to report it and give it to consider. We should measure quality be project revenue, not by the number of bugs.
Categories: Testing thoughts