✅ Assignments

What you submit each week, where, and how it's graded. Submission mechanics live here — nowhere else on the site (SITE.md rule R2).

🙋 Ask the Teaching Team → Fix a grade or submission problem — it goes straight to a real person. Access opens with your course login — if it asks you to sign in, that is expected.
Where to submit Homework Weekly learning checks Activities Midterm Hackathon Project deliverables Rubric Self-grade checklist

Where to submit

Everything is submitted on Canvas. Homework, learning-check exports, activities, Live Labs, and project deliverables all go through the course Canvas site — that is also where every deadline lives. This site tells you what the work is; Canvas is where it lands and when it is due.

Honor code. All homework and project submissions are made under the course honor code: I have neither given nor received any unauthorized aid on this assignment. Put that line at the top of what you hand in.

Open Canvas Assignments →

Homework

Each homework lives on its own site, and a released homework is public: no login, no sign-in, no Posit Connect account. The button below opens it as soon as that homework is released; until then the button is gray and there is no link yet. If a released link ever asks you to sign in or says you're not authorized, that is a mistake on our end, not yours: tell the instructor.

R or Python — your choice. Every homework in this course can be done in R or Python. Where a question names an R function or package, use the Python equivalent if you are working in Python; the textbook shows every method both ways.

No R or Python on your computer yet? The Code Playground runs both in your browser, with a starter for each week's topic.

HW 1

HW 2

HW 3

HW 4

HW 5

HW 6

HW 7

Why this one is called the take-home final. Homework 7 is the last homework of the course, and it is a take-home deep dive on factorial experiments and response-surface methodology: the midterm tests the whole experiments block, and Homework 7 takes its last two topics further. In every other respect it is an ordinary homework: same points, same homework-site format, same submission box, same rubric standard as Homework 1 through 6. It is not a second sit-down exam — no note sheet, no time limit, no exam conditions — but because it is the final, it is the one homework the drop-lowest rule does not cover.

Due dates for every homework are on the course calendar. Each homework below links to its own calendar row.

Weekly learning checks

Every chapter's Learning Checks follow the upgraded MCQ + short-justification format: pick the multiple-choice answer, then write one sentence justifying it. Format source of truth: specs/LEARNING-CHECKS.md — machine-gradeable MCQ, data-driven correct answers wherever possible, one-sentence free-text justification per check.

Each chapter page that has Learning Checks has a 📋 Export my learning-check answers button after its last check — it builds a single Markdown blob (readable for Canvas, machine-parseable for grading) with every check, plus any chosen option and justification. Export that blob and submit it.

Activities

Activities are the short things you do in class — code-it exercises, draw-it exercises, discussions, exercises, pop quizzes, and Live Labs. Every one of them is submitted on Canvas and is worth 1 point, graded on completion: turn in a genuine attempt and you get the point. Pop quizzes are the exception — those are graded on accuracy.

Every activity has its own page on this site, with the instructions written out so you can find them again after class. Browse them all on the Activities page.

A Live Lab is one kind of activity: a ~30-minute in-class exercise run against a live streaming process — watch the data arrive, detect the shift, diagnose the cause, apply a treatment, verify the fix.

  • SPC Live Lab — statistical process control on a live stream: read the X̄ and S charts, name the assignable cause, treat it, and export your worksheet.

Live Labs run on the course's own server rather than on this site, so each one opens with your Cornell login and you must be enrolled in the course to get in. There is no access code and no password to type. Follow the lab link above and sign in; if you are on the roster and it still turns you away, tell the instructor.

In-person students submit an activity during or right after the class session it belongs to; distance learners get the usual distance-learning window. Your deadline is always the one shown on the Canvas assignment.

Midterm Exam

See the calendar

A take-home exam covering the experiments block (designing experiments through response surfaces). It is a Canvas quiz. The exam and the Hackathon are both required — separate assignments, not a choice.

The quiz opens on the scheduled start date and stays open seven days. Take it any time in that window. Once you begin, you have a maximum of 3 hours. Submit once: your answers are final, and there are no multiple submissions.

This is take-home. A room may be available, but the exam is not proctored. The TA and the instructor can help during Friday class and usual office hours.

