The aim of Sprint Planning is to select a few Product Backlog ordered, “ready” Items and derive a Sprint Backlog and a Sprint Goal.

Background This post discusses journey mapping, a visual representation of the customer journey experience, including all their...

In this document, we will discuss swarming and multitasking.

Q talks about velocity, how to use it and reminds you that the team commits to the Sprint Goal and not their forecast velocity.

Q talks about "multitasking" and why it not only does not work but also causes lots of bad outcomes. Then he goes into swarming. If you are

Q talks about scaling communication and coordination between teams working to deliver a product. This is not only for Scrum teams!

Q talks about the Sprint Retrospective, the key event for continuous improvement. Hint: Please watch the Inspect and Adapt video before this

Q talks about inspecting people, processes and tools and adapting them to maximize flow.

Q talks about the Interrupt Buffer and how it can increase delivery predictability for Agile teams and avoid unnecessary stress for all invo

Q talks about Sprint Planning. However, a lot of what is discussed here can be used for any kind of short term planning, not only Scrum.

Q talks about the Sprint Review, a feedback mechanism for the Scrum Team or Teams and how to use it to maximize value.

Q talks about creating new teams by splitting existing ones and why we should not consider stable teams to be a dogma.

Q speaks the Sprint Goal, output and outcome.

Q talks about backlog refinement and why "getting it right" saves considerable time in planning and execution.

Q talks about the Daily Scrum and why it is key to plan for the day and avoid turning it into a status meeting.

Q talks about why most Scrum teams hate the last day of the Sprint and what can we do to avoid the horror and dread.

Q talks about the key aspects of Agile Leadership and potential bumps in the road.