scrum
实际冲刺计划的Scrum准备 (Scrum Preparation for the Actual Sprint Planning)
Adequate Sprint Planning is actually done by all the team members. It is not reasonable for the team representative to commit the work across the team.
实际上，所有团队成员都已完成了适当的Sprint计划。 团队代表在整个团队中进行工作是不合理的。
Key Points for Sprint Planning
冲刺计划的重点
- Team representative should prepare the sprint planning. 团队代表应准备冲刺计划。
- If multiple scrum teams are working on same product backlog, they must gather and take part in the sprint planning together. 如果多个Scrum团队正在处理相同的产品积压，则他们必须聚集在一起并参与Sprint计划。
Using the prioritized backlog, the PO presents the highest value stories to the team in order. The purpose is that everyone on the team fully understands the intent of the story and specific acceptance criteria for that story. It is also helpful to explain the definition of done for all the user stories.
使用优先的未完成订单，PO可以按顺序向团队提供最高价值的故事。 目的是使团队中的每个人都充分了解故事的意图和该故事的特定接受标准。 解释所有用户案例的完成定义也很有帮助。
Every sprint starts with a Sprint Planning Session, which includes two sessions - the WHAT-meeting and the HOW-meeting. In the WHAT-meeting the team picks the User stories from the Scrum backlog, on which they will be working. And, in the HOW-meeting, the User stories picked are further broken into small tasks with a set priority and story points.
每个sprint都从一个Sprint计划会议开始，该会议包括两个会议-WHAT会议和HOW会议 。 在WHAT-meeting中，团队从Scrum积压中选择用户故事，他们将在该故事中进行工作。 并且，在HOW会议中，所选择的用户故事进一步分为具有设定优先级和故事点的小任务。
规划的上半年-确定要实现的目标 (First Half of Planning - Deciding What to achieve)
审查冲刺目标 (Reviewing Sprint Goal)
Scrum meeting representative will show the high level vision of the project. The Product Owner identifies the goal of the Sprint and justify that how it will deliver value to the product.
Scrum会议代表将展示该项目的高层愿景。 产品负责人确定了Sprint的目标，并证明了它如何为产品带来价值。
查看产品积压 (Reviewing the Product Backlog)
Before the sprint planning meeting Product owner will rearrange the user stories and give the priority to the stories.
在Sprint计划会议之前，产品负责人将重新安排用户故事并优先考虑故事。
During Sprint Planning, PO presents the highest-priority user stories to the team. Stakeholders will give feedback on the user stories. Stories may change on the basis of stakeholder feedback.
在Sprint计划期间，PO向团队展示优先级最高的用户案例。 利益相关者将就用户故事提供反馈。 故事可能会根据利益相关者的反馈而改变。
计划的后半部分-如何完成工作 (Second Half of planning - How to get work done)
During the second half of the planning, team decide how to get work done.
在计划的后半段，团队决定如何完成工作。
创建积压 (Creating Backlog)
PO reviews the highest priority stories with team and decides how much they can do in each sprint. Everyone should commit his or her work in this planning. If someone can't commit, the PO and team need to work together to change the shape of the sprint until everyone can commit. Sprint planning is a key collaborative effort in scrum.
PO与团队一起审查最高优先级的故事，并决定他们在每个冲刺中可以做什么。 每个人都应在此计划中投入工作。 如果某人无法提交，则PO和团队需要共同努力以改变冲刺的形状，直到每个人都可以提交为止。 Sprint计划是Scrum中关键的协作工作。
更新发布计划 (Updating the Release Plan )
Once the team has committed to user stories, the Product Owner revisits the Release Plan mapping of user stories into Sprints. With the current information, stories that the team completed in the previous Sprint, stories taken off the Product Backlog for the current Sprint, the Product Owner updates the release plan.
一旦团队致力于用户故事，产品负责人就会重新访问将用户故事映射到Sprint的发布计划。 利用当前信息，团队在上一个Sprint中完成的故事，从当前Sprint的产品待办事项中删除的故事，产品负责人将更新发布计划。
Scrum takes the commitment step very seriously. Each person's commitment is very important to achieve your sprint goal. Starts from reviewing sprint goals to updating the release plans, each step must be should followed carefully.
Scrum非常重视承诺步骤。 每个人的承诺对于实现您的冲刺目标非常重要。 从检查冲刺目标到更新发布计划开始，必须认真遵循每个步骤。
翻译自: https://www.studytonight.com/scrum-framework/actual-sprint-planning
scrum