Th by month)Filter by: initial post Something went wrong Try to reload widget. If the problem persists, please contact us at semrush-email@semrush.com dmaic report example

Six Sigma Report Hammett

Six Sigma DMAIC Project Report Template

Comments

· The following template provides guidelines for preparing a Six Sigma written certification project report. Subheadings and length of each section will obviously vary based on your findings and writing style. For a complete sample report using the template, see “Sample Project Report”.

· The information in your report should follow the Six-Sigma Problem Solving Methodology DMAIC. This includes a description of the project, key points in the problem-solving process, and detailed support for your conclusions and any recommendations. Reports should be approximately 10-12 double-spaced pages (excluding appendices), including tables and figures.

· Some general guidelines for grammar and format are provided for your reference at the end.

· Some information contained in this template is repetitive across sections. However, since different audiences will read your report to various degrees of depth, we believe that it is essential to repeat certain information. Ultimately, you should produce a high quality, professionally-presented report that has sufficient detail to help other Six Sigma practitioners utilize and build upon your project findings.

Title of Report

Submitted to:

Name, Title

Department/Organization

Address (optional)

Prepared by:

Name, Title

Department/Organization

Address (optional)

Date Submitted

Note: Do not put a page number on your title page. Begin numbering the pages with the Executive Summary.

Executive Summary

The Executive Summary presents the major information contained in the report. Its readers are typically managers who need a broad understanding of the project and how it fits into a coherent whole. These readers do not need or want a detailed understanding of the various steps taken to complete your project. Therefore, the Executive Summary allows readers to learn the gist of the report without reading the entire document, to determine whether the report is relevant to their needs, or to get an overview before focusing on the details. We consider writing a concise (typically one-page) and comprehensive executive summary a critical element of a Six Sigma project report. The Executive Summary should NOT include terms, abbreviations, or symbols unfamiliar to the reader. Readers should understand the content of the Executive Summary without reading the rest of the report.

The Executive Summary should include a problem statement, summary of approach used, and major project findings and recommendations.

· Problem Statement / Description

· Concisely describe the problem (few sentences).

· Identify the time period of the problem

· Quantify the degree of the problem and its impact on the business (if possible).

Example: During the past year, the average # of incoming calls with complaints per card-year has increased by 20%. These additional calls have resulted in additional staffing and facility costs of ~$100K per year . This project identifies several reasons for this increase in calls and provides solutions to reduce them.

· Summary of Problem-Solving Approach (methods used to solve problem)

· Example: We formed a cross-functional problem solving team from the following departments. This team used the Six Sigma DMAIC problem solving process to identify opportunities for improvement. First, we conducted a qualitative process analysis to identify potential causes for the number of complaint calls. Next, we set up a data collection plan at two call centers. Here, we conducted an observational study over a two-month period of various key input variables versus the number of complaint calls to determine the major causes of our increase in calls. From this study, we were able to identify several recommendations for our call centers.

· Major project results or findings and recommendations -- should include KEY information.

Example: A major finding of our project is that the majority of our increases in complaint calls (about 70%) are the result of either confusion with using our new ATM screen menus or delays in providing customers new ATM cards in the case of lost or stolen cards. Our analysis resulted in several recommendations to our ATM format menus. In addition, this project has lead to the implementation of a new internal procedure to send customers new ATM cards to replace lost or stolen cards. In an initial verification study of these new procedures, we have been able to significantly reduce complaint calls resulting in a projected savings of $50,000 for reduction in call center staff resources.

1.0 Improvement Opportunity: Define Phase

Discuss the problem you examined. Explain how you identified your specific Six Sigma project. You might possibly integrate visuals and data summaries using tools such as a Pareto chart or a summary report of current performance for either a manufacturing or transactional process.

Some topics that should be included in this section are:

1.1 Discussion of the process being examined and problem addressed

· Include a written description of the process and the potential performance issues. This is a good place for a process map, flow chart, or perhaps a SIPOC diagram.

· See problem statement discussed in executive summary for suggestions on writing an effective problem statement. Note: this section likely will repeat information from executive summary.

1.2 Identification of key measures used to evaluate the success of your project

· Examples: DPM, DPMO, costs, quality yield, error rates, processing or order-filling time or % conformance, machine cycle time, # complaints, etc.

1.3 Discussion of project scope

· Note: include discussion of scope if you chose to limit your project to a particular part of a larger problem statement or due to timing constraints or span of influence.

2.0 Current State of the Process: Measure Phase

2.1 Current Performance Level

Summarize current performance levels. Note: you typically need to describe the data set used to summarize performance by discussing how the data were collected, what was the sample size, the period of data collection, whether the data were measured, and if there were any measurement system issues). Integrate visuals such as tables and figures to summarize performance. Some metrics and analysis tools that might be used here:

