The project life cycle outlines the processes that should be followed when undertaking a project to give it the best chance of producing a product that meets as many of the client's requirements as possible.
The project life cycle consists of four stages...
i nitiation is the first phase, during which the requirements of the product, resources available and any are deadlines constraints rules designs considered in order to determine whether or not the project should go ahead. The second stage of the project life cycle, , is where the various tasks that need to be carried out will be determined (along with establishing suitable milestones) - planning design execution initiation and the designs for the product will be drawn up. Execution is the third stage - this involves both production and of the actual product. evaluation testing documentation prototyping is where the final product is released, the user documentation is created, and the success of the project is reviewed. Planning Initiation Evaluation Execution
However, the project should not only be assessed at this final stage -
reviews should occur throughout the project life cycle. Each stage of the project life cycle requires some sort of SMART user iterative limited before it can begin, and produces an input output milestone feasibility report which is usually used by the next stage of the cycle. output milestone input feasibility report
During the initial stage of the project, you must consider the
(the needs of the client, and what they want the final product to do), the success criteria critical path constraints user requirements (the restrictions on the product, such as its constraints user requirements critical path success criteria , that limit what the project is able to accomplish), and the potential success criteria task list objectives budget facing the project and how to mitigate them. From this you can create risks milestones opportunities objectives goals, objectives for the project that are: specific (clear and unambiguous); prototype success iterative SMART (have some way in which the success of the goal can be assessed); achievable (can actually be accomplished); tasked timed measurable marked (can be achieved when taking the project's limitations and resources into consideration); and can be accomplished in a reasonable time. These goals can then be assessed by creating reported realistic right required , which are used to determine whether or not the project has achieved what it intended to do. constraints success criteria task lists critical paths