Gap analysis

Gap analysis

Key Gaps and Strengths

The below are the obstacles to avoid when developing software. These are acts of co-mission - things that the software groups should stop doing to have more reliable software. It's not as easy as it sounds to stop bad habits. Some bad habits should be stopped before others. The below shows a typical pecking order for getting rid of obstacles (bad habits).

keygaps.jpg (68467 bytes)

Other gaps are caused by "omission" or not doing something that you should. One common mistake is to attempt to improve software reliability by tackling gaps that aren't appropriate for the organization. An organization has to walk before it can run. We know that some gaps require prerequisites as evidenced by the results of our quantitative benchmarking study.

	Deliverables	Comments
The detailed assessment is a prerequisite for this service See price list	Identification of key gaps that separate your project from getting to the next percentile Identification of key strengths that separate your project from percentiles with bigger defect density Recommendations as applicable for how to execute the key gaps identified Checklists Helpful tips and hints Lessons learned	You must have an initial and detailed assessment prior to having a gaps and strengths analysis

Copyright, SoftRel, LLC 2011. This page may not be copied in part or in whole without written permission from Ann Marie Neufelder