PMC post implementation review

20. Jun 2013
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
PMC post implementation review
1 von 43

Más contenido relacionado

Was ist angesagt?

How to set up a project management office (PMO)How to set up a project management office (PMO)
How to set up a project management office (PMO)PM Majik
PMO PresentationPMO Presentation
PMO Presentationwilliamfranklin
PMP_Project Stakeholder ManagementPMP_Project Stakeholder Management
PMP_Project Stakeholder ManagementHisham Haridy MBA, PMP®, RMP®, SP®
The pmo   strategy discipline execution valueThe pmo   strategy discipline execution value
The pmo strategy discipline execution valueOrlando Lugo
Project manager-roles and responsibilitiesProject manager-roles and responsibilities
Project manager-roles and responsibilitiescollege
Project Plan templateProject Plan template
Project Plan templateDemand Metric

Destacado

Post Implementation Review TemplatePost Implementation Review Template
Post Implementation Review TemplateEdmond Cheng
Lesson Learned ReportLesson Learned Report
Lesson Learned ReportAnand Subramaniam
eXtreme programmingeXtreme programming
eXtreme programmingJean Pаoli
Mgmt forum MTC 5Mgmt forum MTC 5
Mgmt forum MTC 5Jean Pаoli
Design patternsDesign patterns
Design patternsJean Pаoli
Design patterns introDesign patterns intro
Design patterns introJean Pаoli

Similar a PMC post implementation review

ContentsTeam Work Schedule3Team Task Assignment3Project .docxContentsTeam Work Schedule3Team Task Assignment3Project .docx
ContentsTeam Work Schedule3Team Task Assignment3Project .docxbobbywlane695641
Methodology Patterns (Agile Cambridge 2014)Methodology Patterns (Agile Cambridge 2014)
Methodology Patterns (Agile Cambridge 2014)Giovanni Asproni
DevOPs Transformation WorkshopDevOPs Transformation Workshop
DevOPs Transformation WorkshopJules Pierre-Louis
Project Management The Managerial Process 5th Edition Larson Solutions ManualProject Management The Managerial Process 5th Edition Larson Solutions Manual
Project Management The Managerial Process 5th Edition Larson Solutions ManualKemppe
New pmp exam webinar slide  no annotation (No Annotation)New pmp exam webinar slide  no annotation (No Annotation)
New pmp exam webinar slide no annotation (No Annotation)CliffordEgbomeade
The New PMP Exam: Changes and Implications (With Annotation)The New PMP Exam: Changes and Implications (With Annotation)
The New PMP Exam: Changes and Implications (With Annotation)CliffordEgbomeade

Similar a PMC post implementation review(20)

Último

Fixing Your OKRs With Agility – Agile Indy 2023Fixing Your OKRs With Agility – Agile Indy 2023
Fixing Your OKRs With Agility – Agile Indy 2023Yuval Yeret
EQX Corporate PresentationEQX Corporate Presentation
EQX Corporate PresentationEquinox Gold Corp.
ResumeResume
ResumeAnthoneyHuff
Marv Wexler - Transform Your with AI.pdfMarv Wexler - Transform Your with AI.pdf
Marv Wexler - Transform Your with AI.pdfSOLTUIONSpeople, THINKubators, THINKathons
IMD World Talent Report 2023.pdfIMD World Talent Report 2023.pdf
IMD World Talent Report 2023.pdfPaperjam_redaction
Grand Challenges & Platform EcosystemsGrand Challenges & Platform Ecosystems
Grand Challenges & Platform EcosystemsPaavo Ritala

PMC post implementation review

