If Developers struggle to forecast, what should Product Owner Mary do?

• A. Inform the Scrum Master so he/she can help the Developers learn techniques for improving their ability to forecast work and, as the PO, spend more time with the Developers
• B. Ignore the issue
• C. Replace the Scrum Master
• D. Tell Developers to work faster

Answer: (A)

When forecasting is slipping, the team needs support to improve their estimation skills and the workflow around it. The Scrum Master is the right person to coach the Developers, help identify blockers to accurate forecasts, and introduce or reinforce estimation techniques such as planning poker, relative sizing, and breaking work into smaller, more estimable items. Informing the Scrum Master creates a path to better practice and removes impediments that distort forecastability. At the same time, the Product Owner should spend more time with the Developers to clarify backlog items, ensure acceptance criteria are clear, and provide the context needed for realistic estimates. This collaborative coaching and hands-on guidance help the team forecast more reliably and align what they commit to with stakeholder expectations. Options that ignore the issue, replace the Scrum Master, or push speed over quality don’t address the underlying forecasting capability and can undermine the process.