· Quantify Current State of Key Y Variable(s) [i.e., Project Metrics], summarize performance using one or more of the following:

· quality yields (% conformance or % defective)

· process capability summary (either as DPM/DPMO measure, or using process capability indices),

· descriptive statistics summary tables, (note: if project examines a Y variable that involves continuous data (e.g., length, time, etc.) to specification limits, you may want to discuss if your problem appears related to a mean off target and/or a variation issue.)

· Note: Do not present long, bulky data set tables in the main report, place them in appendices to the report.)

· Distribution/Data Patterns of Key Outputs (identify distribution of performance and/or discuss any data patterns in the current state data). Some tools to use here are:

· histograms,

· Pareto charts,

· Statistical process control charts and/or run (time trend) charts.

· If possible, identify if problem is a chronic and/or a sporadic problem.

· Measurement System Analysis (Optional)

· Discuss the validity of your measurement data either qualitatively (in words) or quantitatively using tools such as a Gage Repeatability and Reproducibility Study, Repeated Measurement Analysis Results, and/or Gage Accuracy Study. If appropriate, discuss the strengths and limitations of your data collection method.

2.2 Identification of Key Variables.

· Identify Key Product/Process Output Variables (KPOV’s) examined and/or list potential Key Product Input Variables (KPIV’s).

· Sample Tools that might be used here include P-Diagram or a Cause-Effect Diagram. Or, simply include a summary paragraph or list of potential variables.

2.3 Identification of Target Performance Levels or Project Goals.

· Target Performance Levels (Required) - identify the desired performance levels or improvement amounts of your performance metric (e.g., Reduce DPM level from 35,000 to 1000 DPM, or reduce reject rate from 10% to “<1%”, or reduce time-to-delivery by 50%, or reduce process costs by XX%).

Examples of Current and Target Performance Level Assessments:

· Our current process requires 15 days to complete a special order and we wish to reduce this time to less than 7 days. Or,

· We currently are operating at 20,000 DPMs and we wish to reduce this level to less than 1000 DPMs.

3.0 Analysis and Findings: The Analyze Phase

Analyze gaps between current performance and target performance levels, explaining possible sources of variation. Include subtopics and subheadings that reflect your case. Include visuals, supporting analysis from various methods discussed in the course including cause-and-effect diagrams, stratification analysis, scatter plot analysis, correlation analysis, etc.

In this section, you should discuss the relationships between your KPIVs and KPOVs. For example, you should discuss those variables that have a direct cause-and-effect relationship or those input variable settings (or range of settings) in which your KPOV(s) are robust.

For most reports, your analysis will include both a qualitative and quantitative assessment. For a qualitative assessment, you might include a cause-and-effect diagram summarizing results, a process map, or simply a discussion of the results from brainstorming sessions or interviews with affected employees.

For your quantitative analysis, you should provide some data analysis that demonstrates a more systematic and comprehensive assessment of your key output variable and/or the main causes for lack of performance. Please recognize that the purpose of the project is to solve a problem and not necessarily to use a specific quality analysis tool or method. Thus, try to use the tool/method that is appropriate to solving the problem even if the tool used is fairly simple analytically.

In many cases, reports also should include analysis and results for insignificant or unimportant variables. For many projects, identifying variables or (variable settings) that do not affect your key Y variables provide additional opportunities for cost savings. For example, a project may discover that a certain part feature or process step may actually allow for a wider tolerance and still meet next-process customer requirements. Here, widening the tolerance for might yield an overall cost saving.

Information that must be included in this section include:

