Community Blog

A self-managing team is a fundamental part of effectivity. How can this happen during Sprint Planning? Check it out!

In this video, Mark addresses the purpose of Sprint Goals and then explores the message that they are sending when it's hard to define a single Sprint Goal. This can help you ask better questions and steer your team toward higher value.

Scrum Values make the use of Scrum successful. How can you and your Team live these values during the Sprint Planning? Check it out!

If you are an agile leader - do you know whether your teams are currently operating at a sustainable pace? Do you care? Would you rather not know because you’re afraid of the answer? 

How does Sprint Planning support adaptation in order to minimise deviations from agreed goals? Each of the Scrum Events serves to adapt. So does Sprint Planning. Check out our tips!

The more ambiguous the requirement, the more difficult it is to calculate how long something will take. But teams still need to estimate their work to forecast releases. Relative sizing provides a realistic method for estimating. Ultimately, your team will find their own value scale and their own language that is meaningful to them. Until then, these Practical Fibonacci tips will help kick-start your relative sizing.

I have had the opportunity to work with some truly amazing teams that have achieved pretty amazing outcomes. One thing that every team has had in common is that, at one time, they were new to Scrum. When I engage with teams to discuss implementing the Scrum framework, they often raise potential impediments to adopting Scrum. Below are the five most common objections to Scrum and why they don’t hold any weight.

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.

Each Scrum Event serves Inspection, the second pillar of Empiricism. So does Sprint Planning. How? Find out ...

Welcome back to the professional Scrum foundations series. As introduced last week, empiricism is one of the underlying concepts of the Scrum framework.  Scrum is founded on empirical process control, and transparency is one of the three pillars.

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.

Bringing transparency by inspecting the Product Backlog and adaptation (building) the Sprint Goal, a forecast, and the Sprint Backlog.