In the 1990s, software process improvement was primarily promoted under the auspices of achieving the requirements of various standards/models. Tantara believes standards/models have a role in software process improvement but need not be a prerequisite to business excellence.
Applying standards/models for software process improvement
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).
Some roadmaps can also help achieve different objectives:
For example, two travellers may have the same destination (e.g., the goal to attend a family reunion in city XYZ) with different objectives: one traveller may desire the quickest route (hence, will use a roadmap indicating interstate highways) while the other traveller may want to visit friends on the way (hence, will use a roadmap indicating routes to towns and cities)--note: some roadmaps will accomplish both set of objectives.
Applying standards/models for software process improvement
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).
Some roadmaps can also help achieve different objectives:
For example, two travellers may have the same destination (e.g., the goal to attend a family reunion in city XYZ) with different objectives: one traveller may desire the quickest route (hence, will use a roadmap indicating interstate highways) while the other traveller may want to visit friends on the way (hence, will use a roadmap indicating routes to towns and cities)--note: some roadmaps will accomplish both set of objectives.
Tidak ada komentar:
Posting Komentar