Community Blog

Velocity has become a word specifically associated with measuring how well a Scrum Team is doing. This metric is often associated with negative feeling new Scrum Teams are feeling towards Agile in general.

In diesem Blog untersuchen wir, woher diese Grundhaltung kommt, zeigen, wie wir damit umgehen können, leisten Überzeugungsarbeit und bieten Experimente an, d. h. wir

Heeeey. What's good this week awesome people? I hope you are well and keeping safe. During the recent lockdown in Brisbane I created a video about how Professional Scrum team plan their Sprints with Kanban.

Story Points and velocity have been used for many years in the Scrum community and have been engrained so much in the way that things are done that most folks believe that they are part of Scrum.

In the 2020 update of the Scrum Guide, the Sprint Planning section has had a very welcome update. Every part of Scrum has a purpose, a reason to why it's included in the framework, and this update made the purpose - raison d'etre - of the Sprint Planning clearer. Let's see how!

If you currently are in search of the answer to this question, enjoy this video.

Every Sprint starts with a Sprint Planning event. It is very crucial to ensure that the Scrum Team comes to a shared understanding of what and how are they going to deliver a “Done” increment that creates maximum business impact.

Dwight D. Eisenhower, the World War II leader and U.S. President, wrote: “[...] plans are of no particular value, but [...] planning is indispensable”.