LEAN SQA (Software Quality Assurance)

Quality Assurance is perceived as an extra, asa process we must first have confidence that the
overhead and generally, a cost center. To someprocess is capable or performing. One of the best
extent, this is true. It is an investment in the longtechniques for learning a process and finding the
term and quality of your product or service in whereopportunities for improvement is Process Mapping to
the value can come back to you in any number ofliterally follow the item through the flow and
ways and most are not immediate or instant. Let'sdocumenting when changes occur, when it is waiting
take a look at applying LEAN principles to QA andand when it makes "side trips" for inspection and
see if we can improve it just a little.rework. Having one or more subject matter experts
What actually is LEAN?at your side is a great benefit in this task. No special
LEAN is a strategy for reducing cycle time throughtools are needed to make a process map, however,
waste elimination. Cycle time is the lapsed time fromthere are quite a few available on the open source
the start of a process to the end of the process, formarket that are beneficial from a record keeping
example in manufacturing Machine Cycle Time andperspective. Using a sheet of paper and a pencil to
Worker Cycle Time. In Software QA we may beget you started is all I could suggest, when it comes
able to consider each inspection station or stop cantime to review, go for Excel or a process mapping
be considered a smaller cycle of the entire testingtool.
process or cycle, for example, performance testing isProcess or work improvement
one cycle. What is waste in this context? WasteTraditionally, process improvement is started with the
refers to all activities that extend the cycle time butmachine or tool in the process and engineering that
do not add value. The objective of Lean is to reducetool to perform optimally. The thought behind this
the cycle time by eliminating the waste also knownapproach is that with good tools the workers are
as non-value added activities. Any process orfitted with all they need to complete the process
operation that takes time, resources or space buteffectively and efficiently. While this is a good
does not add value to the product or service isapproach, and tools for the job are of paramount
waste.concern, it will generally only impact about 5% of the
They typical examples of waste are:process. For example, we have software that is
- Over-Productionwritten to run on a dual core processor and we are
- Waitingbuilding and testing it on a single core. We improve
- Transportationthe system to a dual core, the code runs faster but
- Processingstill takes just as long at the beginning and the end of
- Inventoriesthe process in wait time. So the improvement is
- Motionabout 5% of the process. How do we impact the
- Defective Productsother 95%? By following the process map and finding
- Unused Creativityout why the code waits at the beginning and the end
Let's take a look at a sample QA process and see ifwould be a great place to start.
any of those fit or if there are some others hidden.What is the Value?
The development team completes and releases anThe object of LEAN is to work faster and more
application to QA for testing. In this package release,efficiently, to provide a greater return than just
QA expects to find business requirements, releaseeliminating defects. How would you know? You take
notes, code, and repository information. If any ofyour process map and build a value stream to
these items is missing, defective or incomplete, wedetermine which part of your process holds what
have waste.percentage of the overall value. Evaluate the major
But whose waste is it?process steps and calculate the value add and non
Technically, the product is in the hands of QA. Is it avalue add of each. This is also known as JIT or Just
"QA problem"? No, but it looks that way to theIn Time. It is pretty common to learn that the
project managers, business and customers as thepositive impact is 10% or less. Much of the non value
problem was uncovered in QA, so they are 'holdingadd may be found in wait time, which is an intangible
up the show'. This appears to be two examples ofwe tend not to be able to visualize. This is a skill to
waste: defective product and waiting for QA, whendevelop that will serve you well in this endeavor -
in reality, it is one issue - QA did not get what theylearning to see the wait or lost time.
needed to perform their task in the cycle. This isIf the issue in our example above could be resolved
where the waters get muddy in false perceptions. Itquickly, and the code could move faster at the
is important to clearly understand where the waste isbeginning and the end it would give you a hard or
coming from before trying to improve it. A goodgreen impact on your budget. An immediate savings!
solution to eliminate this waste of time and resourcesWhat if other items need to take place in order to
might be to implement a release manager to beget the code to the computer faster? These we
certain all the items required are passed along to QA.would call dependencies and they would represent
All work is a processsoft savings as other items need to be completed
All processes have opportunities for improvement,before this improvement could be realized in the
we just have to learn the process well enough to bebottom line.
able to find those opportunities. In order to improve