Element F (Iteration 2): Viability at Scale

1 min read • Assignment

Week 19: Viability at Scale

PLTW Element F, Iteration 2 — Consideration of Design Viability, at production scale.

Cost at Scale

Revise your Sprint 2 BOM to reflect at-scale costs: what does this cost per unit or per user at realistic deployment volume, not just for your one prototype?
For software, this means hosting/API costs at realistic usage, not free-tier assumptions.

Regulatory & Compliance Considerations

Identify any regulatory, privacy, accessibility, or safety standards relevant to your domain (e.g. data privacy for student data, safety standards for physical devices, accessibility for public-facing tools).
Document how the Beta design accounts for each one — or explicitly note it as an unresolved risk.

Revised Build-and-Test Timeline

Lock a timeline for the Sprint 5-6 build and test that accounts for the added complexity of the Beta over the Alpha.

Core Deliverables

At-scale cost analysis.
Regulatory/compliance review.
Revised Sprint 5-6 build-and-test timeline.

Submit Assignment

Need to update a submission later? Open the submissions dashboard.