Models are not new, and neither models in the employ of product development. Product development has always had some basis in discovery and always will. If everything had such a high degree of certainty, likely the product or endeavor has already been done. Developing new things ceaselessly brings questions. To be effective, we want to answer these questions as quickly and as certainly as possible.
What is “watermelon” green? Watermelon. A great treat in the summer. The dark green rind, the yummy bright red center. Recently I had lunch with an IT friend named Phil. We were talking about checklists and determining project “status” when he mentioned the color Watermelon Green. I chuckled. Then I continued a bit afraid to […]
What is severity? We have been spending considerable time on risk in preparation for our up coming Piedmont Triad PMI Risk Management event. Our last specific risk blog we discussed risk and probability. That is only a part of the equation. We are interested in probability, but we also need to know the severity. Severity […]
TIEMPO – Test, Inspection, Evaluation Master Plan Organized by Jon M. Quigley and Kim Robertson PRODUCT DEVELOPMENT TEST, INSPECTION AND EVALUATION Ensuring product quality is not accomplished solely through testing and verification activities. Testing is but a fraction of the techniques that are at an organization’s disposal to improve their development quality. Good planning of the […]
Cell phones and Laptops, Tools – or the Distraction to Success Ever think your not getting the most out of your team due to distraction. The greatest invention perhaps is the smart phone. Now it is easy to check all of our email accounts, text message our friends, post on Facebook, blurt on Twitter, connect […]
Survival of the fittest is not just a biological concern. Our business must constantly adapt to external stimuli and find better, quicker ways of performing our work. One way to accomplish this growth is through actions sometimes referred to as project post mortem, or an after action report. We have a plethora of tools of […]
My work experience informs me that the loss of slack is a big risk to projects. Without this wiggle room, we reduce our probability of success. Projects scheduled out to the last available date just do not work. The reality is these are not manufacturing or routine tasks and jobs. Even the rather routine tasks […]
Our risk exposure starts at the beginning of the project. Even before the project is actually a project. The simple act of scoping a project in the initiating phase already alludes to the risks to which we may be exposed. For example, the minute we decide that our project scope is going to include software, […]
We break form our blog run on sprint meetings due to incoming flambé du jour. Sometimes we see organizations that are afraid to use the most fundamental of tools, for example, fault tracking from verification. Instead of using a tracking and visibility tool, we pass back and forth excel sheets behind the scenes. Why would […]
We strongly recommend automated testing whenever this approach is feasible. The test team can use a language designed for this kind of testing; for example, the National Instruments product Labview. The software should be able to read in the documented test cases, execute the test cases against the product, and finish by producing a […]