Prepared by | [Your Name] |
---|---|
Meeting Date | [Date] |
Meeting Time | [Time] |
Location | [Venue] |
Role | Name |
---|---|
Product Owner | [Name] |
Scrum Master | [Name] |
Development Team | [Name] |
Development Team | [Name] |
Introduction
Welcome and Introduction of Attendees
Overview of Pre-Sprint Planning Objective
Review of Previous Sprint
Review of Sprint Goals
Discussion of Achievements and Challenges
Identification of Lessons Learned
Product Backlog Refinement
Review of Product Backlog Items (PBIs)
Identification of High-Priority PBIs for Sprint
Sprint Goal Setting
Definition of Sprint Goal
Alignment of Sprint Goal with Product Vision
Task Estimation
Breakdown of PBIs into Tasks
Estimation of Effort for Each Task
Assignment of Tasks to Team Members
Capacity Planning
Evaluation of Team Capacity
Adjustment of Sprint Backlog as Necessary
Definition of Done (DoD) Review
Review and Confirmation of Definition of Done
Agreement on Acceptance Criteria for Sprint Deliverables
Review of Sprint Timeline
Confirmation of Sprint Duration
Discussion of Sprint Start and End Dates
Action Items
Assignment of Action Items
Deadline Setting for Action Item Completion
Closing
Summary of Key Decisions
Next Steps and Reminders
Scrum Guide
Product Backlog Template
Sprint Backlog Template
Definition of Done Template
The team appreciated the structured approach to pre-sprint planning and found the agenda comprehensive and well-organized.
Some team members suggested incorporating more time for in-depth discussions on complex user stories or technical challenges during future planning sessions to ensure better understanding and alignment.
There was consensus among participants that defining and adhering to the Definition of Done (DoD) was crucial for maintaining quality and delivering valuable increments consistently.
It was suggested to implement a retrospective at the end of each pre-sprint planning meeting to reflect on the process and identify areas for improvement proactively.
Templates
Templates