For the first time in a long time, I am finding the bugs that have been logged very useful – they do provide an RCA for each bug & it’s those stats that provide the evidence for my recommendations.

unsubscribe at any time. Your email address will not be published. My questions are: 1) Was the first approach defective? We spend a lot of time and effort being careful about what we say. We care about our reputations, and we care about taking responsibility for the words that we use. Damaging: 100% – Using defects for people appraisal is one of the worst practices I have ever experienced, the damage can be immense. The customer becomes irrelevant and people focus on gaming the system to their benefit. Defects are one of the seven wastes of lean manufacturing or 7 mudas, defects are when products or service deviate from what the customer requires or the specification. I believe it is a very difficult wasteful practice to eradicate. In general, transportation waste can be caused by: Limiting transportation waste can be easily addressed by common-sense efforts such as simplifying processes, repairing physical layouts, handling products less often, and making distances between steps as short as possible. As you have probably already read the link I shared above you will know that engaging in such conversation is the type of waste called Overprocessing.

Parts assembled with the incorrect orientation. Isn’t a code review something that focuses on detecting defects? The waste of inventory involves storing products or materials that are not needed at this time. Nice post, thanks for taking the time to put it together & sharing. This waste occurs when there is supply in excess of real customer demand, which masks real production. But mainly, do the rest of the word care what you deprecated and what not? Semantics is the branch of knowledge and understanding concerned with the relationship between words and meaning. They do it to achieve specific results. She also said she likes to log the bugs so we keep track on them and revisit them in the future. Do you own a trademark on the words defect or bug?

MB 2) If the answer to the first question is yes, was the first approach wasteful? Every manufacturing defect results in waste. I doubt very much that the rest of the world, other than a vanishingly small part of it, cares what we have deprecated or not. It is probably the most common and most damaging type of waste that organizations encounter. Standardize processes, empower employees and eliminate unnecessary documentation, sign-off processes and meetings. Change ), You are commenting using your Twitter account. A defect is anything that threatens the value of the product. Key solutions include empowering your employees, stop micromanaging and increase training. We can anticipate wastefulness based on experience, but it’s important to remember that perception of waste is relative to the observer. (We prefer “bugs”. This is unacceptable, and now the vendor has created scrap. Email Lean Blitz Consulting, Subscribe to a daily digest of Lean Blitz posts by. In the factory, material… This article provides an introductory level overview of Six Sigma, which has experienced widespread... Reach Process Excellence professionals through cost-effective marketing opportunities to deliver your message, position yourself as a thought leader, and introduce new products, techniques and strategies to the market. To that list, I can now add “everything” and “immediately”. These questions sound like nit picking to me yes.

There are a few leaps & assumptions in your post that appear to have worked in your situation but I can imagine some scenarios where your ideas may fall down, such as: “The consequence of that conversation (that in some cases can involve also a product owner) should be let’s fix it now or let’s forget about it forever.”. 1/ Defects. People are not wrong to use words in the ways that they choose, although when the words are subject to interpretation and misinterpretation, it might be quite helpful if they could be explicit about what they were talking about.

Our industry has developed a defect coping mechanism that we call defect management. Such defects would not only take testers’s time, but would affect developers, product managers, business analysts and eventually clutter the defect management tool. Change ), Wasteful Activity #2: Playing with defects, Lean Software development – An Agile Toolkit, http://bizcraft.tumblr.com/post/37779031804/the-bug-myth, https://en.wikipedia.org/wiki/Muda_(Japanese_term), https://mysoftwarequality.wordpress.com/2014/10/12/the-agile-tester-a-curious-and-empathic-animal/, Ultimate Guide to Reducing the Amount of Defects and other Waste in your Product | mysoftwarequality, we don’t want to have defects that threaten the value of our product. These kinds of questions may be irritating to you. This will allow you not just to survive as a business but to thrive in today’s global markets. Pingback: Know Why You’re Being Paid | Lean Blitz – Do it better.

Join Process Excellence Network today and interact with a vibrant network of professionals, keeping up to date with the industry by accessing our wealth of articles, videos, live conferences and more. It could have been more efficient to have him pair with a more experienced programmer at design time. Nobody seems to think this is possible. The bug prioritisation meetings were battles where development managers argued any bug was a missed requirement, product managers argued that every bug was a coding error or a tester misunderstanding and the test lead (me) was simply shouted at and criticised for allowing his testers to go beyond the requirements and make use of their intellectual functions outside a scripted validation routine.

Some years back i was working on a business critical project in one of 5 scrum teams . The guidance from my client to the offshore org is that (paraphrased) they are not interested in bugs being raised during the development cycle. So what DO you mean?

I say we can, be patient and read on. we want to give our customers as much value as possible at all times. If like me years back, you are getting tired of filing, categorising, discussing, reporting, ordering defects I have a very quick solution. → Products that are shipped to the wrong address is also a defect. Defects have been around for as long as manufacturing has, and it can be the result of human or machine error, design issues, or poor quality material. The trouble with all that is not that you are infringing on any law, but that (in the first case) you make assertions that are simply untrue and that misrepresent what other people say—and thank you for acknowledging this and fixing it; (in the second case) you would be saying something that will make people believe that you are stupid or crazy (which not even I believe); or (in the third case) that you will oversimplify things to the degree that you will say something fatuous and shallow like “fix all defects as soon as you find them”. She would log a bug for the simplest of things, even if I am sitting next to her. Testers were to be judged on the Defect Detection Index calculated as (Number of Defects detected during testing / Total number of Defects detected including production)*100.

Completely eradicating any form of waste is impossible, but defects can certainly be limited by the application of standardized work plans, more stringent quality control at all levels, a full understanding of work requirements and customer needs, and simple job aids such as checklists. Defects can be caused by many different problems, many that should be avoidable with a little thought when designing your products, processes and equipment.

Defects Waste Examples: → Software with bugs is a defect that has to be re-coded.