Question 3 of 7: Project Management Techniques, Steps and Failure

Question 3: Project Management Techniques, Steps and Failure (20 marks)

Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.

(i) Project Management Techniques for New Development

New product, process, or service development is coordinated using a recognized toolkit of project-management techniques. The Work Breakdown Structure (WBS) decomposes the total scope hierarchically into manageable work packages. Scheduling networks—the Critical Path Method (CPM) and PERT—establish the sequence of activities, their dependencies, and the longest (critical) path that fixes the minimum duration; PERT additionally uses optimistic, most-likely, and pessimistic estimates to treat duration as probabilistic. Gantt charts present the schedule graphically against a calendar and are the common medium for tracking progress. Milestone charts mark key completion points, and stage-gate (phase-gate) reviews impose go/no-go decision points between development phases. Earned Value Management (EVM) integrates scope, schedule, and cost to measure performance against plan, while resource levelling and risk-management techniques round out the set. For product development specifically, concurrent engineering and Quality Function Deployment link the technical work to customer requirements.

(ii) Basic Steps in Managing a Project

Managing a project follows the classic life-cycle phases. Initiation defines the project, its objectives, scope, and business justification, and secures authorization (a project charter) and a sponsor. Planning is the most detailed phase: the scope is broken down through a WBS, activities are sequenced and estimated, the schedule and budget are built, and plans for resources, quality, risk, communication, and procurement are prepared. Execution carries out the plan—acquiring and directing the team and resources to produce the deliverables. Monitoring and control runs in parallel with execution, comparing actual progress, cost, and quality against the baseline, managing changes, and taking corrective action to keep the project on track. Finally, closing formally completes the project: deliverables are handed over and accepted, contracts and accounts are closed, the team is released, and lessons learned are documented for future projects. These phases correspond to the enduring management functions of planning, organizing, leading, and controlling applied to a temporary endeavour.

(iii) Techniques for Successful Planning, and Reasons for Failure

Successful project planning rests on several techniques: clearly and completely defining scope and requirements at the outset; building a thorough WBS; making realistic estimates of duration and cost that include contingency; identifying the critical path and dependencies; assigning clear responsibility for each package; performing proactive risk analysis; and establishing measurable milestones and control mechanisms with active stakeholder communication. Projects fail, conversely, for identifiable and largely avoidable reasons: poorly defined or continuously changing scope ("scope creep"); unrealistic schedules and budgets set by optimism or external pressure; inadequate planning and risk management; weak or absent executive sponsorship; poor communication among stakeholders; insufficient or unskilled resources; and lack of user or customer involvement so that the delivered product misses real needs. Recognizing these failure modes is itself a planning technique, because each can be countered by a specific control.

Practical Application

A team developing a new instrumentation product would open with a charter and a WBS separating hardware, firmware, and certification work, then build a CPM network that reveals regulatory approval as the critical path. Weekly earned-value reporting during execution would flag a cost overrun early, and a mid-project stage-gate would confirm the business case before committing to tooling. By fixing scope, resourcing the critical path, and maintaining sponsor engagement, the manager directly forecloses the most common causes of failure.