Scrum Sprint planning Meeting

The Sprint planning meeting was held on the first day of the sprint, and the meeting was divided into two parts, with the Plan meeting 1 being attended by PO, SM and team, mainly from the product backlog to select the backlog of products that need to be placed in the current sprint, and then by SM, Team participated in the program meeting 2, the story of the backlog is split into tasks to estimate, PO can also participate in this part to understand the specific development details. I will list the main contents of the meeting below. (following meeting content from scrum checklists) meeting content Sprint Planning Meeting 1

The product owner and team work together to set the Sprint target and the established product backlog based on the previously evaluated results.

Target

Set Sprint targets and established product Backlog

meeting Ready to invite Attendees: Product owner, Scrum Master, all members of the team have prioritized the issues in the product backlog evaluate the backlog to make the product backlog available to everyone in the meeting to ensure that it can be obtained as expected Who is clearly absent from the team (e.g. vacation) ensure room environment is suitable for group discussions everyone can get the results of the last Sprint review meeting and the Sprint review meeting the sprint schedule is scheduled for sprint Schedule Meeting 1 when the sprint Schedule meeting 2 The first day of the scheduled sprint has determined that the last day of the sprint determines the timing of the Scrum daily meeting schedule Sprint Review Meeting Schedule (optional) Prepare the Pushpin board for the Backlog: a Pushpin board at least 2x2 meters, Cards and stickers, highlighter (optional) as cards for planning cards

Conference Process (4 hours) make the sprint schedule public for everyone to open the results of the Sprint review meeting to everyone. The results of the Sprint Review meeting are open to everyone. Product Leader Product Vision product owner and team identify Sprin T target if there is a problem missing from the backlog: the product owner has permission to add a question to the backlog if the product backlog is not evaluated at all: Select the problem you think is the smallest use case in the backlog and assign a workload of 2 story points. With this minimum use-case workload standard, you assign the story points of other issues in the backlog if some of the issues in the backlog have not yet been evaluated: based on the workload of the other issues, the amount of story points to evaluate these issues if the items in the product Backlog have not yet been properly Sort by priority: Product owner is prioritized for each item in the Backlog product owners and team members recognize this Sprint target and established product backlog

Conference Results

Prepare scheduled product Backlog Sprint Schedule Meeting 2 for Sprint planning meeting 2

In Sprint planning Session 2, the team refines each item in a given product Backlog into multiple tasks. The time to complete each task is limited to one day.

Target

Identify all tasks, generate sprint Backlog, confirm sprint targets

meeting Ready to invite Attendees: Scrum Master, all team members, product owners (who can have access to all questions) task planning can refer to the established Product backlog (optional) Prepare the Pushpin board for the backlog: a Pushpin plate at least 2x2 meters, Cards and stickers, highlighter pens

Meeting Process (4 hours) team members separate tasks from the Backlog to ensure that all the details of the work are taken into account: coding, testing, code review, meetings, learning new technologies, writing documents if the task takes more than a day: try to split the task into several small tasks If the team believes that there are too many items in the Sprint backlog: work with the product owner to prune the backlog if the team thinks that there are too few items in the Sprint backlog: Join the sprint Backl to pick the most important questions from the product backlog with the product owner The OG team confirms the Sprint target

Conference Results Sprint goals and sprints are open to everyone in the company and all team members can get tasks in the sprint Backlog