REPLY Getting a Good Problem Statement (SD6561)

[SDMAIL Jack Ring]

Posted by  "Jack Ring" <jring at amug.org>

Regarding Jean-Jacques' query (SD6528) ---

One proven way to arrive at a good problem statement is to engage the 
stakeholders in co-authoring a Concept of Operations that describes 
how stakeholdes will use the envisioned remedy or solution or therapy 
or system (but avoids nominating the content/structure of such system) 
and in co-authoring the companion Measures of Effectiveness and Standards of 
Acceptance that stakeholders will apply to any proferred remedy/solution/
therapy/system.  Guidance for creating a ConOps can be provided to those 
interested. 

Depending on a) the extent, variety, and ambiguity of the problematic 
situation and b) the extent, variety (diversity), and ambiguity (who's in 
charge, here) of the stakeholders the task of preparing a ConOps may take a
nywhere from five minutes to 100 days (but no longer) and the resulting 
artifact may range from a simple chart to a multipage simulation. Authoring 
a ConOps starts with modeling the problematic situaiton (as Jay has reminded 
us many times SD should be used for descriptive modeling) and ends with 
concensus that a sufficient basis exists for articulating the 12 or so 
Measures of Effectiveness.

Likely you will find that at least three "languages" are needed, a) 
conversational or narrative or natural, b) graphical, and c) 
mathematical.

cheers,
Jack Ring
Posted by  "Jack Ring" <jring at amug.org>
posting date  Mon, 3 Sep 2007 08:15:35 -0700