When a project manager plans a project, it is always good to separate the project into smaller phases. The project life cycle is the collection of all the phases come together to form the main project. Breaking a project down into phases allows for easier management and can help with uncertainty. Depending on the project there will be a deliverable, which can be a segment of code, a product or service that is produced in each phase. In a traditional project life cycle, there are four project phases. The first two are a concept and the development which is primarily the planning phase. In the concept phase, common deliverables are preliminary cost estimate, business case. In the second phase “development” the deliverable are budgetary cost estimates, and project management plan. In the implementation phase definitive cost estimates, performance reports, execution of work are the usual deliverables. In the final phases which are implementation and closeout. In the final phases of the project, it would be devoted to producing the work, this is often called project acquisition. In order for the project life cycle to work properly each one of the phases has to be completed before moving on to the next phase of the project. During the close-out phase, it’s important to document your work and lessons learned, also remember to ensure that the customer is happy with the completion of the project. There is a framework which helps explains the phases of developing information systems which are called systems development life cycle (SDLC). Common models from the SDLC are waterfall model, the spiral model, the incremental build model, the prototyping model, and the Rapid application development model (RAD). These particular life cycle models are samples of how the project scope can be articulated and the cost and schedule be clarify predicated this is called a predictive life cycle.