The 5 ways to PREVENT ScrummerFall!
There are many names for dysfunctional Scrum—one of which is ScrummerFall. Scrummerfall is embedding Waterfall phases inside of a sprint and it’s alive and well in 2020, 25+ years after Scrum was first introduced. You would think we’d be able to do it “right” by now. The Scrum Guide says that you should have a Definition of Done and a potentially shippable increment at the end of each sprint. It does not say, keep rolling stories from sprint to sprint (carryover) or take credit for partially done work. We hear it all the time development team members complaining at retrospectives that we do not have enough time to complete all the stories. And team members often work overtime the last week of a sprint to ensure the definition of done is accomplished. Why do they do this? In this session, you will learn 5 practical, try them at home, techniques that will inoculate your teams from the ScrummerFall virus. They will also inspire behaviors to create a more self-organized cross functional team. Leading to you playing Scrum as it was intended and delivering the goods for your stakeholders.