The importance of WHAT not HOW when stating Scope and Requirements

04 July

Have a look at following two references from CIO magazine.

They support my arguments about the importance of using scoping techniques like the Context Diagram and the B5 technique. We should use these techniques, of course as part of understanding the “as is” business, but more importantly as a way of describing the business’s or system’s goals. this often can lead to the uncovering of additional opportunities to improve the value of the business.

The key factor when scoping and when understanding the “as is” (I prefer the term “what are we trying to achieve?” over the term “as is”) is to focus on the what and not on the how. Too early a focus on the how is as bad as committing the crime of premature design.

http://www.cio.com.au/article/309384/self_evident_truths_project_management_truth_10_success_comes_from_being_excellent_what_how?fp=39&fpid=26092

http://www.cio.com.au/article/308478/self_evident_truths_project_management_truth_9_-_value_management_makes_sense_project_governance

 

Posted by John Watson

CHAT
EMAIL
CALL