Lessons Learned from projects Presented by Andrew Soswa

Lessons Learned from projects Presented by Andrew Soswa On behalf of PMI Chicagoland Chapter 1

Agenda • About PMI Chicagoland Chapter and PMI Global • PMBOK guide • List of PMBOK project documents • Minimum documentation to complete a project • Lessons Learned Register & Repository • Sample of documents All sources are derived from PMI PMBOK guide Presentation Title 2

PMI Chicagoland Chapter Mission The mission of the PMI Chicagoland Chapter is to promote project management knowledge, standards and ethical practice for members, the profession and the community. Stats: 10 Executive Board + President 23 Board of Directors 120 Volunteers 3, 600 Members 2 major events (PM Leadership and PM Symposium 50 meetings/event 150 projects/programs Our website: www. pmichicagoland. org Contact us: support@pmichicagoland. org PDUs Report 1 PDU to the technical side of the Talent Triangle Presentation Title 3

PMI Global • Leading not-for-profit professional membership association for the project management profession. • Founded in 1969, PMI delivers value to 500, 000+ members strong worldwide, with members spanning 208 countries and territories and forming 292 local chapters that bring project professionals together. • Offers: – Certifications, 870, 429 PMPs – PMBOK Guide, 6 million guides in circulations – 100’s of templates and professional webinars in Project. Management. com repository Presentation Title 4

PMBOK guide • First edition published in 1996 • Last edition, version 6, was released in September 2017 • Last edition contains: – 10 Knowledge Areas – 49 processes – 33 project’s documents Presentation Title 5

List of PMBOK project documents Source: PMBOK guide Presentation Title 6

Minimum documentation to complete a project • Note that PMBOK frequently uses “might be” and “should be” to allow flexibility and tailoring project’s processes to the firm’s needs • Documents – Business Case – Assumptions and Issue Log – Risk Register – Requirements Traceability Matrix – Work Breakdown Structure – Estimates document (Resource, Cost, Task, Effort, Duration) – Project’s Plan in MS Project – Status Report – Change Log – Lessons Learned Register – Closing Note Presentation Title 7

Lessons Learned Register & Repository • Lessons Learned Register is a project document used to record knowledge gained during a project so that it can be used in the current project and entered into the lessons learned repository. – It is used in 34 of out 49 processes • Lessons Learned Repository is a store of historical information about lessons learned in projects – It is stored at the end of a project or phase Presentation Title 8

Lessons Learned process Source: Rowe, S & Sikes, S. Retrieved from https: //www. pmi. org/learning/library/lessons-learned-next-level-communicating-7991 Presentation Title 9

Why are Lessons Learned important? • Any firm can have valuable resources but it also must have capability to use the resources effective to creative a distinctive competency – Capability is ability to coordinate resources and use their skills to a productive use • In Project Management, a distinctive competency is the knowledge, or more properly wisdom that come from applying knowledge in real life examples • Thus sharing the knowledge will help the firm to have better Project Managers, who will run projects in better and innovative ways Presentation Title 10

Sample of Issue Log Presentation Title 11

Sample of Risk Register Presentation Title 12

Sample of Lessons Learned Register Part 1 Source: Project. Management. com Retrieved from: https: //www. projectmanagement. com/templates/download. cfm? ID=423809 Presentation Title 13

Sample of Lessons Learned Register Part 2 Presentation Title 14

Sample of Lessons Learned Register Source: CDC. gov Retrieved from: https: //www 2 a. cdc. gov/. . . /templates/CDC_UP_Lessons_Learned_Log_Template. xls Presentation Title 15

Lessons Learned Q & A • What is a best practice for assessing relevant lessons learned in the planning phase of a new project? • Any experience with building lessons learned into a project risk assessment? • What is a best practice for collection, storage and reporting of lessons learned by project? Presentation Title 16

Lessons Learned Q & A • Any experience with conducting mid-project lessons learned and/or at project milestones? • How do teams, groups, or Divisions take the information gained from the Lessons Learned session and proceduralize the outcome so that current work processes, standards, procedures, activities, and work flows are adjusted and updated to reflect the Lessons Learned and become part of the way projects are performed in the future? • Any best practices for the Lessons Learned Report out to the Project Team and the Lessons Learned Report out to Senior Leadership? Presentation Title 17

Lessons Learned Q & A • Any best practices for data gathering in advance of the actual Lessons Learned session? • Discussion on the range of timeframes to allocate for the Lessons Learned session. • What’s the best way to prioritize and implement LL effectively across a large organization when most have many projects happening at the same time and anywhere from 20 -100+ lessons learned from each project. It’s impossible to ensure implementation of everything across the board, especially when the organization has many projects at different phases. Presentation Title 18