INTRODUCTION  
To maximize the success of IT projects and operations throughout the entire IT life cycle, We follow a definite guideline and proven practices for effectively planning, building, deploying, and operating solutions. Creating a business solution on time and within budget requires a proven practice for planning, building and deploying successful IT solutions. The guidance consists of principles, models, and disciplines for managing the people, process, and technology elements that most projects encounter. This procedure is to describe the process and methodologies that should be used in managing a software development project. 
It covers the life cycle of a solution from project inception to live deployment. This helps project teams focus on customer business value, since no value is realized until the solution is deployed and in operation. 
CBDM is  a milestone-driven process. Milestones are points in the project when important deliverables have been completed and can be reviewed.

1. Sales Handover and Project Initiation  
Upon receiving authorization from the client to commence work on a project there should be a formal handover from the sales function to the project management / production function within the organization.
2. Project Scope  
Scope is the sum of deliverables and services to be provided in the project. The scope defines what must be done to support the shared vision. It integrates the shared vision, mapped against reality, and reflects what the customer deems essential for success of the release. 
The Scope should also identify the business requirements or business issues that the system is required to fulfil. It should deal with issues such as the business problem that has been identified and the solution that is required.
3. Functional Specification  
The Functional  Specification  describes in detail, what the system is to do, not necessarily how it is to do it. The Functional Specification follows from the Business Requirement Specification but at a much more detailed level.
4. Technical Specification  
The technical specification describes the ‘how’ of a system design. There should be enough technical detail in the specification to enable the document to be handed to a project team with instructions to build one of these. The technical specification includes detailed descriptions of how each of the functional requirements are to be achieved and how the system will flow together.
5. Project Delivery Planning
After completion of technical specifications a project plan should be created for programming, testing and delivery of the system. This project plan should identify the major steps involved in completing the software, any identified milestones should be included in the plan and it should identify the critical path.
6. Test Planning  
Test planning is a method of formally documenting the process of testing each element of the project. Test planning involves defining scripts which give a detailed description of what is to be tested and how it is to be tested at the unit test integration and user acceptance level. The test methodology defines a formal method of testing conducted in accordance with a test plan.
7. Program Development  
The duties undertaken during program development are:

• development of graphics for websites and forms applications
• writing a code in various languages such as Visual Basic, C Java, Active Server Pages, etc.
• development of database tables and other database objects such as Views, Triggers, Store procedures and so on.

Unit testing should occur at this stage. It is the programmer’s responsibility to perform unit testing before handing the completed item of work to the QA for quality assurance testing.
8. Testing Phases
The following testing phases will be undertaken:

1. Unit test
2. Integration testing
3. Regression testing
4. User acceptance testing

9. Training/Documentation Development
In this step the user documentation and training material are prepared. This is to be completed prior to user acceptance testing. Tasks include creating user documentation, prepare staff training material, create and document help files to be used.
10. Implementation Details
This step is to plan the delivery of the project at a lower level
11. Delivery to Production
After satisfactory system release tests have been performed and all required sign off obtained, a new application, or changes, to an existing application are ready for migration into the production environment
12. Post Implementation Reviews
Post implementation reviews are to assess the success and timeliness of the activity and to initiate improvements based on experience gained during the activity. Once the review is complete and no deficiencies resulting from the change have been identified, the system can be signed off.