|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/pmi-acp-certification-initiation-and-requirements-gathering/
课程评论：没有评论
课程名称：PMI-ACP认证：启动与需求收集 概述：欢迎参加敏捷项目管理系列课程中的第四门课程——PMI-ACP（敏捷认证从业者）认证课程。本课程专注于敏捷规划，特别是项目启动与需求收集。本课程适合项目经理、项目主管，或任何希望有效参与敏捷项目的人士。内容符合项目管理协会（PMI）制定的敏捷认证从业者考试目标和认证ScrumMaster的学习目标。课程包括培训视频、案例、练习和小测验。若您按照学习资料进行学习，您将获得5个PDU学分，这对于PMI认证考试和维护您的PMI认证是非常有帮助的。 在敏捷开发团队中，通常采用滚动波规划和渐进式详细规划，在项目生命周期的各个阶段对计划进行完善和调整。规划的好处在于降低风险和不确定性，改善决策，促进信任，并使信息更易于传递给利益相关者。 课程内容包括： - 三个层次的规划：敏捷团队专注于发布规划、迭代规划和日常规划。 - 发布规划：涉及需求收集、创建用户故事、优先级排序、故事估算、分组及设定发布日期。 - 迭代规划：更详细，涉及更新需求、确认用户故事和优先级、将故事分解为任务以及在新迭代开始前进行估算。 - 业务案例与产品愿景：制定业务案例和产品愿景是启动敏捷项目的第一步。 - 项目范围与用例：项目范围是工作范围，使用敏捷方法，团队关注直接对客户有价值的功能。 - 用户故事：将高层次需求分解为具体、可实施的需求。 本课程分为两个主要部分：第一部分为敏捷规划导论，第二部分为启动与定义敏捷项目。完成第一部分后，您将能够识别敏捷规划的层次，了解敏捷项目规划的好处，并确定不同阶段的活动。完成第二部分后，您将能够理解业务案例的基本要素，识别产品愿景的要素，分析用例示例，并制定用户故事示例。 感谢您考虑参加本课程！点击“报名参加”按钮，让我们在课堂上见！
Welcome to the 4th course of the Agile Project Management - The PMI-ACP (Agile Certified Practitioner) Certification Program. This course is focused on Agile Planning and more precisely on Project Initiating and Requirements Gathering. Who will benefit from taking this course This course is intended for project managers, program managers, or anyone who wants to efficiently participate in agile projects. It is aligned with the Agile Certified Practitioner exam objectives developed by the Project Management Institute® and Certified ScrumMaster learning objectives. The course includes training videos, examples, exercices and quizes. And, if you take your time to go through all the learning materials this will entitle you to claim 5 PDU's for the PMI certification exams and to maintain your PMI certification. An agile development team uses rolling wave planning and progressive elaboration, refining and adjusting plans at various points throughout a project's life cycle. Planning is beneficial because it reduces risk and uncertainty, improves decision-making, fosters trust, and makes it easier to pass on information to stakeholders. Three levels of planning Agile teams focus on three levels of planning. During release planning, the customer and developers collaborate to provide high-level information on what user stories, or features, and how many iterations, to include in a product release. During iteration planning, a team conducts detailed planning of the tasks to complete in a specific iteration. This planning is informed by the results of previous iterations. Daily planning occurs during brief meetings, when developers discuss their progress, immediate plans, and any obstacles. Release and iteration planning In an agile approach, release planning involves gathering requirements, creating user stories, prioritizing stories, estimating stories, grouping stories, and setting a release date. Iteration planning is more detailed. It involves updating requirements, confirming user stories and priorities, decomposing stories into tasks, and refining estimates before each new iteration begins. A business case and a product vision The first step in planning an agile project is developing a business case and a product vision. The business case is a short document outlining the opportunity that a project represents, the project's goals and a strategy for achieving them, a project vision, milestones, the required investment, and the expected payback. The product vision is a description of what will be delivered - which is encapsulated in a vision statement, of who will be involved in creating a product, and of how the work will be done. A project scope and a use case A project's scope is the extent of the work it includes. Using an agile approach, a team controls project scope by focusing only on developing functionality that is of direct value to the customer. A use case provides an overview of a project's scope. It describes how users must be able to interact with a system, and the required results. It also describes exceptions, or the steps that must occur in response to system errors. User stories User stories break down the project's high-level requirements into specific, discrete requirements for particular product functions. They're usually expressed using the wording "As a , I want to so that I can." An agile team may need to break large user stories, known as epics, into smaller stories as a project progresses. It may also group related user stories into themes. This course will have two main sections. The first one is called Introduction to Agile Planning and the second Initiating and Scoping an Agile Project. After completing the first section, Introduction to Agile Planning, you be able to: recognize the levels of agile planning,understand the benefits of having a plan for an agile project,identify activities that take place during the different phases of agile planning. After completing the second section, Initiating and Scoping an Agile Project, you will be able to: understand the essential elements of a business case,identify the elements of product vision,analyze an example of a use case,develop examples of user stories. So, thank you for considering this course! Now, go ahead, and hit that "Take This Course" button. And, see you on the inside.
