This thread somehow filtered into one of my folders and I'm just now seeing it. Very interesting discussion.

I agree with the analogy of a sports team to some extent. You go into the competition fully committed and expecting to win. However, in a competition, one competitor always loses. And how to deal with falling short of expectation, short of commitment, or what happens when our dedication, or preparation is not enough, is a tough thing to figure out. It takes soul searching and rework.

In this scenario, we're not in a competition with anyone except ourselves. Actually, thinking about it again, maybe we are in competition: with others' expectations of what we can achieve as part of Modernization. IMO, where the analogy breaks down is that we can decide what it means to “win” and we can decide what's in and out of scope, and continue redefining and refining it as we go along, so that we meet our most important targets and discard other ideas along the way. We can also engage our stakeholders so that we can guide their expectations and let them be a part of the process, rather than judging from the outside, or being in the dark for several years, and then having the curtain lifted.

Just a few thoughts from an amateur competitive combat sport athlete and professional code slinger.


From: Panchal, Mahesh
Sent: Friday, September 3, 2021 9:27 AM
To: Nibeck, Mike; Shirley, Robert L.; Agile at Library; ECS_SAFE_LACE; ECS_SAFE_ScrumMasters; ECS_SAFE_PO; ECS_SAFE_PM
Cc: Panchal, Mahesh
Subject: RE: Commitment vs. Forecast

In reality what “Dev Team” is doing – their best GFE-2-Deliver (yes, Good Faith Estimate of their Efforts to deliver that undertaken tasks / work); and hence with asking themselves to be self-accountable, being a team – an autonomous who knows to self-organize & self-manage at their best, with the mentoring, guiding & coaching of their Scrum Master and/or Agile Coach, “Commitment” is the rightly used.


Forecast is very light word to be used here in this light. Yes, Forecast is backed by substantial data and/or derived information, but will it be accompanied by the Accountability of the Doers ? Forecast is mostly used by professionals in Business : Finance & Accounting, Sales & Marketing and at other such teams.


I never heard any Sports Team Forecasting their WINS in any championship, but yes they are COMMITED for the WINS at their best.


I second the thought of Mike for the use of “Commitment”.



Mahesh Panchal

IT Specialist, Design & Development

Office of Chief Information Officer

Library of Congress


cid:<a href=[log in to unmask]" style="width:1.6388in; height:.6597in" src="cid:[log in to unmask]">



From: Nibeck, Mike <[log in to unmask]>
Sent: Thursday, September 2, 2021 9:22 PM
To: Shirley, Robert L. <[log in to unmask]>; Agile at Library <[log in to unmask]>; ECS_SAFE_LACE <[log in to unmask]>; ECS_SAFE_ScrumMasters <[log in to unmask]>; ECS_SAFE_PO <[log in to unmask]>; ECS_SAFE_PM <[log in to unmask]>
Subject: Re: Commitment vs. Forecast


Words mean things and I really like the use of “Commitment”. 



On: 02 September 2021 10:21, "Shirley, Robert L." <[log in to unmask]> wrote:

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]" style="width:1.6319in; height:.6597in" src="cid:[log in to unmask]">