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<https://scrumguides.org/index.html> 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"?

https://www.scrum.org/resources/commitment-vs-forecast


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="/cgi-bin/wa?LOGON=A3%3Dind2109%26L%3DAGILEATLIBRARY%26E%3Dquoted-printable%26P%3D1098%26B%3D--_000_6818a718467f444aadb8ebb0dbca0b23acfxex02LCDSLOCGOV_%26T%3Dtext%252Fplain%3B%2520charset%3Dus-ascii%3B%2520name%3D%2522%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD%2522%26N%3D%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD%25EF%25BF%25BD" target="_parent" >[log in to unmask]</a>]