Your agile team has completed a sprint and is conducting a sprint review with stakeholders. During the review, a key stakeholder sees the working software for the first time and requests significant changes to the user interface, saying it doesn't match their expectations. The team completed all committed user stories and met the acceptance criteria as originally defined. The stakeholder insists these changes must be made immediately. How should you respond?
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?
You are facilitating sprint planning for a three-week sprint. The product owner presents the prioritized backlog, and the team begins selecting user stories. After selecting six stories totaling 24 story points, three team members mention they have committed to attending a mandatory company training program that will take them away for three full days during the sprint. What should the team do?