Dozens of books address the mechanics and theory behind Scrum. These books are great. But they offer little guidance to those who work on Scrum teams and are neck-deep in organizational dysfunction—and have no idea what to do next. Let's try an experiment.

Rather than trying to figure out what you need or want to hear from our session, we propose your taking over as the product owner and driving the discussion. Leveraging the power of the crowd and liberating structures, Todd Miller and Ryan Ripley will address the questions of the room and facilitate a whole-room collaborative event.

Join them as they take your most pressing, real-time questions and craft them into a session that will help you break the cycle of bad Scrum. Learn what you can do to “inspect and adapt” your way back to a healthy Scrum practice and how the Scrum Values – Focus, Commitment, Respect, Openness, and Courage - can be leveraged to take your scrum teams to the next level.

In this session, we will explore the importance of empiricism and how behavior can affect whether your Scrum implementation is mechanical or professional. 

Scrum is based on empirical process control where we are guided by our experiences. Built into the events of the framework, a Scrum team frequently inspects, adapts and is transparent in order to optimize product development. What are some positive and negative ways that empiricism is affected by our behavior?

The introduction of Scrum values into the Scrum framework tells us that culture and behavior is a recurring problem that we must tackle in order to optimize empiricism.