If you would like to "borrow" this Life Cycle, please send me an e-mail and ask permission first.
STATEMENT: All Development staff will comply with the Project Development Life Cycle for all systems development and enhancement work.
All Development staff will design, build, and support software in conformance with the Development Standards as outlined in this document.
All Development staff will use the standard project management approach consistent with the Project Development Life Cycle and the Development Standards to plan, organize, and control work effectively.
This policy ensures management control over the development process and provides for standard Development and Client milestones and deliverables. The use of the Project Development Life Cycle with its associated key deliverables will facilitate improved productivity and organizational flexibility and promote consistent, high quality applications.
All Development staff are responsible for compliance to this Life Cycle and for production of the key deliverables in conjunction with every project. All Development staff are required to comply to the Life cycle’s requirements during all phases of the project life cycle.
The Development Life cycle is as follows:
1. A request to do the project is submitted in writing from Marketing/Client to Development.
2. Development Department Manager/Analyst, along with a Marketing representative talks to the client to clarify the request.
3. Begin to organize the Beta Plan. Build the potential list of Beta clients, identify the requirements for a Beta Plan, and circulate for approval.
4. Create a high level design document (a requirements agreement) with a projected time estimate for review. At the review present a tentative project time line. This document is signed by development, marketing, and / or customer to signify acceptance.
5. Create a project file/ binder. It will include all supporting documents for the project.
6. Development Department Manager/Analyst determine resources for the project.
7. Create an Architecture Design Document. It will include the Beta Program, distribution methodology, etc.
8. Present the Architecture Design Document to programmers / Development staff for input.
9. Create the project time line. Include distribution, quality assurance, documentation, source control, etc. (stress person hours)
10. Conduct a walk-thru of the functionality of the Architecture Design Document and time line with the Client / Marketing representative.
11. Obtain the approval for the Architecture Design Document and time line from the Client / Marketing representative.
12. Circulate a project overview as internal notification to other company departments.
Go To Page: 1 2
