Still hearing sprint planning being referred to as a two-part event? Ever been in a sprint planning where developers had to explain their plan of work to the product owner and scrum master?

What you may be dealing with are relics of sprint plannings past. To understand how sprint planning has changed, we’ll take a look at the evolution of the event throughout the years.
Read the full article…

Now that we’ve examined the history of daily scrum, we can shed some light on common anti-patterns of the event. Many of these are relics from Scrum Guides past: like scrum, the Guide inspects and adapts for continuous improvement. In other words, if you’re still following practices from an older Scrum Guide, you may be doing your team a disservice.
Read the full article…

Ever been in a daily scrum that sounds like this?: “Yesterday, I… Today, I… I’m blocked by….”
Does your scrum master still show up to every daily scrum?
Have you heard the one about the chickens and the pigs?

Scrum is an ever-evolving framework. And the events within it evolve too. As a result, some artifacts from past iterations of the events will still linger. You might be wondering where they came from.
Read the full article…