Design Methodology · Study deck

IoT Project Planning: Brief and Viability

A project brief links a user problem to the work the team can fund.

Blueprint Bina is your guide for this deck.

thinkingprojectplanning
Blueprint Bina, the module guide, in a scene from this chapter.
iotclass.org

After studying this chapter

Learning objectives

You will be able to:

  • Explain: Where supported, the device can trigger pedestrian crossing signals, and it can give step-by-step directions and bus route and pickup times through a Bluetooth earpiece.
  • Explain: French startup Handisco built a Bluetooth-connected, GPS-enabled cane attachment called Sherpa so blind and vision-impaired pedestrians could navigate their communities more independently.
  • Explain: That gap is not a flaw in the canvas; it is exactly what the assumption map in this chapter's project brief exists to catch.
  • Explain: Reuses the brief's problem frame and target users -- it should not be re-researched from scratch.
iotclass.org

Major section

Build the Project Brief

The project brief is the planning anchor.

  • User group, context, pain, current workaround, and desired change.
  • The statement would still make sense if the proposed technology were removed.
  • Primary users, secondary users, maintainers, installers, support staff, and data owners.
  • Each user group has a need, constraint, or decision that affects the plan.

Why it matters

The boundary prevents accidental expansion when new ideas appear.

An evidence board keeps the project brief, research notes, unresolved risks, and next checks in one readable structure.
An evidence board keeps the project brief, research notes, unresolved risks, and next checks in one readable structure.
iotclass.org

Major section

Build the Project Brief (continued)

The boundary prevents accidental expansion when new ideas appear.

  • The measure is tied to user value, not only device activity.
  • Unknowns about desirability, feasibility, data quality, deployment, security, privacy, and support.
  • Each gap has an owner and an evidence check.
  • The gate can block work when evidence is weak.
iotclass.org

Major section

Check Commercial Viability with a Lean Canvas

A Lean Canvas is that tool: a one-page way to make the commercial case reviewable alongside the brief.

  • The project brief records what the team plans to build and which technical and operational assumptions still need evidence.
  • Design Thinking Introduction names desirability, feasibility, and viability as three lenses a connected product has to satisfy together.
  • Reuses the brief's problem frame and target users -- it should not be re-researched from scratch.
iotclass.org

Major section

Worked Example: A Cane Attachment for Independent Navigation

French startup Handisco built a Bluetooth-connected, GPS-enabled cane attachment called Sherpa so blind and vision-impaired pedestrians could navigate their communities more independently.

  • Where supported, the device can trigger pedestrian crossing signals, and it can give step-by-step directions and bus route and pickup times through a Bluetooth earpiece.
  • That gap is not a flaw in the canvas; it is exactly what the assumption map in this chapter's project brief exists to catch.
  • A canvas block with no evidence behind it is still an assumption, not a fact.
iotclass.org

Major section

Align Stakeholders, Hold Scope

IoT projects cross physical devices, software services, data governance, field operations, and support.

  • Stakeholder alignment is therefore more than approval.
  • Whether the workflow is useful and understandable.
  • Whether the device can be installed, supported, and recovered.
  • Whether data is collected, retained, shared, and deleted appropriately.
iotclass.org

Major section

Turn Scope Into Work Packages

Once the brief and assumption map are clear, split the project into work packages.

  • A work package is not just a task.
  • Problem frame and evidence gaps are agreed by user and sponsor representatives.
  • Prototype shows the required behavior under realistic constraints.
  • Users can complete the target action without extra explanation.
iotclass.org

Major section

Risk Register and Release Gates

The risk register connects uncertainty to action.

  • Each risk needs a trigger, mitigation, owner, and gate.
  • Without a gate, the register becomes a list that people read but do not use.
  • Users cannot say what they would do with the alert.
  • Device identity, update, credential, or access decisions are still unresolved.
iotclass.org

Deck summary

Key takeaways

