Quote of the Day
Glen Alleman MSSM
Applying Systems Engineering Principles, Processes & Practices to Increase Probability of Program Success for Complex System of Systems, in Aerospace & Defense, Enterprise IT, and Process and Safety Industries
Clay is molded to make a vessel, but the utility of the vessel lies in the space where there is nothing... Thus taking advantage of what is, we recognize the utility of what is not ― Tao Te Ching, Chapter 41, Lao Tze, 604-531- BC
When we think about solutions looking for a problem to solve, think of the vessel. We must recognize the utility of the solution before that solution becomes of any value.
To recognize any value, we must define the units of measure of that value, starting with Measures of Effectiveness (MOE) and Measures of Performance (MOP). With those in hand, define the Technical Performance Measures (TPM), the Key Performance Parameters (KPP), and Key System Attributes (KSA), and any measure that is Critical to Customer (CTC) success.
A Step-by-Step Plan to Produce Value from any Proposed Solution
Without measures defined upfront the acquisition of the solution has no means of confirming its value.
Let's start with my favorite - Agile Transition by buying Disciplined Agile.
Without answers to these steps at the start, you'll never know what done looks like other than when you run out of time and money. And without frequent assessments of the deployment of the solution against these measures, you'll never recognize Done, if and when it ever arrives.
This is not only the failing of the current agile solution domain, it's common in many domains and is a common failure of treating symptoms rather than finding and treating the root cause of that symptom.
From public health to transportation systems, to any project success, to buying a technological solution looking for a problem to solve,