Project Planning

The primary challenge of project management is to achieve all of the project goals and constraints.[5] This information is usually described in a user or project manual, which is created at the beginning of the development. The primary constraints are scope, time, quality and budget.[6] The secondary — and more ambitious — challenge is to optimize the allocation of necessary inputs and integrate them to meet pre-defined objectives.

Approaches

There are a number of approaches for managing project activities including lean, iterative, incremental, and phased approaches.

Regardless of the methodology employed, careful consideration must be given to the overall project objectives, timeline, and cost, as well as the roles and responsibilities of all participants and stakeholders.

The traditional approach

A traditional phased approach identifies a sequence of steps to be completed. In the "traditional approach", five developmental components of a project can be distinguished (four stages plus control):

Typical development phases of an engineering project

  • initiation
  • planning and design
  • execution and construction
  • monitoring and controlling systems
  • completion and finish point

Many industries use variations of these project stages. For example, when working on a brick-and-mortar design and construction, projects will typically progress through stages like pre-planning, conceptual design, schematic design, design development, construction drawings (or contract documents), and construction administration. In software development, this approach is often known as the waterfall model, i.e., one series of tasks after another in linear sequence. In software development many organizations have adapted the Rational Unified Process (RUP) to fit this methodology, although RUP does not require or explicitly recommend this practice. Waterfall development works well for small, well defined projects, but often fails in larger projects of undefined and ambiguous nature. The Cone of Uncertainty explains some of this as the planning made on the initial phase of the project suffers from a high degree of uncertainty. This becomes especially true as software development is often the realization of a new or novel product. In projects where requirements have not been finalized and can change, requirements management is used to develop an accurate and complete definition of the behavior of software that can serve as the basis for software development.[20] While the terms may differ from industry to industry, the actual stages typically follow common steps to problem solving—"defining the problem, weighing options, choosing a path, implementation and evaluation."


APRP took this question and finally answer long distances. Utter capacity planning is staggering, especially replica watches when you realized the mechanical problems that require solutions are bizarre and random at best. What APRP did not have to say, "because the minute hand to prevent the crown uk rolex replica stick dial can do it just skip the 10-minute period of fake swiss replica watches the clock face. The rest of the time it is more or less replica rolex watches designed around what it means.