· You must demonstrate your understanding of course concepts and tools by showing evidence of the use of at least one data analysis tool/ method discussed in this course. You should support this requirement by including at least one table, graph, or diagram within the main body of the text. (e.g., you might include a Pareto chart, stratification analysis table, cause-and-effect diagram, scatter plot, correlation analysis, process control charts, experimental results, value stream map, value-add analysis, measurement systems analysis if your report involves improving a measurement system (Note: these tables and figures must be integrated into the main body of your report; additional background material may be included in the appendix).

· Note: We encourage the use of additional data analysis tools and may request re-submittal of a project to include additional analysis if appropriate.

Note: Some of the analysis tools used in the Analyze Phase may also apply in the Improve Phase. Feel free to include Six Sigma problem solving and analysis tools in either the Analyze Phase or the Improve Phase as appropriate to present your argument.

4.0 Recommendations: The Improve Phase

Identify alternative ways to improve performance. Try to evaluate how well alternatives will be able to meet target performance goals. Specify criteria for choosing a course of action. Present conclusions regarding alternatives and identify recommended solution. Consider presenting the material in the following subtopics with appropriate second-level headings.

· Alternative Solutions Considered

· Recommended Solution

Historically, improvement recommendations fall into a few general categories. These include (but are not limited to) recommendations to:

· train operators to more effectively perform tasks (e.g., to address customer concerns, or adopt best work practices)

· standardize procedures or processes

· make adjustments to settings of key process input variables Note: may require adding processes to collect data.

· redesign process flow (e.g., reorganize the flow of parts/ documents/information through your system)

· install new process monitoring or automatic defect detection system (e.g., install monitoring systems for either X’s or Y’s)

5.0 Monitoring and Control: The Control Phase

Identify the method of control to prevent reoccurrence of problems. Control phase recommendations might include recommendations for improved:

· Management Control Systems

· Design Control / Change Management Control Procedures

· Training and Standard Operating Procedures

· Supplier Control/ Process Setup Control Processes

· Source Inspection (in-process controls such as poke-yoke devices)

· End of Process Quality Inspection and Process Monitoring/Tracking Systems

· Quality Audits

· Statistical Process Control with control charts

· 100% Inspection (usually not recommended as long term strategy)

Comment: We realize that it might not be possible to include data that supports that an actual improvement was made to the process because of the project time constraints. If this is the case, please at least discuss the potential benefits of implementing your recommendations.

6.0 Conclusion

Briefly restate the problem addressed, the process followed to reach a solution, and the chosen solution. List the potential benefits to the chosen solution. Note: if your results or recommendations are incomplete or sensitive to your company, please try to discuss potential benefits in relative terms. (e.g., a 20% reduction in error rates or a 10% cost savings). If appropriate, explain any further action to be taken, including the responsible team members and schedule.

Appendices

Use appendices to present information that is too bulky to be presented in the body of the report or that will interest only a few readers. For example, large diagrams or charts, computations, software package graphics, test data, and texts of supporting documents should appear in appendices. Appendices have the following characteristics:

· Titled "Appendix," not "Figure" or "Table."

· Usually lettered rather than numbered.

· Referred to at appropriate points in the body of the report so they are accessible to the reader who wants to consult them.

Only use an appendix when the data is not relevant to the report but might be of interest to some other readers. We expect most if not all of your tables and graphs to be in the main body of the report.

General Guidelines for Writing Reports

The following list presents reminders to help you write reports that are easy to read and understand. You do not have to follow every one of these recommendations. How you present your written argument depends on your situation. These tips are offered as basic guidelines. For more information about techniques for writing clearly, consult a writing handbook or a writing website such as: http://www.plainlanguage.gov/

· Know your audience and purpose when writing.

· Choose and organize your content around your purpose and audience.

· Use frequent, informative headings and subheadings. Headings and subheadings help readers preview and review the major sections of information.

· Divide material into short sections.

· Introduce the sequence of sections that follow to let readers know what's coming in the report.

· Limit each paragraph to one topic.

· Vary structure and length of sentences. However, prefer short, direct sentences.

· Use "you" to speak to the reader. Use "I" or "we" to refer to events in which you were involved. Note: Using "I" or "we" is now widely accepted in technical writing.

· Be concise. Avoid unnecessary words.

· Select appropriate diction. Prefer clear, simple language. Avoid inflated, obscuring words.

· Prefer active voice. Use the passive voice only when the identity of the agent is irrelevant.

· Be consistent in tenses. Prefer present tense.

· Prefer active verbs to abstract nouns.

· Use terms consistently to refer to the same object.

· Use lists.

· Use parallel grammatical structure for ideas or facts of equivalent importance (often presented in lists). For example: Instead of Accidents can be either personal injury producing or cause property damage write Accidents can either produce personal injuries or cause property damage OR Accidents can either injure people or damage property.

· Use visual cues to guide readers such as:

· bullets or numbers to signal items in a list

· indented lists

· boldface to emphasize key points

· Use good document design: use plenty of white space; avoid all uppercase letters and underlining; use serif typefaces (such as Times New Roman used here); and use left-justified, ragged right margins.

· Display material suited to visual presentation in well-designed, clear visuals such as tables, charts, and maps.

1

Applied Sciences

Architecture and Design

Biology

Business & Finance

Chemistry

Computer Science

Geography

Geology

Education

Engineering

English

Environmental science

Spanish

Government

History

Human Resource Management

Information Systems

Law

Literature

Mathematics

Nursing

Physics

Political Science

Psychology

Reading

Science

Social Science

Home

Blog

Archive

Contact

google+twitterfacebook

Copyright © 2019 HomeworkMarket.com