Part 3 in a 5-part series. This post covers Commitment. Agree or disagree, it doesn’t matter. What does matter is committing.

The third value;

People personally commit to achieving the goals of the Scrum Team

Scrum.org

One of my former IBM colleagues, says it something like this way.

“We agree and commit, or we disagree and commit, we just need to commit to action.”

Mo Shah

At times, team members fail to personally commit to achieving a state goal. There are many reasons for this. It’s different for each person.

More frequently, the team fails to set goals. That’s a bit of a “mic drop”.

Agree or disagree just commit

Problem-solving is never easy. It is a part of life that is unavoidable. As a result, it takes courage to tackle challenges.

Gaining team alignment is challenging as well. Defining team goals is worth the effort to avoid friction.

If there is disagreement about a goal, objective, or outcome then the difference can be worked out.

A disagreement should not prevent team commitment.

If Scrum is being properly applied, then changing goals in future Sprints is acceptable to address the disagreement. This goes to the heart of being transparent, inspecting the outcome, and adapting to get a better outcome.

A wonderful, potential outcome is alignment as work is progressed. The act of moving forward can be a catalyst. As a result, commitment can help in getting past disagreement.

Value 1, Value 2, Value 3, Value 4, Value 5