3 ms·
In fact, Scrum changed the word “commitment” to “forecast”. https://www.scrum.org/resources/commitment-vs-forecast https://www.scrum.org/resources/commitment-v
by Terretta 8y ago
In fact, Scrum changed the word “commitment” to “forecast”.
https://www.scrum.org/resources/commitment-vs-forecast https://www.scrum.org/resources/commitment-vs-forecast
“One of the most controversial updates to the 2011 Scrum Guide has been the removal of the term “commit” in favor of “forecast” in regards to the work selected for a Sprint. We used to say that the Development Team commits to which Product Backlog Items it will deliver by the end of the Sprint. Scrum now encourages the Development Team to forecast which Product Backlog Items it will deliver by the end of the Sprint. It may seem to be a simple wording change, but in fact there are strong reasons behind it.”
Pretty sure the Scrum folks are aware of needs of enterprises and their deadline addiction.
- lima 8y agoYes - sprints can be a great estimation tool as long as they aren't mistaken for a deadline or performance measurement. In my opinion, it needs be more like drawing a (rough) "this is how far we will get at the current velocity" line somewhere in the sorted backlog, rather than a fixed set of tickets that you expect to get done. Popular tool-driven "agile" workflows where you move tickets into a particular sprint, followed by the admission of defeat at the next sprint planning meeting when you failed to complete all of them, reinforce the idea of "commitments" rather than "forecasts".