Topic: Applying standards/models for software process imp

When you read business success stories, they often advise that you need to begin your business/software process improvement journey by first applying a standard or model. However, when you speak to these successful businesses, a commonality stands out -- they use standards and models not as bibles but as planning tools and as checklists to be considered when determining completeness of their planned efforts.  Using standards and models in this manner is like using a roadmap when you take a journey.

Everyone will agree, a roadmap is a great initial planning tool and a good guide to a new never yet travelled destination (goal).  The roadmap shows you many routes (choices) to your destination and possibly, the type of terrain--divided highway, paved road, gravel road, mountains, dessert, and so forth. The roadmap indicates what is possible and often potential rewards (points of interest). It does not dictate how (the route to take), where to stop (gas stations, tourism centers,...), nor advise on the required resources (the type of vehicle for the terrain), costs (the recommended luxury of your vehicle), schedule (the speed of travel) and expected return-on-investment (which point of interests are worth your efforts/focus).