Project management is a team’s focus on the planning, organization, and execution of resources to meet specific goals. While many projects are viewed as temporary endeavors, at SRS we believe that even the smallest of jobs require a certain level of dedication and developmental emphasis on technical skills and management strategies.
The most challenging aspect of project management is to achieve all of the project goals and objectives while staying within the scope of your client’s requests. Although, even the greatest challenges can be overcome with the combined effort of a strong team like the units that have been created within our company.
A traditionally phased approach to project management identifies a series of five necessary steps, which if completed will ensure project success. These five developmental components are:
Not all projects will have every stage, as each project is unique. Some projects will not follow a structured planning and/or monitoring process. And some projects might repeat steps 2, 3 and 4 multiple times.
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 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. While the terms may differ from industry to industry, the actual stages typically follow these traditional steps to problem solving.