QDT 19-Nov-2007 Bob - opening: just one manual, non invasive, improving lab processes Jed: a program that works for us and is compliant with orders -team building exercise -project familiarization -key decision: QA, contractor assurance -reach agreement about aproach to deliver first draft of QAP to OQBP by Dec 19 -deliverables: slides delivered to Bob and Bruce: cover, approach to completing the QAP, high level schedule to complete dec 31 deliverable Lots to cover today!! Tim - comments - QA documentation has become the QA program in the past (no real interest in process or real QA, only in the book) - needs to be a common currency for risk assessment: program - cost of QA program must be less than expected benefit - approach is all based on risk; another approach is to see how elements of QA apply to process 4 stages of team develoment: forming, storming, norming, performing Styles & personalities: drivers, enthusiasts, analyzers, affiliators Ground rules Strategy: 3 components: -build qa program to meeet lab goals and leverage to improve effectivenes -use risk based graded approach to tailor -single qa plan and implementing procedures team roles and repsonsibilites: you are spokesperson and decision maker for your org and a two way conduit to and from team. will bring in scribe to take minutes for future meetings; today is mostly infor exchange with two key decisions which ed will capture. functions of qdt: -make binding decisions -review and refine existing draft documents -create new documents -establish stabdard approach & implementing docs to meet requirements of DOE order and lab neds -flowchart processes -collect and collate existing QA practices -identify gaps -create plan and schedule for program -establish metrics for reporting on and tracking progress -periodic briefings to OQBP, AC, D/S heads, staff Proposed communication plan: staff metings, milestone briefings to AS and DS heads, fermilab today, small group metings, OQBP website. Inventory of draft docs: -QA plan -QA approach -graded approach procedure, tables, forms -control of docs and records procedure -PQBP doc master list -IMS correctve and preventve action procedure form (issue management system): we will get a demo of the IMS tool suggestion: doc inventory should include intended audience Tools: -draft documents (head start) -flowcharting -project management tool -process improvement methodologies (brainstorming, affinity diagrams, force field, run charts, six sigma - DMAIC, lean, benchmarking, lessons learned -OQBP website Rich will give briefing on PM tools, probably at a special meeting All QA docs under configuration mgmt, with proposed doc control procedure QDT deliverables: -QA plan to OQBP by 12/19, by 12/31 to doe -graded approach procedure, tables, forms -refine approach doc -create project plan for development -develop implementing documents and process pams -establish metrics and reporting functions on progress -map existing QA practices to requirements -identify gaps -create project plan for implementation -periodic briefings -create lab wide plan for formal assessments Group discussions and brainstorming - Ed There are no stupid ideas Lessons learned: what worked, what didn't - previous lab wide QA, other projects lots of input from team, captured on flip charts what would we not do without the doe order? Key decision process: -each individual polled for vote -diffferences: explain reason, discussion, revote -no resolution-->OQBP (or AC) Decision: should we combine 414 and 226 into a single QAP, or should contractor assurance be a stand alone document number of pros and cons put forth, not a clear preference for either Contractor assurance has alot of redundancy with QA, but only applies to ES&H, cyber security, emergency response, and facility management, inparticular in the areas of assessment, incident reporting, worker feedback, issues mgmt, lessons learned, performance indicators. vote remains split, no decision for now until we better understand pros and cons and what redundancies are Plan for the plan what we submit on Dec 31 is the real deal; we canmake ater changes bu only with justification, so we do need keep implementation in mind when we submit the plan After 12/31 we review full QAP, feedback and update, lab review of full plan, DOE review, graded approach assessments and gap analysis, feedback, next round of updates and possible resubmission. Approach to plan: divide and conquer, go chapter by chapter, line by line, interactive conflict resolution, all comments and resolutions recorded, witgh meetings scheduled as: ch 1-4 11/26 (24 pages) ch 5-6 12/3 (17 pages) ch 9-12 12/10 (23 pages) 12/17 last reconcile will schedule extra sessions as needed. All in snake pit, 9-12, with potential expansion to monday afternoon. we shold also look at DOE guides to QA plans before discussions: they wil be posted on web site. Risks to the project project RA: resistance (personal, cultural, group); reources, schedule Create risk amanagment plaan: terminate (eliminate), treat (mitigate), tolerate (retain), transfer (buy insurance)