Scrum Sprint Planning Anti-Patterns (8) – Not a Team Event (Hands-on Agile Webinar #5)

START FROM EPISODE #1:

There is no shortage of Scrum anti-patterns, impeding your team’s ability to deliver value to your customers. This Hands-on Agile mini-series covers Scrum’s sprint planning ceremony.

The purpose of the sprint planning is to align the development team and the product owner. Both need to agree on the shippable product increment of the next sprint. The idea is that the development team’s forecast reflects the product owner’s sprint goal. Also, the team needs to come up with a plan on how to accomplish its commitment.

Easier said than done, it appears.

This Hands-on Agile mini-series addresses 12 common sprint planning anti-patterns. Learn how to keep a simple scrum ceremony useful by avoiding typical mistakes, from pushy POs, toying with the definition of ready to obstructing the future flow by pushing utilization to 110%.

This episode covers the exclusion of some scrum team members from the sprint planning: The development team does not participate collectively in the sprint planning. Instead, two team members, for example, the tech and UX lead, represent the team. (Regarding the idea of one or two ‘leading’ teammates in a scrum team, there are none. And unless you are using LeSS – no pun intended – where the scrum teams are represented in the overall sprint planning, the whole scrum team needs to participate. It is a team effort, and everyone’s voice hence needs to be heard.)

HOST: Stefan Wolpers