The Project Life Cycle and Initial Considerations GapFill

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...

Project initiation is the first phase, during which the requirements of the product, resources available and any budgets prototypes constraints rules are considered in order to determine whether or not the project should go ahead. The second stage of the project life cycle, execution visualisation evaluation planning , is where the various tasks that need to be carried out will be determined (along with establishing suitable milestones) - and the designs for the product will be drawn up.  Execution is the third stage - this involves both production and maintenance documentation delivery testing of the actual product. Visualisation Evaluation Initiation Limitation is where the final product is released, the user documentation is created, and the success of the project is reviewed.

However, the project should not only be assessed at this final stage - iterative limited constraint asset reviews should occur throughout the project life cycle. Each stage of the project life cycle requires some sort of task list output constraint input before it can begin, and produces an constraint input output task list which is usually used by the next stage of the cycle.

During the initial stage of the project, you must consider the constraints user requirements user contingencies milestones (the needs of the client, and what they want the final product to do), the user requirements user contingencies constraints milestones (the restrictions on the product, such as its asset log prototype budget task list , that limit what the project is able to accomplish), and the potential opportunities risks success criteria reviews facing the project and how to mitigate them. From this you can create SMART PERT START prototype goals, objectives for the project that are: specific (clear and unambiguous); measurable timed triggered milestoned (have some way in which the success of the goal can be assessed); achievable (can actually be accomplished); realistic risky ready required (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 success criteria feasibility reports contingencies task lists , which are used to determine whether or not the project has achieved what it intended to do.