23-CS-4 Engineering Management · December 2014
Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
National Exams — December 2014 — 23-CS-4 Engineering Management (printed code 11-CS-4). Closed book; no calculators. Any five of the seven questions constitute a complete paper; all questions are of equal value. Answers are written in point form but fully, as instructed. Complete answers to all seven questions follow.
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.
Developing a new product, process, or service relies on established project-management techniques. The Work Breakdown Structure (WBS) decomposes the project into manageable work packages. Gantt charts display the schedule of activities against time. Network techniques—the Critical Path Method (CPM) and the Program Evaluation and Review Technique (PERT)—model activity dependencies to determine the project duration and the critical path, PERT adding probabilistic (optimistic/most-likely/pessimistic) duration estimates. Milestone charts track key checkpoints, resource levelling balances demand on people and equipment, and earned-value analysis integrates scope, schedule, and cost to measure performance. Stage-gate processes structure new-product development into phases separated by review gates. These techniques plan, schedule, and control the work.
Project management follows a recognized life cycle of process groups. Initiation defines the project, its objectives, scope, and feasibility, and authorizes it. Planning develops the detailed scope, WBS, schedule, budget, resource, quality, risk, and communication plans. Execution carries out the plan, coordinating people and resources to produce the deliverables. Monitoring and control runs in parallel, comparing actual progress against plan, managing changes, and taking corrective action. Closing completes and hands over the deliverables, obtains acceptance, releases resources, and captures lessons learned. Progressing deliberately through these steps, rather than plunging into execution, is what distinguishes managed projects from improvised ones.
Successful planning depends on clearly defining scope and objectives, decomposing work with a WBS, sequencing activities and identifying the critical path, estimating durations and costs realistically, allocating resources, building in contingency for risk, and setting measurable milestones and a control system. Projects fail for identifiable reasons: unclear or shifting scope ("scope creep"); unrealistic schedules or budgets; inadequate planning; poor communication; insufficient or mismanaged resources; weak risk management; lack of stakeholder or executive support; and poor leadership. Most failures trace back to deficiencies in the definition and planning phases rather than to execution alone, which is why disciplined up-front planning is the strongest predictor of success.
To develop a new control system, a project manager would define scope in a charter, build a WBS and a CPM network revealing that firmware development sits on the critical path, and track progress with earned-value analysis. By managing change formally and holding stage-gate reviews, the team would avoid the scope creep and unrealistic scheduling that most often derail such projects.
