Transcription of Vol. 10, No. 1 …
{{id}} {{{paragraph}}}
Example: biology
Vol. 10, No. 1 …
2003 Vol. 10, No. 1 PRACTICAL PROCESSIMPROVEMENT PLANNINGBy Neil Potter and Mary SakryWe have seen many approaches to improvement planningduring the past 16 years. Two stand out as the mostcommon. With the first approach, small teams develop aplan to document the tasks they typically perform whenthey develop software. The notion is that if their currentpractices are documented, they can be shared among thedevelopment group and the best ones will become bestpractices. Unfortunately, the result is often a stack ofpaper that is the second approach,a company strides towardthe achievement of animprovement frameworksuch as ISO9001 or theSEI CMM1. The primaryfocus typically consists ofdeveloping animprovement plan tocreate procedures thatdescribe how the companyshould operate. Becausethe framework requires that procedures must exist,documenting them appears to be a logical first step and themost direct path to the goal. The result is often a mixtureof too-few benefits, universal frustration, and lots of these two examples, the approach to improvementplanning is the problem, not the use of a framework or thedefinition of best practices.
Understand customer needs. Clarify product requirements early. In this workshop, IN SEARCH OF EXCELLENT REQUIREMENTS, software engineers, managers, requirements analysts and user representatives learn how to gather,
Loading..
Tags:
Information
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document: