START WITH THE FOUNDATIONS

Engineering Management Foundations

Connect project scope, cost evidence and clear professional communication.

Free · No sign-in required3 lessonsWorked examples & practiceBeginner

0 of 3 lessons checked · Progress is saved in this browser.

  1. 01 / SYSTEM VIEWDefined outcome
  2. 02 / SYSTEM VIEWPlan and delivery
  3. 03 / SYSTEM VIEWEvidence and handover

This map connects the course ideas; it is not a detailed engineering schematic.

LESSON 1 / 3 · FREE

Scope and acceptance

Your goal: Describe a deliverable in terms someone can verify.

Understand the idea

A project scope states what will be delivered and the boundaries of the work. Acceptance criteria make completion observable. Separate an activity from its output and record changes through an agreed process. A schedule entry saying complete is not evidence that the recipient’s needs were met.

Worked example

A fictional package requires 10 reviewed drawings and 2 reports: 12 deliverables. Their count does not measure equivalent effort or verify acceptance.

Try it yourself

A package requires 8 drawings and 3 reports. How many deliverables are counted?

Which is an acceptance criterion?

Background reference ↗ · Original teaching text and fictional practice values.

Continue to lesson 2: Cost and variance →

LESSON 2 / 3 · FREE

Cost and variance

Your goal: State the baseline and sign convention for a cost comparison.

Understand the idea

Compare actual cost with the approved scope and baseline for the same work. In this lesson overrun is actual minus budget. A favorable cost number may hide incomplete scope, so evaluate progress and quality as well. Forecasts are estimates with assumptions, not guarantees.

Worked example

A fictional completed package budgeted at 10,000 currency units costs 11,000. Overrun is 1,000, or 10 percent of budget.

Try it yourself

For budget 20,000 and actual 22,000 on the same completed scope, find overrun percentage.

Can low spending alone prove project success?

Background reference ↗ · Original teaching text and fictional practice values.

Continue to lesson 3: Communication and handover →

LESSON 3 / 3 · FREE

Communication and handover

Your goal: Separate observations, decisions and assigned actions.

Understand the idea

A useful technical handover states what was observed, why it matters, what remains uncertain and who owns each action. Distinguish a confirmed finding from a hypothesis. Record due dates and closure evidence so the next person can continue without reconstructing the conversation.

Worked example

A fictional handover has 12 actions, with 9 closed and 3 still assigned. Closure fraction is 75 percent; unresolved high-impact items may still prevent completion.

Try it yourself

Of 20 assigned actions, 16 have verified closure. Find closure percentage.

What should distinguish a closed action?

Background reference ↗ · Original teaching text and fictional practice values.

Choose your next step →

Finish with evidence of your understanding.

Explain each worked example in your own words, check the units and identify one assumption that could change the result. Then use the linked labs or roadmap to apply the ideas to a broader task.

Practice progress is a study aid, not a professional qualification or proof of field competence.

Continue in Engineering Management, Business & Professional Skills

Apply these foundations in an available course, lab or roadmap. The linked resource’s access rules still apply.

Show 4 more available resources

Open the full studio → · Choose another discipline →

About this introductory course

These original lessons use simplified models and explicitly supplied practice values. Calculations teach concepts; they do not select real equipment, establish code compliance or authorize field work. Follow the linked references and advanced resources for deeper study.

Updated · Study progress stays in this browser. There is no certificate or paid gate for these lessons.