Qualitative Testing Qualitative tests look for a change in a quality; for example, a color might change. Qualitative tests always involve the use of attributes rather than variables values (e.g., temperature). Consider the Kastle-Meyer test for the presence of blood–an archetype for qualitative forensic testing. The test is impressively quick and functions as a decision […]
Archive for the
‘Requirements Management’ Category
Manufacturing Project The project whose scope includes delivery through manufacturing will include some quality assurance steps from the previous blog post to ensure we are able to produce the designed product to the quality expected by the sponsor. Trial Production Run and Problem Discovery The manufacturing team reviews the development of the manufacturing line with […]
Requirements testing There is a Twitter discussion going on regarding “Testers do not break the product.” I am not so sure this is true in all contexts. Consider for example, embedded products. Our organization will almost certainly have a multiple perspective approach to the testing of that product. One of those would be test the […]
What is concurrent engineering? Concurrent engineering is when activities are paralleled that could be sequenced. Concurrent engineering can help us deliver the product earlier since we have compressed the schedule by overlapping the various development activities. There are certain risks associated with this way of working. To be successful and not incur massive rework, it […]
By Kim Robertson and Jon M. Quigley Leveraged Innovation Logistics Mike and Akio had been invited to one of the Genesis Test Equipment logistic repair depot by Lina Hendrik, the facility manager to discuss an idea she had regarding retrofit of a discontinued product line still widely used in an automotive niche market segment. As […]
Our making the measurements up or arbitrarily assigning values is of little help. Dismissing the standards as bloated without knowing is not productive. Standards are not evil, no more than ad hoc and on the fly are.
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 are we trying to accomplish with a communications plan? Effective project management is the efficient achieving of an organization’s objectives. To do that, we have to keep our project team informed and working toward the target. That includes our project sponsor and other stakeholders. Ultimately our plan should be able to quickly answer the […]
The daily sprint meeting has connections to our risk management as well. We have seen from the previous posting the fact we are having the meeting daily can hasten our project’s (system’s) ability to respond. The sprint master is now asking about the obstacles or impediments to achieving the objectives of the sprint. Impediments and […]
We felt the need to follow on from our previous blog on tracking testing results in the background using hidden ubiquitous spreadsheet or documents. If all you have is a spreadsheet for tracking, then you make that visible to all relevant stakeholders. If the company has a sanctioned or preferred way of handling “bugs” and […]