Closed book. You may use only (1) a calculator and (2) a formula sheet: one 8.5×11 sheet of notes, any fonts, double-sided OK. Helper materials (stat tables plus some formulas) come with the exam.

You will sign the honor code before you start.

A practice exam is posted about a week prior — see the practice midterm on the calendar. A supplemental review session is DATE/TIME TBA.

No extensions during prelim week: the 1-week window plus 3 hours is the accommodation. If you will be absent for a religious observance, reach out by September 10 to schedule a makeup.

Work on your own — no cooperation on the exam. Questions go to the TA. You’ve got this!

See the Syllabus for its weight and the deadline policy. Your exact hand-out and due moments are on the Canvas assignment.

Six Sigma Hackathon

See the calendar

The hackathon window is on Canvas: the hackathon assignment shows when it opens and when it closes. Content is still in development. You will be asked to create some kind of working dashboard or software with vibecoding. Details forthcoming.

This is a required assignment, separate from the midterm. You do both — there is no midterm-or-hackathon choice. Where it sits in the term is on the course calendar.

You don’t have to be a veteran coder. This hackathon was made for this class.

Distance learners, and anyone who absolutely cannot attend, complete the DL Challenge: a one-week hackathon-by-homework. Same general challenge, a different question, and a different time frame.

Last year’s event is on GitHub: previous year’s Six Sigma Hackathon (v2025 branch).

Signup, the flyer, the live event site, and the debrief survey: COMING SOON!

See the Syllabus for its weight in your grade.

A short one-on-one conversation with a member of the teaching team — you book a slot with one of the examiners — about the main ideas from the first half of the course. There is nothing to upload: the exam happens live, and the grade is entered by hand afterwards.

When. Oral exams run on the dates shown on the course calendar. Book your 5-minute slot with an examiner.

What we talk about. The course, not your project. We pick a couple of ideas from the material covered up to that point — standard error and variation, control charts, process capability, lifetimes and system reliability — and ask you to explain them in your own words and say when you would reach for them.

What it is worth. 10% of your final grade on the 4-credit track, and about 14.3% on the 3-credit track. It is graded on whether you can explain the main ideas and reason out loud with the course's tools — not on recalling formulas.

How to prepare. Skim the chapter and your learning checks from the first half of the course, and practice out loud the main ideas. Work through the Practice questions out loud with a teammate. Bring nothing — no notes are needed and none are expected. If you want a warm-up, the in-class activities are close to the kind of question we ask.

Practice questions (27)

Spread, standard error and variation

  1. P1 A coffee roaster weighs single bags, and also reports the average weight of each pallet of 10 bags. Which of those numbers bounces around less from pallet to pallet, and what do we call the amount the pallet average bounces? How could you estimate that bounce in R by simulation, with no formula at all?
    Follow-up: If you wanted to cut that bounce in half, how many bags per pallet would you need, and why?
  2. P2 Two labs report their results: one measures battery life in hours, the other measures cable length in metres. Your manager asks two things: which process is more variable, and how much to trust each lab's reported average. Which statistic answers each question, how is each one computed, and why can one statistic not answer both?
    Follow-up: Lab 1 doubles its sample size. Which of your two numbers changes, and which stays about the same?
  3. P3 A call centre's average answer time wobbles a little every day, and on one Tuesday it tripled when the phone system crashed. Which of those is common-cause variation and which is special-cause? Who is responsible for reducing each kind, and how would a control chart help you tell them apart?
    Follow-up: A supervisor wants to hold a team meeting every time the daily average goes up a bit. What would you advise, and why?
  4. P4 A lab weighs 5 tablets from every hour of a shift. Describe two ways to summarise the spread of those weights: one that looks only at variation inside each hour, and one that uses every tablet at once. When would these two numbers disagree, and which one belongs in the control limits?
    Follow-up: A customer cares about every tablet they receive over a month. Would you report Cpk or Ppk to them, and why?

