|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/master-post-mortems-for-continuous-improvement/
课程评论：没有评论
课程名称：进行更好的事后分析项目事件 课程概述：事后分析是一种在项目管理、事件响应及其他商业领域中极为重要的工具。它不仅帮助团队避免消极问题，还通过深入学习有效经验来提升积极成果。此外，事后分析并不是为了指责某个团队或个人，而是为了促使团队改进和提高。在进行事后分析时，营造一个没有指责的环境对于其成功至关重要。 本课程的设计由两个主要部分组成： 第一部分 - 如何进行事后分析 本部分涵盖成功实施事后分析的步骤，包括： - 定义事后分析过程中应包含的内容 - 如何收集信息，包括识别参与者和所需信息 - 分析发现的内容，从所有数据中得出结论 - 召开事后分析会议，集思广益，探讨如何在下次做得更好 - 实施改进，将所学应用于实践 第二部分 - 培养改进的文化 本部分重点讨论如何帮助团队关注改进，远离指责。讲座内容包括： - 建立认同感 - 说服他人事后分析的重要性，先从小处入手，再逐步扩展 - 养成事后分析的习惯 - 不仅在特殊场合进行，而是对每个项目都进行事后分析，以培养习惯 - 无责备 - 事后分析不是为了指责，而是为了帮助我们所有人做得更好 适合报名的人群： 本课程适合任何可能参与或负责进行事后分析的人。以下角色通常会涉及此过程： - 软件工程师：分析系统故障并识别改进机会 - 系统管理者：确定系统故障原因并避免发生 - 分析师：了解项目为何成功，并帮助他人实现成功 - 客户支持：拆解升级事件并避免类似问题 - 项目经理：确保通过有效的事后分析完成项目，特别是在面对意外挑战时 - 敏捷教练：丰富您的工具箱，采用促进团队成长和效率的实践 为什么选择本课程： 每个项目、事件、升级、失败和成功等都应进行分析，以了解其发生原因。选择本课程是因为您希望从成功和失败中学习，并希望您的团队专注于改进，而不是指责。
Post mortems are an incredibly important tool in project management, incident response and other areas of business. They not only help groups avoid negative problems, but also enhance positive outcomes by digging in and learning what works.Additionally, post mortems are not a way to blame a team or an individual - they're a way for the group to improve and do better. Cultivating a blame-free environment when conducting post mortems is critical to their success.This course is designed around two main sections:Section 1 - How to conduct a post mortemThis section covers how to run a post mortem successfully, and includes things like:Defining what will be included in your post mortem processHow to collect information - including identifying who should be involved and what information you needAnalyzing what you find - Drawing conclusions from all that dataConducting a post mortem meeting - getting everyone together to brainstorm how to do better next timeImplementing improvements - How you'll take what you've learned and make it realSection 2 - Cultivating a culture of improvementThis section focuses on how to help your team focus on improving, and moving away from blaming. Lectures include:Building buy in - Convincing others that post-mortems are important can be hard, start small and build out.Making a habit of post mortems - They shouldn't be only only on special occasions, do them for every project to help build a habit Blameless - post mortems aren't meant to blame, instead they're meant to help us all do betterWho Should EnrollThis course is meant for anyone who might be involved in a post mortem, or expected to run one. Examples of roles that tend to do this include:Software Engineers: Analyze system failures and identify improvementsSystems Managers: Determine the cause of system faults and avoid themAnalysts: Figure out why a project is successful and help others do the sameCustomer Support: Pull apart an escalation and avoid themProject Managers: Ensure project closure with effective post-mortems, especially following unexpected challenges.Scrum Masters: Augment your toolkit with practices that foster team growth and efficiency.Why Choose This Course:Every project ,incident, escalation, failure, success (and more!) should be analyzed to see why it happened. You should choose this course because you want to learn from success (and failure), and because you want your team to focus on improving - not blame.
