Do you create a Sprint Forecast? (aka The functionality that will be developed during the Sprint)

Last updated by Gordon Beeming [SSW] 5 months ago.See history

After the Sprint Planning meeting, it is useful for the Development Team to send the Product Owner (PO) a Sprint Forecast for the next Sprint. Doing this helps to improve common understanding in, and sometimes to enforce, the relationship between the PO and the Team.

This is simply an agreement between the Development Team and the PO for one Sprint and should be confirmed via an email at the beginning of every Sprint.

“The implementation team agrees to do its best to deliver an agreed on set of features (scope) to a defined quality standard by the end of the Sprint. (Ideally they deliver what they promised, or even a bit more). The Product Owner agrees not to change his instructions before the end of the Sprint.”
Agile Project management

Each Sprint in a Scrum project can be considered a mini-project that has time (Sprint Length), scope (Sprint Backlog), quality (Definition of Done) and cost (Team Size * Sprint Length). Only the scope can vary and this is measured every Sprint.

Figure: Good example - Copy this as email template and send to Product Owner

::: info Tip: You can copy and paste the Sprint Backlog as a table into the email body:

  1. Go to Azure DevOps and navigate to the Sprint's Backlog view
  2. Remove the unnecessary columns so it looks clean
  3. Select all items, copy, then paste into the Sprint Forecast email :::
We open source. Powered by GitHub