
Behaviorally speaking: Defining the Software Development Life Cycle
Address
Bob Aiello raiello@acm.org
Bob Aiello - July 2002
Defining a Software Development LifeCycle (SDLC) can raise many behavioral or “people” related challenges. Any effort to specify how people should work is bound to meet with extensive resistance and even hostility on the part of the developers who must adhere to the development process. Yet it is essential that the successful CM Practitioner create a release process that is repeatable and predictable. Tremendous losses can occur if a major company has production applications that cannot be quickly fixed because they do not have the exact sources and build dependencies safeguarded and available. In this article, we would like to look at how to create a useful SDLC that specifies the workflow necessary to support the Software Development Process, especially Release Management.
Defining a Software Development LifeCycle (SDLC) can raise many behavioral or “people” related challenges. Any effort to specify how people should work is bound to meet with extensive resistance and even hostility on the part of the developers who must adhere to the development process. Yet it is essential that the successful CM Practitioner create a release process that is repeatable and predictable. Tremendous losses can occur if a major company has production applications that cannot be quickly fixed because they do not have the exact sources and build dependencies safeguarded and available. In this article, we would like to look at how to create a useful SDLC that specifies the workflow necessary to support the Software Development Process, especially Release Management.
Reviews (0)
Be the first to review this listing!
