Appendix D: Lean Charter Template ‘The following Lean Team Charter Template, which was developed to support EPA Lean projects, may be used to dlrify and promote understanding of the scope and expectations for Lean events and projects. MCR Project Details Project Name: Event Dates: Room: Region/Office: Event Start & End Times: ‘Management Briefings Dates: Times: Locations: Project Sponsor: Project Deseri Process Description: Customers & Deliverables of the Process: Problem(s) to Address in Project: /What is the problem (real or perceived) the team is trying to address in the project? What evidence do you have that the problem exists? How could we deliver more value for the customer?) Project Scope [What are the start and end points in the process that the project will address?] Process Start: Process E Boundary Conditions [What are the boundaries and limitations of the scope (i.e., what is excluded from the process being addressed)? What types of changes are off limits or out of bounds to the team?] Appendix: ean charterTempbte» Page 6&Goals, Objectives, and Metrics [Goals define the desired outcomes for the project — that is, what success looks like. Objectives set specific and measureable targets for improvement. Express your goals and objectives as percent reductions if you do not have current, baseline data for the process, or set specific targets for the future if you can.] Quantitative Goals & Objectives ‘The following table provides a summary of the team’s quantitative targets for the Lean project. Perey ores ey aC eek Ceo) EXAMPLE 1: Lead Time 1100 business days B business days EXAMPLE 2: Processing Time TBD at event 130% 1. Lead Time 2. Processing Time 3. Number of Process Steps 4 Percent Complete and Accurate 5. Participant Satisfaction with the Process (1-5 scale) 6. [Other metrics] Qualitative Goals & Objectives [Specify any qualitative goals and objectives for the project, such as clarify roles and responsibilities, create standard work procedures, improve communications, improve customer satisfaction, etc.) Pre-Work ‘The following actions represent what tasks need to be completed prior to the Lean event. a CC 1. [pre-event task] [person responsible] [mm/dd/yy] 2. [pre-event task] [person responsible] [mm/dd/yy] 3. Follow-Up Schedule ‘The team will confirm these dates during the event in the context of progress and future needs. '30-Day Management Briefing: [mm/dd/yy] ‘Other Key Milestones: 60-Day Management Briefing: mm/dd/yy] 90-Day Management Briefing: /mm/dd/yy] Appendix: eancharterTempbte» pageTeam Members [ideally 8-10 people. The majority (75-80%) should be people who work in the process; also include 1-2 supervisors of the process, and 1 customer or stakeholder. Note the name and function that each person serves, such as data entry, document production, supervisor, quality control, IT specialist, customer, etc.) 1. [Name, function] 5. [Name, function] 2. Name, function] 6. [Name, function] 3. [Name, function] 7. (Name, function] 4, [Name, function} 8. [Name, function] On-Call Support [identify any individuals who will be available as needed during the event or project to answer questions, address issues, or make decisions to enable to the team to succeed. Include contact information if appropriate.] © [Name, function} © [Name, function} Approvals ur signatures show our commitment to this project and our willingness to take actions to ensure its success. De ‘Append: b: lean Charter Temple» Page 70Appendix E: Lean Implementation Plan Template Lean implementati Jerect sponsor fo-pay [mm/yr] [ream teader lo-oay [rma |rzaator fo-bay — [rma [event oate femonth [mw lvear froma fate created fnvaalio] fast updated: (rm " senso af ee vmevast | mms | ime ‘oie sdorneoratl Ten Tren 2] ime tm | tmmvseind | mvt sae sonseorat ema [eaters Tse oe 2] clita, [stdzeymemenns | mmvauy | tmmasina | sven tare Somaag st sonseorat Ten Tse oe of ee vmevast | mms | ime ‘oie sdorneoratl Ten Tren 5] eit tm | tmmvseind | mvt sae Somaog ee sconseorat