Teams must grow; teams cannot be simply appointed and anointed. We may have a designated group that evolves into a team, but this emergent phenomenon takes time. It takes time to discover the strengths and weakness if each member of the group, understanding that ultimately transforms into trust, the backbone value/concept for any successful team. […]
Occasionally, we are put in the position of removing an employee; that is, we must fire them. In many cases, we will not have enough documentation to validate the ineptitude of such an employee. Furthermore, we may not have a standard algorithm (procedure) to follow when removing this individual. Many companies add the impediment of […]
People in education often like to implement “programs.” In fact, we call this syndrome “program-itis” because it leads to inflammation of the budget. As with many corporation, we see people who want to improve a situation decide to follow “best practices” without verifying that these are, in fact, best practices. They can only be best […]
Creating a separate software test group has pluses and minuses. At a minimum, we may have more to manage. Some of the minuses are a product of human nature. When we know our work will be inspected, we will often assume the inspector will catch issues and we pay less attention to the issue ourselves. […]
The Pareto chart (not to be directly confused with the Pareto probability distribution function) is a simple approach to revealing significance in data. Before we plot our chart, we need to complete some initial work: Gather the data in a natural format (count, floating point [decimal], dollars, etc.) Sort the data from high to low […]
We have been on a bit a tear (or rant) about FMEAs. We suggest the FMEA documentation is part of the core of a design process. The ultimate approach we have seen is that of Michael Anleitner (The Power of Deduction: Failure Modes and Effects Analysis for Design, Quality Press, 2010), which uses functional analysis […]
There is only one way to describe this scenario and that is via a story. Consider the organization that is coming to the end of the project. The product is a complicated subassembly that goes into a larger system and has numerous interactions and incarnations of the design. They are late in the delivery of […]
Risks can have origins in communications and are not the sole province of the stakeholders and sponsors of the project. Sometimes the organization damages itself via the structure. We are all familiar with the functional organization, often referred to as a line organization or stove pipe organization in which we group the company by discipline. […]
This blog post is born out of a response to the Named Risk post from Ed Arnold on www.LinkedIn.com. He left the reply below: In my experience, a lot of time/effort is wasted when project owners change. The knowledge gets lost, even if they leave their spreadsheets and power points behind. The answer: a collaborative […]
We addressed the issue of the modular FMEA in a previous blog. We also suggest that the FMEA in its various guises is also a great place to capture lessons learned. In the medical, aerospace, automotive, and food industries, some kind of FMEA is a required document. Since we already must create these documents, why […]