Design a site like this with WordPress.com
Get started

Why we should work in small batches – a story from Japan

“The ability to work and deliver in small batches is especially important” [1], which is why many development teams work in small batches.  Scrum teams work in small batches by limiting the work they plan to do in a sprint. Kanban teams work in small batches by limiting the work in progress. Working in small …

First Thoughts on a System of Profound Testing

W. Edwards Demings’s System of Profound Knowledge (SoPK) is a valuable framework for leadership. SoPK provides a view, which Deming called a lens, “by which to understand the organisations we work in”[1]. The SoPK is “a framework for applying best efforts to the right tasks”[2]. There are four parts to the SoPK: The theory that …

A review of “Total Quality Control – the Japanese Way” by Kaoru Ishikawa

Kaoru Ishikawa was a significant figure in the development of quality in Japan. In his book Total Quality Control – The Japanese Way he describes many of the ways that Japanese businesses achieve quality. His book contains many points that are useful to testing professionals.  He wrote that the very essence of Total Quality Control …

Definitions of Done, Team Agreements, Ways of Working and Checklists have so much in common

Many teams, create a definition of done to clarify what putting a card in the Done column on a scrum or kanban board means. A good number of teams also have team agreements or ‘ways of working’ which define ways in which the teams work. Also, some teams have checklists of items that need to …

The Five S’s create a structure for test automation

I use the Five S’s to create a disciplined structure that helps me create and maintain automated tests. Mary and Tom Poppendiek recommend using the Five S’s to create the discipline necessary to develop quality software. They wrote that “the five S’s are a classic lean tool to organise a workspace” [1].  Mary and Tom …

Using plan-do-study-act to improve testing

Testers and developers can use the Deming Cycle to improve the quality of their testing. The Deming Cycle was initially used in the manufacture of telephones and has had a big influence on software development. The cycle has four steps: The cycle should be repeated with the knowledge accumulated.  The Deming Cycle can be described …

We need to remove barriers to good work

If we want to make good quality software we need to remove barriers to good work. Dr Deming‘s 14 Points for management were the basis for lessons for top management in Japan. Dr Deming said that “the 14 Points apply anywhere, to small organisations as well as to large organisations[1]”. Point 12  is to “remove …

Using Ishikawa diagrams to improve quality

Cause-effect diagrams are a useful technique that can be used to improve quality.  Glenford J. Myers wrote that “a weakness of boundary value analysis and equivalence partitions is that they do not explore combinations of input circumstances”[1]. A technique that can be used to explore and describe combinations of inputs to an issue is a …

Using the Five Whys to improve quality

The Five Whys is a technique for finding the root cause of a problem. Toyota developed this technique and it is now widely used, including in software development. I was introduced to the Five Whys by Tom Gilb as part of a course he ran on Lean QA and have used the Five Whys in …

Should we practice continuous learning?

I enjoy working in an organisation where we are learning from the work we do. An example of this would be using retrospectives to enable the team to learn from their work and taking this knowledge forward to help the team.  Until recently I have called this approach continuous learning. It sounded right, as it …

How have approaches to quality changed over the past 20 years?

We can all learn a great deal from people who have influenced our industry. BCS SIGiST recently hosted a discussion with Mary and Tom Poppendieck about “How have approaches to quality changed over the past 20 years?”. Mary Poppendieck wrote books with her husband Tom about Lean Software Development based on her experience of applying …

Don’t ask “Why did the tester miss that bug?”

“Why did the tester miss that bug?” is a question I have heard in many places but it is the wrong question. W. Edwards Deming’s philosophy shows that if something has gone wrong we need to look at the process and not blame the individual. A tester can be working in a system that the …

Four insights from “a reference book for all who all who are involved with quality”

Joseph Juran wrote in the 5th Edition that Juran’s Quality Handbook ”is a reference book for all who are involved with quality of products, services, and processes”. I find it a useful book to refer to if I am thinking about a problem. There are eight editions of the Juran’s Quality Control Handbook. They are …

What job should you hire a tester to do?

Jobs Theory gives us a way of understanding clients by asking what job did they “hire” a product or service for. An example of Jobs Theory is given in “Competing Against Luck”: by Clayton M. Christensen, Taddy Hall, Karen Dillon and David S. Duncan. The example they give explains why people “hired” milk shakes. Research …

One cycle to inspire them all

I have worked in lean or agile teams for a number of years and developing my knowledge of lean and agile has helped me. The Deming Cycle is something I have found helpful to understand because it is a part of agile and lean and it is also about continuous improvement of quality. Engineering teams …