Sprint Planning Meeting
Intermediate English listening exercise · Dev Team Meetings
Transcript
[Scrum Master] Alright team, let's kick off our sprint planning for Sprint 23. We have two weeks and our velocity from last sprint was forty-two story points. [Developer 1] Before we start, the authentication refactor from last sprint is still in code review. It's about eighty percent done. [Scrum Master] Got it. Let's carry that over. That's eight points. So we have about thirty-four points of capacity. [Developer 2] The product team wants us to prioritise the search feature. Users have been requesting it for months. [Scrum Master] How many points did we estimate for search? [Developer 2] Thirteen points. It includes the backend API, frontend UI, and indexing. [Product Owner] That's our highest priority this sprint. We also need the payment bug fixed — customers are getting double-charged. [Developer 1] That bug is critical. I can investigate it today. I'd estimate five points including testing. [Scrum Master] Okay, so we have the auth refactor at eight, search at thirteen, and the payment bug at five. That's twenty-six points. We have eight more points of capacity. [Developer 2] What about the technical debt ticket for database optimization? It's five points and it'll improve page load times significantly. [Scrum Master] Let's add that in. And we'll keep three points as buffer for unexpected issues. Everyone agree? [All] Sounds good. [Scrum Master] Great. I'll update the board. Daily standups at nine AM as usual.
Comprehension questions
- What was the team's velocity last sprint?
- What is the critical payment bug causing?
- What is the sprint number mentioned during the planning?
- What percentage of the authentication refactor is completed?
- How many points is the technical debt ticket for database optimization?