Your development team has been consistently achieving their sprint goals for the past four sprints with a stable velocity of 30 story points. In sprint planning for the next iteration, the team commits to 30 points of work. However, by mid-sprint during the daily standup, it becomes clear that three critical stories are blocked due to an unexpected production outage requiring immediate team attention. The team estimates they can only complete 18 points this sprint. What should the scrum master do?
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 →Your manufacturing equipment upgrade project is in the executing phase. A key vendor has submitted deliverables for the third milestone, but during the inspection process, your quality assurance team identifies that 15% of the components do not meet the specifications outlined in the procurement contract. The vendor claims the specifications were ambiguous and requests additional payment to remake the components. This is causing a potential two-week delay. What is the BEST course of action?
You are managing a construction project with a fixed budget of $2.5 million and a 14-month timeline. During month 6, you conduct an earned value analysis and discover that the Cost Performance Index (CPI) is 0.85 and the Schedule Performance Index (SPI) is 0.92. The project sponsor asks you to forecast the final project cost and determine what actions are needed. Using the current performance trends, what is the most appropriate estimate at completion (EAC) if you believe current variances are atypical and future work will be performed at the planned rate?
You are leading a regulatory compliance project using a hybrid approach where legal requirements are managed predictively with sequential gate approvals, while technical implementation uses iterative sprints. After three sprints, the compliance team reviews the working software and identifies that two implemented features may not fully satisfy regulatory requirements. The development team argues that requirements were ambiguous and their interpretation was reasonable. The next compliance gate is in two weeks. What is the best course of action?
