PMP Practice Question: Process — Agile, Hard
An agile team developing a healthcare platform has maintained consistent velocity at 38 story points for six consecutive sprints. During the retrospective, technical debt items are repeatedly raised but never addressed because the product owner prioritizes new features to maintain competitive advantage. The lead architect warns that accumulated technical debt is increasing the time required for new features by approximately 30%, and estimates two full sprints would be needed to address critical technical debt. Code quality metrics show increasing defect rates and decreasing test coverage. What is the most appropriate action?
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 construction project is in month 18 of a 30-month schedule. A new environmental regulation has been enacted that requires additional soil remediation procedures for your project site. The regulation applies retroactively to work already completed. Your legal team estimates compliance will add $1.2M in costs and 3 months to the schedule. You have management reserve of $800K and schedule reserve of 6 weeks. The contract includes a force majeure clause and regulatory change provisions. Your CFO wants to minimize financial impact, your customer is concerned about schedule, and your legal counsel advises documenting everything for potential claims. What is your best course of action as the project manager?
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?