Computer Science Honors
Course Progress
0/0
Sprint 1 intro
W0 Team Formation & Agile Initialization 0/1
W1 Instructional Problem & Requirements Analysis 0/1
W2 Literature Review, Design Specs & Peer Review 0/2
W3 Mentor Engagement & Feasibility Review 0/1
W4 Retrospective and Assessment 0/2
Sprint 2 intro
W5 Element D: Design Concept Generation, Analysis & Selection 0/2
W6 Element E: Application of STEM Principles & Practices 0/2
W7 Element F: Consideration of Design Viability 0/1
W8 Element G: Construction of a Testable Prototype 0/1
Sprint 3 intro
W9 Elements H+I: Prototype Testing, Data Collection & Analysis 0/1
W10 Element J: Documentation of External Evaluation 0/1
W11 Element K: Reflection on the Design Project 0/1
W12 Elements L+M: Recommendations & N@tM Portfolio Defense 0/2
Sprint 4 intro
W13 Element A (Iteration 2): Redefine & Rejustify the Problem 0/1
W14 Element B (Iteration 2): Analyze Your Own Prior Attempt 0/1
W15 Element C (Iteration 2): Justify Revised Design Requirements 0/1
W16 Sprint 4 Retrospective & Team Realignment 0/1
Sprint 5 intro
W17 Element D (Iteration 2): Beta Design Concepts 0/1
W18 Element E (Iteration 2): Production-Fidelity STEM Application 0/1
W19 Element F (Iteration 2): Viability at Scale 0/1
W20 Element G (Iteration 2): Construction of the Beta Prototype 0/1
Sprint 6 intro
W21 Elements H+I (Iteration 2): Edge-Case & Comparative Testing 0/1
W22 Element J (Iteration 2): External Evaluation (UAT) 0/1
W23 Element K (Iteration 2): Final Reflection 0/1
W24 Elements L+M (Iteration 2): Final Recommendations & Capstone Defense 0/2
Element F (Iteration 2): Viability at Scale
1 min read
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.