| Course | MT475 Quality Management |
|---|---|
| Unit | Unit 8 |
| Paper type | Improvement project charter |
| Length | About 840 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | BS in Business Administration |
| Updated | October 2026 |
Free sample paper for MT475 Unit 8
139 Wrong-Size Skylights in Thirty Days: An MT475 Unit 8 DMAIC Improvement Project Charter
[Student Name]
Purdue University Global
MT475: Quality Management
Unit 8 Improvement Project Charter
[Instructor Name]
[Date]
Overlook Skylight Company, its people and every figure are composite; the sources cited are real.
Project Title
Reducing wrong-size skylight remakes at the Lancaster plant.
Problem Statement
Over thirty production days in the spring, Overlook Skylight Company remade 139 skylights out of 19,200 built because they were the wrong size, a rate of 0.72 percent. At about $186 per remade unit and roughly 1,160 wrong-size remakes a year at that rate, the defect costs about $215,000 a year in materials and labor, before counting delayed shipments and dealer frustration. Wrong size was third among remake causes by count in the Unit 2 Pareto chart but first by cost.
Defect Definition
The definition sits near the top because every later number depends on it. A wrong-size skylight is a unit built to dimensions that do not match what the dealer's customer needed, as confirmed when the unit fails to fit its curb or is returned by the dealer for size before installation. The definition has two branches. Manufacturing error: the unit does not match the dimensions on the plant's cut list. Order entry error: the unit matches the cut list, but the cut list does not match what the dealer ordered or what the opening required. Each remake ticket is coded to one branch by the quality engineer, using the original order, the cut list and the measured unit.
Data source: coded remake tickets from the plant's quality system, cross-checked against dealer returns. Tague (2005) describes the charter as the document that keeps a team working on the same problem, and a shared definition is its foundation.
Baseline
From the thirty-day sample: 139 wrong-size remakes, 0.72 percent. Of the 139, the quality engineer's first coding assigns 54 to manufacturing error and 85 to order entry error, which already suggests where the project's attention should go.
Most wrong-size skylights were built exactly as ordered; the order itself was wrong.
Goal Statement
Reduce wrong-size remakes from 0.72 percent to 0.25 percent of skylights built within six months of the project's start, from about 1,160 a year to about 400, while holding on-time shipment at or above its current 94 percent. Pyzdek and Keller (2018) recommend that goals be specific, measurable and tied to the baseline, so that the project can be judged at its close.
Scope
In scope: the process from receipt of a dealer's order through order entry, engineering review and generation of the saw cut list, and the cutting and welding steps that turn the cut list into a frame. Out of scope: the dealer's measurement of the rough opening in the field. Field measurement is a likely contributor, but Overlook does not control it; the project will collect data on dealer measurement errors and pass them to the dealer training program without trying to fix them itself.
Team
Champion: the vice president of operations, who removes obstacles and approves resources. Project lead: the quality engineer, trained in DMAIC. Process owner: the customer service manager, who owns order entry and will own the improved process. Members: an order entry specialist, the saw operator from first shift, a welder from second shift and an engineering technician who reviews nonstandard orders.
Tollgates
Define: charter approved, week 2. Measure: defect coding validated by two independent coders on 60 tickets and a full baseline confirmed, week 6. Analyze: root causes tested for both branches, week 11. Improve: changes piloted and results compared with baseline, week 17. Control: control plan, updated work instructions and a p chart of wrong-size remakes handed to the process owner, week 22.
Risks and Constraints
The spring peak will reduce the team's available time; the champion has agreed to backfill the order entry specialist two days a week. Dealer cooperation in collecting field measurement data is voluntary. And coding remakes into two branches may be harder than it appears, which is why the Measure tollgate includes a test of coder agreement. Montgomery (2020) emphasizes that a measurement system must be shown to be reliable before its data are used to judge a process.
Measures the Team Will Track
The primary measure is wrong-size remakes as a percentage of skylights built, charted weekly on a p chart. Secondary measures are the share of remakes coded to each branch, the number of orders flagged by engineering review for unusual sizes and the on-time shipment rate, which must not fall as a side effect. The team will also log dealer measurement errors found during the project, even though field measurement is out of scope, so that the dealer training program receives evidence rather than anecdotes.
Expected Benefits
Meeting the goal would save about $141,000 a year in remake costs, about 760 fewer remakes at $186 each, and shorten lead times for affected orders. The champion will review the financial estimate with finance at the Control tollgate.
References
Montgomery, D. C. (2020). Introduction to statistical quality control (8th ed.). Wiley.
Pyzdek, T., & Keller, P. A. (2018). The Six Sigma handbook (5th ed.). McGraw-Hill Education.
Tague, N. R. (2005). The quality toolbox (2nd ed.). ASQ Quality Press.
What the MT475 Unit 8 assignment asks for
MT475 Unit 8 asks for a charter for an improvement project, usually following the DMAIC structure. Write a problem statement with a measured baseline, a time period and the cost of the problem. Pin the defect down tightly enough that two coders reading one ticket reach one answer, since every later number depends on it. State a goal that is specific and measurable, tied to the baseline, with a deadline and any measure that must not get worse. Set the scope, saying what is in and out and why. Name the team by role: champion, project lead, process owner and members. Set dated tollgates for each phase. List the risks with a response for each, and give expected benefits that finance can confirm at the end. About three pages in a standard charter layout is typical for this assignment.
How the MT 475 Unit 8 example is put together
Overlook's charter opens with a project title and a problem statement built from the Unit 2 log. The defect definition follows with its two branches and the remake-ticket data source, citing Tague on charters. The baseline splits the 139 remakes by branch, under a highlighted line that most wrong sizes were built exactly as ordered. The goal sets 0.25 percent and protects on-time shipment, with Pyzdek and Keller on measurable goals. Scope includes order entry through welding and leaves dealer field measurement out while still collecting its data. The team is named by role. Five tollgates run from Define at week 2 to Control at week 22, including a coder-agreement test. Risks cover the spring peak, voluntary dealer data and coding reliability, citing Montgomery. Measures and expected benefits close the charter.
MT475 Unit 8 rubric: what earns full points
Project charters are graded on precision and feasibility. Instructors credit a problem statement with a baseline, period and cost, rather than a general complaint. The defect definition is a frequent marking point, because an ambiguous definition undermines every later measure. Splitting a defect into branches that point to different causes shows analytical thinking at the charter stage. Goals that are specific, dated and paired with a protected measure are rewarded. Scope that explains exclusions shows judgment. Team roles that match the process show the student understands who must own the fix. Dated tollgates and named risks make the project manageable. A compact charter layout that fits in a few pages helps the grader find each element quickly.
MT475 Unit 8 help: mistakes that cost points
Weak Unit 8 charters describe a problem in general terms, such as improving quality, with no baseline or defect definition. Another frequent problem sets goals like significantly reduce errors, which cannot be judged at the end. Students often make the scope too large, trying to fix everything from the dealer to the customer. Team sections sometimes list names without roles. Tollgates are commonly missing or undated. Measures that must not get worse are rarely included, which invites solutions that create new problems. Before submitting, give your defect definition to a classmate with three sample cases and see whether they code them as you would. If not, tighten the definition. Then check that your goal names a number, a deadline and a measure you will protect.
Get an MT475 Unit 8 example written to your instructions
Bring the defect or problem your Unit 8 prompt names, any baseline data or case, and the charter template and rubric. A composite charter is returned with an operational defect definition, a baseline and dated goal, a bounded scope, distinct roles, a balancing measure and DMAIC tollgates. Your first custom sample is free, with delivery in 24-48h. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More MT475 papers and BS in Business Administration samples
- MT475 Unit 1: Quality Definitions Board Post
- MT475 Unit 2: Seven Quality Tools Exercise
- MT475 Unit 3: Cost of Quality Report
- MT475 Unit 4: P Chart Control Chart Analysis
- MT475 Unit 5: Process Capability Study
- MT475 Unit 6: Product Recall Seminar Reflection
- MT475 Unit 7: Supplier Quality Scorecard Review
- MT475 Unit 9: Quality System Gap Analysis
- MT475 Unit 10: Quality Improvement Proposal
- MT460 Unit 8: Strategy Implementation Plan
- MT459 Unit 8: Rescue Subculture Litter Study
- MT455 Unit 8: Territory Quota Setting Exercise
- MT453 Unit 8: Sanitation Value Proposition Memo
MT475 Unit 8 questions, answered
What does DMAIC stand for?
Define, Measure, Analyze, Improve and Control, the five phases of a Six Sigma improvement project. Define sets the problem and scope, Measure establishes a reliable baseline, Analyze identifies root causes with data, Improve tests and implements solutions, and Control keeps the gains. A charter is a Define phase document, so it describes the project before any cause is known.
What makes a defect definition measurable?
A rule precise enough that two inspectors judging one window would reach the same verdict: a tolerance, a pass-or-fail test, or a coded category with written criteria. It should also name the data source, such as inspection records or remake tickets. Definitions like poor quality windows or customer complaints are too loose to produce a stable baseline.
Should the charter include a solution?
No. The charter describes the problem, its cost, the goal and the boundaries, and leaves causes and solutions to later phases. Naming a solution early commits the team before the data has spoken, which is what DMAIC is designed to prevent. Mentioning hypotheses to test is acceptable if they are clearly labeled as hypotheses rather than conclusions.
Where can I find a free MT475 Unit 8 sample paper?
The whole MT475 Unit 8 charter is on this page, setting a DMAIC project to cut wrong-size skylights from 0.72 to 0.25 percent.
Why does the MT475 Unit 8 sample split the defect into two branches?
Most wrong-size units were built exactly to a cut list that did not match the order, so manufacturing errors and order entry errors point to different causes.