|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/agile-methodology-in-pmp-preparation-journey/
课程评论：没有评论
本课程旨在帮助您全面理解PMP备考所需的所有敏捷知识。课程内容涵盖： * **敏捷宣言的四大价值观和十二项原则**：深入剖析敏捷核心理念。 * **Scrum 方法论**： * **Scrum 如何指数级降低风险**：理解Scrum的风险管理优势。 * **Scrum 三大理论支柱**：透明（Transparency）、检视（Inspection）、适应（Adaptation）的含义与应用。 * **Scrum 四种仪式（Ceremonies）**： 1. **Sprint 计划会议**：强调产出价值的重要性，会议时长会根据Sprint周期调整，需要设定SMART目标，并回顾产品待办事项、已交付的产品增量、团队容量以及持续改进。 2. **每日站会（Daily Scrum）**：15分钟的团队内部会议，确定未来24小时的工作安排。 3. **Sprint 评审会议（Sprint Review）**：非正式会议，用于检视产品增量和调整产品待办事项，主要目标是向客户展示增量并收集反馈，鼓励协作，目的是优化价值。对于一个月周期的Sprint，建议4小时。 4. **Sprint 回顾会议（Sprint Retrospective）**：类似“经验教训”会议，Scrum团队进行自我检视，制定改进计划。此会议夹在Sprint评审和下一个Sprint计划会议之间，有助于团队应用评审反馈进行规划和改进。会议聚焦于质量和范围，团队坦诚交流，讨论进展、问题及改进建议。 * **Scrum 三个关键产物（Artifacts）**： 1. 产品待办事项列表（Product Backlog）。 2. Sprint 待办事项列表（Sprint Backlog）。 3. 产品增量（Product Increment）。 * **Scrum 三种角色（Roles）**： 1. 产品负责人（Product Owner）。 2. Scrum 主持人（Scrum Master）。 3. 开发团队（Development Team）。 * **待办事项列表梳理（Grooming the Backlog）**：强调产品负责人与开发团队协作，持续优化产品待办事项列表，以提供价值。 * **Sprint 待办事项列表的生成**：解释在Sprint计划会议中，为应对产品待办列表的动态变化，设定目标并预测Sprint结束时的产品增量，从而产生Sprint待办事项列表。 * **看板（Kanban）和燃尽图/燃起图（Burn up and down charts）**：全面理解这些方法论的实际应用场景。 本课程将通过丰富的场景和详细的解释，助您深入掌握敏捷方法论。
The course builds a complete understanding of all the Agile needed in the PMP journey.The course contains a complete explanation of the four values, the twelve principles, the entire Scrum methodology, how is Scrum reduce risk exponentially, The three pillars of Scrum theory "transparency, inspection, adaptation". Scrum ceremonies1- Sprint planning Sprint planning is essential part of producing value.The actual sprint planning meeting is time boxed may be one hour for short sprint or may be eight hour for longsprint (one month). The sprint must have SMART Objective. Also important point sprint planning are reviewing the product backlog, product increments that may have been produced prior to this planning meeting, projected capacity of the development team during the sprint, and a focus on continuous improvements by looking at past performance2- Daily scrum The daily Scrum is a 15-minute time boxed event specific to the development team and determine what the next 24 hours will look like.3- Sprint review Sprint review is an informal event. It is to inspect the increments and adapt the product backlog asneeded. The major goal of the sprint review is to present the increment to the customer in order to gain their feedback and to encourage collaboration. looks at the things that have been done, it is also looking forward to determining the next things that could be done to optimize value. What was valuable to the customer a month ago may very well have changed so welcome to change, the customer has the ability to inspect the increment and give his feedback. The best practice for the sprint review would be a four-hour time boxed meeting for the typical one-month sprint. if the sprint was shorter, the event would be shorter as well.4- Sprint retrospectiveThe retrospective like a lessons learned meeting, the Scrum team spend three hours inspecting itself and to create a plan forimprovements. The retrospective is sandwiched between the sprint review and the next sprint planning meeting, so the team can keep in mind what was talked about in the review and use that information to plan forward while improving the results.The big focus is on the quality and the scope. The team is transparent about their feelings on what went well, what did not go well, and what changes they would like to see made.Scrum artifacts 1- product backlog. 2- Sprint backlog. 3- product increment.Scrum roles:-1- Product owner. 2-Scrum master. 3-Development team.Grooming the Backlog The product owner and the development team are working together to provide value, so it is important to refine the product backlog constantly in a process called grooming.The Sprint Backlog Because the product backlog is constantly changing and being updated, it is necessary to set goals and to forecast what the increment might look like at the end of an iteration called the sprint and it is happened during the sprint planning meeting, That is why there is a sprint backlog.Kanban, and burn up and down charts. You will achieve a comprehensive understanding of these methodologies in full and good scenarios for complete explanation.
