Estimate vs. Commitment
The distinction between estimates and commitments is crucial in project planning. Teams can provide a range of story points based on historical velocity, but committing to a specific number often requires more time for accurate assessment. Organizations may prefer immediate commitments or opt for a flexible approach, allowing for adjustments based on observed productivity over time.In this clip
From this podcast

Software Engineering Radio - the podcast for professional software developers
SE-Radio-Episode-273-Steve-McConnell-on-Software-Estimation
Related Questions
Can you explain realistic goal setting in detail as discussed in the episode SE-Radio-Episode-273-Steve-McConnell-on-Software-Estimation and the clip Estimation and Commitment?
Can you explain realistic goal setting in detail in the context of the episode SE-Radio-Episode-273-Steve-McConnell-on-Software-Estimation and the clip Estimation and Commitment?
What are the challenges of estimation in the episode SE-Radio-Episode-273-Steve-McConnell-on-Software-Estimation and the clip Estimation in Scrum?