The project brief is the planning anchor.

  • The boundary prevents accidental expansion when new ideas appear.
  • A Lean Canvas is that tool: a one-page way to make the commercial case reviewable alongside the brief.
  • French startup Handisco built a Bluetooth-connected, GPS-enabled cane attachment called Sherpa so blind and vision-impaired pedestrians could navigate their communities more independently.
  • IoT projects cross physical devices, software services, data governance, field operations, and support.
iotclass.org

Retrieval practice

Recall check 1 of 5

Blueprint Bina says: answer from memory, then check your reasoning.

Q1A team has a list of device features, but no user action, no evidence gaps, and no out-of-scope list. What is the best planning response?

AStart implementation from the feature list without naming user action or evidence gaps.
BAdd more features before asking stakeholders to define the project boundary.
CSkip stakeholder review until the first device is built and the scope is fixed.
DTurn the list into a project brief before implementation planning.
Show answer

Answer: D A ready planning brief connects problem, user action, evidence gaps, scope boundary, ownership, and gates.

iotclass.org

Retrieval practice

Recall checks 2–3 of 5

Blueprint Bina says: answer from memory, then check your reasoning.

Q2During a gate review, the team learns that users do not trust the sensor reading enough to act. What should the plan do next?

AContinue rollout while collecting untrusted sensor data, leaving action confidence unresolved.
BRemove the decision log and leave placement and calibration concerns unrecorded.
CDefer the trust risk with no owner or confidence-message test before expansion.
DPause rollout; test placement, calibration and confidence messaging.
Show answer

Answer: D Evidence gates exist so the team can continue, narrow, pivot, or stop.

Q3What records the shared project problem, users, outcome, evidence gaps and success test?

AStakeholder map
BProject brief
CAssumption map
DScope boundary
Show answer

Answer: B It states the problem, users, outcome, evidence gaps, and success test the team shares.

iotclass.org

Retrieval practice

Recall check 4 of 5

Blueprint Bina says: answer from memory, then check your reasoning.

Q4Complete the Python function so it returns True only when a planning brief has problem, users, outcome, scope_in, scope_out, evidence_gaps, constraints, acceptance_measure, and release_gate, plus visible assumptions, risks, and owners for risk follow-up.

Amissing = [field for field in REQUIRED_FIELDS if not record.get(field)]
Bmissing = []
Cmissing = list(record.keys())
Dmissing = [field for field in record if field not in REQUIRED_FIELDS]
Show answer

Answer: A The readiness check requires problem, users, outcome, scope_in, scope_out, evidence_gaps, constraints, acceptance_measure, and release_gate, plus visible assumptions, risks, and owner plus next-check metadata for each risk.

iotclass.org

Retrieval practice

Recall check 5 of 5

Blueprint Bina says: answer from memory, then check your reasoning.

Q5A project brief lists features but gives no release threshold. Which addition makes the decision testable?

AA longer feature wishlist without user outcome or pass criteria
BA supplier logo and launch date without an acceptance measure
CA user outcome, observable acceptance measure and explicit hold rule
DA later demo decision promised without a reviewable release gate
Show answer

Answer: C A measure and decision rule link the brief to release evidence.

iotclass.org

Print reference

Answers 1 of 2

Answer key.

  1. D · A ready planning brief connects problem, user action, evidence gaps, scope boundary, ownership, and gates.
  2. D · Evidence gates exist so the team can continue, narrow, pivot, or stop.
  3. B · It states the problem, users, outcome, evidence gaps, and success test the team shares.
  4. A · The readiness check requires problem, users, outcome, scope_in, scope_out, evidence_gaps, constraints, acceptance_measure, and release_gate, plus visible assumptions, risks, and owner plus next-check metadata for each risk.
iotclass.org

Print reference

Answers 2 of 2

Answer key.

  1. C · A measure and decision rule link the brief to release evidence.
iotclass.org