Stability and capability

  1. P5 Explain to a new engineer the difference between a stable process and a capable process. What tool tells you about each, and whose 'voice' sets each set of limits? Describe a real process that is stable but not capable, and one that is capable but not stable.
    Follow-up: Why should you check stability before you report a capability index?
  2. P6 A resistor maker reports Cp = 1.8 and Cpk = 0.7 for resistance, and Pp and Ppk are close to those. Sketch what the histogram must look like against the spec limits. Is the process capable, and what single change would help most?
    Follow-up: What would have to happen for Cpk to equal Cp?
  3. P7 A soda filler reports Cp = Cpk = 0.9 and Pp = Ppk = 0.6, and the process is well centred. What do the numbers tell you, and why are the P indices lower than the C indices?
    Follow-up: Which would you work on first: tightening each short run, or stopping the drift between runs? Why?
  4. P8 Write Cpk as a formula and explain each piece in plain words: which parts come from the customer and which come from the process? Why does it look at both spec limits and then keep only one?
    Follow-up: Sketch a process where Cp is high but Cpk is low, and one where the two are equal.

Designing a study and choosing a chart

  1. P9 Diners at a campus dining hall say the lunch line has gotten slower this month. How would you check whether the line has really changed? What would you record, how would you group the readings, and which charts would you make?
    Follow-up: The dining hall promises 'served within 10 minutes'. Where does that number belong in your analysis, and where does it not?
  2. P10 Baristas say a coffee shop's espresso shots 'taste weak lately'; the machine is supposed to pull 18 g of coffee into a 36 g shot. How would you find out whether the machine has drifted? What would you weigh, how often, grouped how, and plotted on what?
    Follow-up: The recipe says 36 g plus or minus 2 g. At what point in your analysis would you bring that in?
  3. P11 A bakery checks 200 cookies every day and throws out any that are broken. You have a month of daily reject counts. Which control chart fits these data, where do its limits come from, and what would count as a signal?
    Follow-up: A colleague wants the mean and standard deviation of each cookie's 'broken or not'. Why does an averages chart not fit here?
  4. P12 A city inspects some of its streetlights every month and counts every fault it finds (dead bulbs, cracked covers, bad wiring). Some months it inspects 50 lights, some months 300. Which chart would you use, and how do its limits behave from month to month?
    Follow-up: A council member points to the month with the most faults. Why might that not be the worst month?
  5. P13 From memory, write down the upper and lower control limits for an averages chart, then explain what each symbol stands for. Why do we multiply by 3, and why divide by the square root of the subgroup size?
    Follow-up: If you estimated sigma from all the data pooled together instead of from within subgroups, would your limits get wider or narrower, and what would the chart then miss?

Reading control charts and process overviews

  1. P14 Sketch an averages chart with a centre line and control limits where every point is inside the limits, but the last eight points all sit above the centre line. Is that process in control? Explain why that pattern is unlikely if only common-cause noise is at work.
    Follow-up: What would you go and look for at the subgroup where that run began?
  2. P15 Sketch three averages charts: one with a single point below the lower limit, one with seven points in a row steadily climbing, and one that just wiggles inside the limits. Which would you flag, and what would you tell the process owner about each?
    Follow-up: Why is a lot of wiggling inside the limits not, on its own, a reason to act?
  3. P16 Picture an averages chart where the points zigzag up, down, up, down for fourteen subgroups in a row, all inside the limits. Another chart has two of three points in a row sitting close to the upper limit. Are these signals? Why would a pure-noise process rarely do either?
    Follow-up: What kinds of real causes produce a strict zigzag?
  4. P17 Picture a process overview of the length of cut lumber boards (target 2.40 m): boxplots of 20 subgroups over time, plus an overall histogram. The boxes stay centred on the target but get taller and taller from left to right. What would you say about centre, shape and change over time, and which chart would you draw next to test it?
    Follow-up: What would the overall histogram, on its own, have hidden from you?
  5. P18 Picture a process overview of delivery times for a food-delivery app, in minutes. The boxes are steady over time, but each has a long upper whisker, and the histogram has a long right tail. Describe the centre and the shape, and say what you would look into next.
    Follow-up: Would you report the mean or the median delivery time to customers, and why?
  6. P19 Picture a process overview of paint thickness on car doors (target 120 microns). The first ten subgroups sit around 120 and the last ten all sit a bit higher. What does the overall histogram probably look like, and what would you do about it?
    Follow-up: Why can a histogram of all the data make a process look more variable than it is from moment to moment?