Hinweis der Redaktion

  1. The quality of future products can be improved by improving the way the products are developed. WLE (Work Life Effectiveness) Help future projects avoid pitfalls Help future projects avoid long hours Help future projects succeed This is NOT where we celebrate our success. The celebration needs to be a separate event. The PIR is hard work. Need to stay focused on the task. Requires considerable thought. Celebrating our success should not be work.
  2. What have we proven to work that should be repeated by future projects? Where do the existing processes not meet our needs? What do we want to make sure future projects don’t do? Where can we standardize – the benefits here are the same as those for driving us toward having standard processes across the organization? Where can we automate tasks? Simple tasks that are repeated many times Complex tasks that are prone to error
  3. (Last 2 sentences in the OSP will be discussed during the review of the process) Notice the timing – “prior to closure”. PLC project closure has the successful completion of a PIR as an entry criteria. Known by many names – retrospective, post mortem, post implementation review. Our PIR is different than any other at Intel due to our new opportunities (to be described later).
  4. If we want to remain competitive, we must improve quality and efficiency. We must continually move forward. CMMI is a process improvement framework. Insanity: doing the same thing over and over again and expecting different results. - Albert Einstein
  5. This is the environment that most all of Intel is currently in. Once learnings are identified, the trick is to be able to effectively pass these learnings along to future projects. The people from the old project go on to new projects and hopefully will take at least some of the learnings with them. This usually limits the learnings passed along to the domains of the personnel passed along. If you are fortunate enough to have a database or website where learnings can be archived (the shaded part of the picture), new projects can find relevant learnings to apply to their project. This relies on a pull system (the end user having the desire and time to go get the information), and a structure that allows a person to find relevant learnings within a large database. Hopefully the project personnel will have the time, desire, and mechanisms to sift through the information and find something meaningful to his/her project. Relying on ‘hope’ for the foundation for process improvement is not very reassuring (hope people take learnings with them; hope new projects have experienced people on them; hope PMs will/can find applicable learnings in a large database; hope new projects are aware of pitfalls experienced by past projects; hope the word gets passed along). The Intel retrospective web site states that incorporating BKMs/Key Learning’s into subsequent projects is the most challenging part of the process! And that having no closed loop to require key learning’s to be considered for subsequent projects is a major issue. WE HAVE AN OPPORTUNITY TO RESOLVE THIS.
  6. This is the environment that ISTG is in. This provides us with a huge advantage that affords us some great opportunities. All projects use the standard processes. Each project incorporates its learnings back into the standard processes. This enables a project to share its learnings (using a push system) with the entire organization, all geographies, and all applications. So the objective of the PIR is to improve future projects by identifying and sharing learnings, preferably by using the process change control procedures.
  7. The JAD that developed the PIR process decided that the PIR meeting must not exceed 2 hours, which meant that a survey taken prior to the meeting must be used to collect information from which to derive the learnings.
  8. Review tables 3.1 and 3.2, including notes. Table 3.1: Planning is done early in the life cycle (during the Planning Phase), immediately after the entry criteria has been met. Entry criteria – names do not necessarily have to be assigned to roles, as long as you know which roles need to participate (including any stakeholder who uses the processes). The PIR must be conducted at the end of the project. However, the PIR process may be utilized at additional points in the life cycle (e.g., at the end of a phase, or after an event like a delivery by a supplier). Table 3.2: Go to the survey tool and walk through how to set up a survey. Survey tool provides anonymity if that is important (some groups find this important, other groups want to know who sent the information – this can vary by country and is dependent on the culture). Notice the timing of the PIR in the Notes. A completed PIR is an entry criteria to PLC Closure. The standard survey MUST be used, and CANNOT be modified, but CAN be appended with additional questions if desired.
  9. Review table 3.3, including notes. Table 3.3: Survey participants must include the project manager, all personnel attending the PIR meeting, and those stakeholders who will not attend the PIR meeting but have used the processes. These individuals are identified in the PMP. Notice the objective in step 1. Review eBG-PC-42-Post Implementation Review Survey.doc. Survey: Survey asks for 3 most successful activities, and 3 biggest pain points. This is the team’s opportunity to improve the next project and fix what is broken. Describe the successful activity in enough detail that the process can be updated with the information. ‘Enough detail’ means that future projects can execute these successful BKMs. The description of the crucial issue and its root causes are steps to the objective, which is the resolution and hence the process improvement/learning. The expectation of those surveyed is that substantial thought be put into what went well and what didn’t. Substantial thought must be put into the root cause and resolution for the PIR activity to add any value. Quality (process) improvement must be a way of life for us, and this takes a concerted effort. The resolution of each root cause of an issue is the process improvement. The root cause and resolution must be in enough detail to effectively initiate a process change.
  10. Take time to really think about ‘why’ the issue occurred. Make this an informal analysis. Use paper and pencil if necessary, but this may be able to be done in your head if the issue is simple enough. There is no “right” answer, so don’t worry about getting it wrong. Think about what could have existed so that this issue would not have occurred on your project. This is the process improvement. Please document this as the resolution. You may have several resolutions, especially if there is more than one root cause. If you can’t figure out the resolution, just document the issue and root cause(s), leaving the resolution blank. If you can’t figure out the root cause, just document the issue and leave the rest blank (but make sure you put forward a legitimate attempt at identifying the root cause). FOR THE RESOLUTION: Think about the existing process. What would have helped prevent this from occurring? Add a template (checklist; taxonomy; email template; etc.). Add a field to a template. Add descriptive/instructional text (in italics) to the field of a form. Add a comment with instructions to an Excel cell. Add an item to a list (a role to the R&R org standard; an item to an existing checklist; etc.). Clarify a process step. Assign a different role to a process step. Process should require that a record be archived. Etc., etc., etc.
  11. As a class, complete these exercises. Complete the survey table for each example with the root cause(s) and resolution(s). Do not spend more than 3-4 minutes on each exercise (1-2 minutes may suffice).
  12. Assumption: No known errors were made during programming (so you didn’t know how to program it).
  13. Review table 3.4, EXCLUDING notes. Table 3.4: eBG-TP-45-Post Implementation Review Presentation Template.ppt will be reviewed in a subsequent slide. Concentrate only on extracting the results from the surveys and recording them on either the survey results spreadsheet (for process change requests) or the presentation template (either as learnings/tips that are not process improvements, or as open items to be analyzed during the PIR meeting). This step is to organize the feedback from the surveys. Combine duplicate issues or successes. The root causes may not be identical, so list all unique root causes and resolutions that are valid. This will require a new mindset. Try to apply every resolution and BKM to processes since this is the most effective way to proliferate the learnings. Most all learnings will be able to be applied to a process, and very few will need to be tips.
  14. Review the notes in table 3.4. Survey (eBG-PC-42-Post Implementation Review Survey.doc): Successful activities If question 2/7/12 is answered “no”, determine if the BKM is truly better than the existing process, and why the process was not followed (root cause). If questions 3/8/13 is answered “yes”, then there is no further action required. The BKM is already required. If question 3/8/13 is answered “no”, then the BKM is not included, or is not clear, in the existing process and needs a process change request. If question 4/9/14 is answered either “yes” or “no”, a process change request is needed. The answer to questions 4 and 5 help determine the resolution. Issues For questions 17/19/22, verify that these are the root causes. Complete the root cause analysis if incomplete or missing. For questions 18/20/23, verify that the resolution will prevent the issue from occurring in the future, and correct or embellish if necessary. Ensure that each root cause has a resolution.
  15. Complete the template through the ‘Open Items’ page. The remainder of the template is to be used to document the decisions made during the meeting, and to document meeting minutes. Any ‘Tip’ without an action plan probably will not be able to be used in the future. Sensitive issues (e.g., human resource issues) may be dealt with offline and not documented. The time-boxed agenda provided is only a guideline. Make a best-guess as to the priority of the Open Issues and list them in order of importance, highest importance first.
  16. As a class, discuss what action the PM should take. Refer to the speaker notes on the previous slide to help disposition each example. Do not spend more than 3-4 minutes on each exercise (1-2 minutes will be all that is needed on most).
  17. Assumption: the process does not mandate how to track the build process.
  18. Review table 3.5. Table 3.5: Open the process change request spreadsheet (eBG-TP-55-PIR Survey Results.xls embedded in the presentation) and validate the proposed change requests that will be submitted. Validate the ‘Tips’ and corresponding ‘Action Plans’.
  19. When addressing the Open Issues, take a little time (but not too long) to prioritize them since analysis time is limited. Start by asking if there are any disagreements with the order in which they appear, with the highest priority being listed first. Try to come to a quick resolution as to the priority. If agreement cannot be reached, use a more formal technique. THIS IS NOT A SKILLS CLASS. Nominal Group Technique Assign a letter to each item (first item is A, second item is B,…). Assume 5 items on the list. The most important item receives a 5, the next most important receives a 4, … and the least important receives a 1. The highest priority MUST have the highest value so a non-vote (equating to 0) does not increase an items priority. Each participant ranks the items and assigns a score, 5 through 1. The project manager adds the rankings for each item. The sum for each item indicates is priority, with the highest sum receiving the highest priority. Limit the number of rankings to 10, even if there are more than 10 items. Each participant only ranks the top 10 items, with all other items receiving a 0 from that participant. Weighted Multivoting Assign a letter to each item (first item is A, second item is B,…). Assume 5 items on the list. Each participant has 100 votes to distribute among the items. A participant may give all 100 votes to a single item, or spread the votes among several items depending on their relative importance. The project manager adds the ratings for each item. The sum for each item indicates is priority, with the highest sum receiving the highest priority. If the sums are close, another round may be performed between the items with close vote totals.
  20. THIS IS NOT A SKILLS CLASS. Use fishbone diagram (a.k.a. cause and effect or Ishikawa diagram). You may only get a couple of these completed in one hour, so make sure you prioritize. Make sure everyone agrees on the problem statement. Include as much information as possible on the “what,” “where,” “when,” and “how much” of the problem. Use data to specify the problem. Modify the categories of the major bones to fit the situation. Keep asking “why” until you have reached the root cause (go no more than 4 levels deep). A root cause may appear multiple times. These root causes may be more critical than others. Visio has a root cause template (see attachment).
  21. Perform the root cause analysis as a class. Using a white board would be easiest, but this can also be done via NetMeeting by completing the Visio attachment above. This exercise will take approximately 10-15 minutes).
  22. Review tables 3.6 and 3.7. Table 3.6: Process Coach will submit the process change requests. Table 3.7: Archive the PIR presentation/minutes in the project records repository.
  23. Students should be referred to the web site for the most current list of terms and definitions.
  24. Write the test codes on the board and be prepared to give them to the students.
  25. There are 2 resolutions, one for each root cause. Both root cause resolutions could be a combination of a process and a template.
  26. There are 2 root causes. The first root cause has no resolution (unless we want to buy a new VCR). Some root causes will not have resolutions. Notice that the second root cause resolution does NOT state that I should go back and read the VCR instructions. This only addresses the symptom, and is a bandage. We need to ensure we fix the root cause for future project, which in this case needs to address ALL appliances and electronics so I know how to use them.
  27. It is important to precisely state the issue. Notice that the “gas gauge is STILL broken”, putting the issue in context. So the gas gauge did not JUST break. Also notice that this is a compound issue signified by ‘because’, so there are actually 2 related issues. If one issue is resolved, the other goes away, but both may need to be resolved due to the length of time to fix the primary issue. There are 3 root causes, and 3 resolutions. The last resolution has 2 alternatives. The EPG may choose one, or may include tailoring criteria if both are accepted.