You are leading an agile transformation for a distributed team building a customer portal. After three sprints, you notice that the team's velocity has dropped from 45 to 28 story points, and sprint goals are consistently not met. During daily standups, team members report blockers related to waiting for architectural decisions from a centralized enterprise architecture group that reviews designs every two weeks. The product owner is frustrated with slow progress and wants to add more developers. Team morale is declining as members feel they cannot control their outcomes. What is the most effective approach to restore the team's ability to deliver value?
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?