Nov 16, 2026 | 576 words | 6 min read
16. TP: Milestone 1: Scope the Problem#
At a Glance
What you will do: Analyze the client’s brief individually. Then work as a team to draft the first sections of your Technical Report: stakeholders, success criteria, roles, and background research.
What you will submit: Two individual Gradescope activities and your Technical Report checkpoint (TP1).
Fig. 16.1 The Martian surface at Murray Buttes on lower Mount Sharp, photographed by the Mast Camera on NASA’s Curiosity rover. Image source: NASA/JPL-Caltech/MSSS.#
In this milestone, teams define the problem before they design a solution. Engineers who start building before they understand the problem often deliver products that do not meet the client’s needs. GHU-1’s contractor made that mistake. Mission Control has hired your team to define the problem first.
Read the Mission Brief carefully before starting, and open
your Design Project Technical Report; you begin
filling it in this milestone. Every question here can be answered from the brief, your
close reading of it, and your own reasoning and research.
Read the AI Usage Policy before you use any AI tool on project work. It applies to every milestone.
16.1. Tasks#
Task |
Who |
Deliverable |
|---|---|---|
Individual |
Gradescope assignment (extraction worksheet and synthesis) |
|
Individual |
Gradescope assignment |
|
Technical Report checkpoint (TP1), described below |
Team |
Report sections II and III |
16.2. Your Report This Milestone (TP1)#
Draft the first sections of your
Design Project Technical Report:
II. Team Member Roles and III. Problem Scoping.
Leave Table 2, Actuator owners, in section II blank for TP1. Your team completes it in Milestone 2 (TP2), after each member operates the four actuators in Operating the Greenhouse.
Remember to utilize your team’s submissions for the Client Needs Analysis and Problem Formulation to complete these sections in your report.
Save your report as a PDF named TP1_design_project_report_team_#.pdf. Submit it as a group to 16.2 TP1: Design Project Report - Milestone 1 (Team) in Gradescope, with these sections drafted. Submit before the deadline listed on the
Course Schedule.
Learning Objectives
- PS01:
Stakeholder-Based Problem Definition - Explain the problem based on synthesis of client, user, and stakeholder needs.
- PS02:
Contextual Importance of the Problem - Justify the importance of the problem using global, societal, economic, or environmental context.
- PS03:
Constraints and Criteria - Define key criteria and constraints that address client and user needs.
- PS04:
Competing or Conflicting Needs - Identify competing or conflicting needs that influence the problem definition.
- IL01:
Asking Questions to Guide Research - Identify gaps in knowledge and pose clear, specific questions that guide research and information gathering.
- IL02:
Gathering Reliable Information - Locate and select relevant, credible sources appropriate to the engineering context.
- IL04:
In-Text Citations - Include appropriate in-text citations to indicate the source of information, data, or ideas.
- IL05:
Reference List and Source Documentation - Provide a complete and properly formatted reference list for all external sources used.
- TM01:
Acknowledge Team Strengths - Recognize and respect the unique knowledge, skills, and experiences that each teammate brings. Use this awareness to distribute responsibilities or seek support when needed.
- TM04:
Meet Team Commitments - Complete tasks on time and at an appropriate standard. Communicate clearly and early if support is needed or deadlines cannot be met. Follow through on team expectations.
- PC01:
Written Communication Standards - Use professional tone, clear sentence structure, and correct spelling and grammar in all written work.
- PC03:
Captioning Visuals - Include professional captions for all figures, tables, and plots that describe what is shown and why it is relevant.
- PC05:
Meeting Assignment Expectations - Fully complete all parts of each assignment according to provided instructions.
- TM02:
Document Contributions - Provide clear evidence of individual contributions to the team’s work, including technical, written, or supportive tasks.
- SQ01:
Technical Accuracy - Use accurate scientific, mathematical, and technical concepts, units, and data.
- IL03:
Supporting Claims with Evidence - Use data, examples, or published sources appropriately to support claims, assumptions, or recommendations.
- EB02:
Assumptions Under Uncertainty - Identify assumptions made when information is limited or unavailable.