|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/agile-in-the-program-management-office/
课程评论：没有评论
课程名称：项目管理办公室的敏捷方法（PMO） - 新版 课程概述：敏捷是一种迭代的项目管理方法，旨在帮助团队更快地为客户提供价值，并减少约束。课程中将不断评估需求、计划和结果，使团队能够快速响应变化。敏捷不仅是一种方法，更是一种思维方式，受到敏捷宣言的价值观和原则的指导。这些价值观和原则可以帮助组织应对变化与不确定性。 在课程中，我们将探讨如何将项目管理办公室从基于瀑布的方法转变为基于敏捷的方法，了解瀑布与敏捷管理之间的不同。课程内容还涉及商业敏捷性，强调整个组织需要支持敏捷思维，以便员工能够更有效地应用敏捷原则。 学习目标： 1. 为利益相关者准备敏捷原则和流程所带来的变革。 2. 与治理部门合作，审查基于敏捷的项目和程序。 3. 管理混合投资组合。 4. 利用敏捷原则和流程提升项目管理办公室的绩效。 主要敏捷概念： - 用户故事：与客户或产品负责人协商后，团队将工作分割为称为“用户故事”的功能增量。 - 每日会议：团队每天在同一时间开会，更新协调所需的重要信息。 - 人物角色：在用户体验为关键因素时，团队创建详细的虚构用户传记，称为“人物角色”。 - 团队：敏捷中的“团队”是指一小组全职参与同一个项目的人。 - 增量开发：大多数敏捷团队偏好增量开发策略，确保每个产品版本都是可用的，并在前一个版本的基础上增加功能。 - 迭代开发：敏捷项目具有迭代特性，允许重复进行开发活动，并可能重新审视先前的工作产品。 - 里程碑回顾：项目进行一段时间后，团队全体成员会集中一天到三天对项目重大事件进行详细分析。 通过本课程，您将能够实现在项目管理中应用敏捷方法，从而提高效率和响应能力。
Agile is an iterative approach to project management that helps teams deliver value to their customers faster and with fewer constraints.Requirements, plans, and results are evaluated continuously so teams have a natural mechanism for responding to change quickly.Agile is a Mindset: Ultimately, Agile is a mindset informed by the Agile Manifesto's values and principles. Those values and principles provide guidance on how to create and respond to change and how to deal with uncertainty. What about Business Agility?The two concepts noted to attempt to move Agile "outside of software." Those efforts have resulted recently in the Business Agility movement. You might say that business agility is a recognition that in order for people in an organization to operate with an Agile mindset, the entire organization needs to support that mindset. Agile software development was never truly Agile until the organization changed its structure and operations to work in an uncertain environment.In this course: We will travel to where you serve as a PMO director and guide the transformation of your office from a waterfall-based to an agile-based PMO. And we will explore and discover the differences between waterfall and agile management.By the end of this course, you will learn to:Prepare key stakeholders for the changes Agile principles and processes will bringWork with governance to conduct reviews of agile-based projects and programsManage a mixed portfolioImprove your project management office's performance using Agile principles and processes.Key Agile ConceptsBelow are a few key Agile concepts, during the course will get more. User Stories: In consultation with the customer or product owner, the team divides up the work to be done into functional increments called "user stories." Each user story is expected to yield a contribution to the value of the overall product. Daily Meeting: Each day at the same time, the team meets so as to bring everyone up to date on the information that is vital for coordination: each team member briefly describes any "completed" contributions and any obstacles that stand in their way. Personas: When the project calls for it - for instance when user experience is a major factor in project outcomes - the team crafts detailed, synthetic biographies of fictitious users of the future product: these are called "personas." Team: A "team" in the Agile sense is a small group of people, assigned to the same project or effort, nearly all of them on a full-time basis. A small minority of team members may be part-time contributors or may have competing responsibilities. Incremental Development: Nearly all Agile teams favor an incremental development strategy; in an Agile context, this means that each successive version of the product is usable, and each builds upon the previous version by adding user-visible functionality. Iterative Development: Agile projects are iterative insofar as they intentionally allow for "repeating" software development activities, and for potentially "revisiting" the same work products.Milestone Retrospective: Once a project has been underway for some time, or at the end of the project, all of the team's permanent members (not just the developers) invest from one to three days in a detailed analysis of the project's significant events.
