Your agile team has completed three sprints of a mobile application project. During the sprint retrospective, several team members express frustration that they are spending too much time in meetings and not enough time developing features. The Scrum Master notes that the team is attending daily standups, sprint planning, sprint reviews, sprint retrospectives, and several ad-hoc meetings called by stakeholders. Velocity has declined from 32 story points in Sprint 1 to 21 story points in Sprint 3. What should the Scrum Master do first to address this issue?
Study this topic
WBS Work Breakdown Structure: Proven Best PracticesMaster the essential techniques for creating effective Work Breakdown Structures that drive project success and align wi…
More Process Questions
View all →You are leading an agile project to develop a mobile banking application. The team has just completed Sprint Planning and committed to delivering eight user stories in the upcoming two-week sprint. During the daily standup on day three, a developer mentions that one of the stories is taking much longer than estimated and may not be completed. What should you do first?
During a sprint retrospective for your software development project, team members identify that unclear user story acceptance criteria have caused significant rework in the past three sprints. The team estimates that 30% of their time has been spent redoing work that didn't meet unstated expectations. What should the team do to address this issue?
Your agile team is building an e-commerce platform. At the sprint review, the team demonstrates a completed shopping cart feature to stakeholders. The functionality works as specified in the user story, but the product owner notices the user interface colors don't match the company's recently updated brand guidelines, which changed during the sprint. What should happen next?