Here’s an article I came across that talks about how the subtle difference in language can make a big difference in how we see things when it comes to the work we do (or don’t do) in a sprint.


Bak in 2011, the Scrum Guide changed over from using “Commitment” to “Forecast” when talking about the work agreed to by the development team in a sprint. This was done to change the perception.


What are your thoughts? Do you think it matters? Is it important to have “commitments”?



Bob Shirley

Supervisory IT Specialist, Design & Development

Office of Chief Information Officer

Library of Congress

(410) 874-3156 w / (336) 681-0182 c

cid:<a href=[log in to unmask]">