Building on a Good Reliability Goal
If we set a product reliability goal of 99% reliable over two years in the requirements document, what are we supposed to do tomorrow? On the other hand, if our goal is to write 1,000 pages for the next great novel by the end of the year and we have no pages written so far, well, we should write a page or two tomorrow.
A good goal provides a vision, a measurable milestone, a target. What it lacks is what we do from now till achieving that goal. If the goal is 1,000 pages in 365 days, we may want to set up a process to write at least 3 pages per day.
So, given a reliability goal, what do we do tomorrow, next week, and each week between now and when the goal is due?
A Good Reliability Goal
In previous work, I’ve written about setting reliability goals, connecting the goal to customer expectations, technical capability, and business needs. Plus, have written about the four (five) parts of a complete goal, including Function(s), Environment, Duration, and Probability (and all four continue to get more difficult as customers expect more).
A well-stated reliability goal provides direction and a measurable target for the entire team. It provides a basis to compare progress and to help frame “is the design reliable enough yet” discussions.
This is all well and good, yet is it enough? [Read more…]