Best Practices
- 1. Tips for Conducting a Successful Post Mortem Review Plan Your Post Mortem Review Require Team Participation Hold the Post Mortem Review Meeting List Items Done Well and Things Needing Improvement Create a Post Mortem Summary Report Best Practice in the Spotlight – Lessons Learned
- 2. Best Practice in the Spotlight – Lessons Learned After every project, no matter how major or minor, the entire staff (not just management) should pause to perform a "post-mortem" Identify processes or practices which worked well Identify what didn’t work well Feedback can be anonymous Keep to the facts Acknowledge you need each other to be successful Allows team to figure out what things were done well and to document the things that need improvement Aids in building a knowledge base that teams coming behind you can review to ensure they get the most out of their upcoming projects The key to a successful project is to learn from past mistakes, self reflection translates to improvement.
- 3. Best Practice - Lessons Learned Platform or Phase Comments Ways to improve Where do we need to improve? What went well? Topic
- 4. Summary of Feedback People Process Training / Communication Strategy Implementation Planning Testing Design & Development FRD Mapping BRD Initiation & Timelines SAMPLE
- 5. Yearly Planning v Objectives v Priorities · Projects · Production Support (Issue Tracking/Analysis) · Maintenance · End of Year Calibration (Projects/ Production Support/Maintenance) v Budgetary Baselines, Management & Measure · Internal · External (Vendor) · LOB Spend Breakdown · End of Year Calibration (Expected Spend Vs. Total Spend) v Organizational Chart, Roles and Responsibilities Platform Specifics v Technology Usage · Overview (Broad description of Platform and usage) · LOB Platform Usage Matrix · Supported Site Matrix (LOBs, Version, Service Pack, Depts., Users, Lic) Development Standards v Architecture · Standard Platform Topography/Schema · Site Architecture Diagrams · Site Network Diagrams · Supported Configurations Matrix (Peripheral Platforms, Versions) · Hardware Profile (Server build information) v Asset Inventory · Hardware · Software v Other Solutions/Services · Technology Overview · Platforms/Applications Departmental Processes v Projects · Delivery Process Flow (Request Initiation through post implementation) · Forecast Questionnaire/Change Request Profile Form · Co-supplier Roles & Responsibilities · RACI · SLAs v Production Support · Internal Trouble Ticket Process · Co-supplier Roles & Responsibilities · Vendor Trouble Ticket Process · RACI · SLAs v Maintenance · Maintenance Request Process · Release Schedule v Vendor Engagement · Sales/Training · Support · Professional Service · R&D · Contacts and Escalation Path · SLA Matrix v Financial · Standard Cost Guides · Vendor · Spending approval process · Asset Depreciation Schedule High Level Organizational Charter
- 6. Other LOB Obligation: Initiatives/Plan, Prioritization, Define SVL, UAT Business Mgmt. Obligation: Control, Measure & Improvement, Process Development Platform Owners –HOM/Scope! Project Mgmt. Obligation: Service Requests – Project Tracking, Auditing, Delivery Process Adherence Platform Obligation: Requirements, Design, Develop, Test and Implement Solutions, Process Adherence, SME’s, Vendor Mgmt., Sys. Mgmt., Issue Resolution, Define SVL Platform Owners Co-suppliers Project Mgmt. Communication & Partnership CL IENT SOLUTIONS Doc Business Plan>>>Governance>>>Communication>>>Evaluation>>>Control Senior Leadership & Business Engagement Shared Accountability Operating Model Client Out In Other