Six Sigma Black Belt Project Information

1. Six Sigma Black BeltProject Information Prepared: July 20, 2004

2. Steering Committee • Identifies projects • Identifies black belts • Allocates resources • Monitors progress • Reviews effectiveness • Establish implementation strategy and policies

3. Steering Committee Expectations • Do you have a steering committee at your organization? • What is its expectations regarding six sigma?

4. Black Belt Responsibilities • After the project • See that documentation is completed and lessons captured • Monitor implementation if appropriate • See that control plan is handed off to Process Owner

5. “Contracting” Process • Establish mutual expectations between the project manager and the process owner. • Clarify roles and resources. • Identify the needs of the process owner. • Establish a follow up plan.

6. Customer/Client Requirements • Requirements are a want or need that is tied to expectations. • Satisfaction is a positive margin between what is expected and what is received. • Project manager is responsible for setting expectations. • Expectations must be converted to a measurable requirement.

7. Project Purpose • Why goals and project is important • Charter is vehicle for developing and communicating purpose • Written charter defines and clarifies the project.

8. Elements of a Charter • Problem Statement: Short description of the problem and why it should be worked. • Background: Summary of data collected during define stage. • Objective: Concise statement of project quantified goals.

9. Elements of a Charter • Output Measures: Presentation of metrics to be tracked for this project. • Boundaries: Clearly state the scope and limitations of the project. • Results: To be complete at the conclusion of the project. • Approvals:

10. Project Charter Includes • The business case • The problem statement • Project scope • Goals statement • Milestones • Roles and responsibilities of the project team

11. Project Charter Do’s • Make problem statement specific • Focus on observable symptoms • Use Charter to set direction, goals • Address project questions early

12. Project Charter Don’ts • Assign blame in problem statement • Set non-obtainable goals • Make the charter wordy

13. Business Case • Given to the team by the Leadership Council • Gives a broad definition of the issue • Gives rationale why this project is a key business priority • Compelling reason to commit resources

14. Problem Statement • Concise statement of the problem • Under what circumstances does problem occur • Extent of problem • Impact of problem • Opportunity if problem is eliminated

15. Project Scope • An important element in the charter • Sets boundaries on what’s included/excluded • Seek a balance • Viewed as a contract to avoid scope creep

16. Goal Statement • Specific • Measurable • Attainable • Relevant • Time bound

17. Milestones • Indicates when and where the team should be in the process • Set limits for other steps in DMAIIC process

18. Define Phase Do’s • Give equal attention to Service and Output requirements • Create clear goals and objectives • Measurable requirements are essential to understanding your customers

19. Define Phase Don’ts • Fail to measure your performance against customer requirements • Close your mind to new information • Make new requirements your standard operating procedures (SOP)