Lifetimes and failure functions

  1. P20 A component has a constant failure rate lambda. Write the probability that it has failed by time t, and the probability that it is still working at time t. Sketch both curves on one set of axes and say what the mean time to failure is.
    Follow-up: Why would this model be a poor fit for a car tyre that wears out?
  2. P21 Your supplier gives you R(t), the reliability function of a fan motor. How would you get the chance that it has failed by time t, and the density of failures at time t? Sketch all three and say what each one means in plain words.
    Follow-up: Can f(t) be bigger than 1? What does the area under it mean?
  3. P22 Explain the hazard function to someone who only knows f(t) and R(t). How is it computed, and why do we call it a conditional rate?
    Follow-up: Sketch the bathtub curve and say which part of a light bulb's life each section describes.
  4. P23 Start from R(t) = e^(-lambda t) for an exponential lifetime. Derive F(t), f(t) and the hazard h(t). What do you notice about h(t), and what does that mean for a part that has already run for a year?
    Follow-up: Name one kind of product whose failures fit this model and one that does not.

System reliability

  1. P24 Read this case. A food truck's espresso service needs power from either its generator or a shore-power plug, then one grinder, then either of two espresso machines. Describe the series and parallel parts, and explain how you would work out the reliability of 'coffee gets served' without doing any arithmetic.
    Follow-up: Both espresso machines draw water from the same tank. What does that do to your independence assumption?
  2. P25 Read this case. An airliner's landing gear can be lowered by the main hydraulic system or by a backup electric motor, or as a last resort by gravity free-fall; the gear then has to lock. Describe the structure, and explain how you would compute the reliability of 'the gear is down and locked', without numbers.
    Follow-up: Where is the weak point, and where would one more backup help least?
  3. P26 Read this case. A website runs on two load-balanced servers; each server needs its own disk, and both sit behind one network switch and one internet connection. Describe the series, parallel and nested blocks, and explain how you would compute the reliability of 'the website is up'.
    Follow-up: Both servers sit in one rack on one power strip. How does that change your calculation?
  4. P27 Read this case. A home aquarium keeps its fish alive overnight if the water is filtered by either of two filters, heated by one heater, and aerated by an air pump that runs off the wall or a battery backup. Describe the structure, and explain how you would calculate the reliability of 'the fish are fine overnight'.
    Follow-up: Which single component would you duplicate first, and why?

How to practise them with a teammate, plus a tip per topic: the full Practice questions page.

Project deliverables

The semester project is submitted as a ladder of ten rungs — each rung is its own Canvas assignment, each is graded on its own, and each one feeds the next. Ten rungs instead of thirteen: three pairs that were separate submissions in 2025 are now single combined submissions. In order:

  1. Team & topic — form a team of 3–5 and commit to one process you can actually observe or get data about.
  2. Your dataset — the actual data, plus a codebook saying what every column means, its units, and where each number came from.
  3. Project charter — one page: the problem, the scope, the metric you will move, and the target.
  4. VOC tree & SIPOC diagram (combined for 2026) — turn what the customer says into a measurable requirement, and bound the process.
  5. Process map & literature review (combined for 2026) — the real sequence of steps, decisions and handoffs, plus what is already known about this class of failure.
  6. Research design — what you measure, how often, under what conditions, and what result would change your mind about the cause.
  7. Preliminary results & financial impacts (combined for 2026) — the charts, the fitted models and the intervals, reported with what the improvement is worth in money.
  8. Rough draft — the whole report assembled end to end while there is still time to fix it.
  9. Final report — define, measure, analyze, improve, control, ending in a recommendation somebody could actually act on. This is the deliverable the black-belt certification is judged against.
  10. Poster presentation — the report compressed to what a stranger can absorb standing up, presented live to the class.

Every rung has its own full spec — what to hand in and what it is graded on — on the Projects page, which also carries the method gallery and the project-idea network to help you choose a topic.

Rubric

A short self-check you can copy into your own notes before you submit. The graded rubric for each assignment is attached to its Canvas assignment.

Learning checks: MCQ correct? (Y/N)  ·  Justification demonstrates understanding? (Y/N)
Lab: submitted on time? (Y/N)  ·  Diagnosis matches the live data? (Y/N)
Project: milestone met? (Y/N)  ·  Notes: ____________________

Self-grade checklist

Run through this before you submit anything.