One of the simplest ways for our team to change up how they work is to experiment. This will most likely come from a team improvement action created at the Sprint Retrospective, or from a suggestion made by a team member at a Daily Scrum. Either way, a champion from within the team will usually come forward to run the experiment and present their idea for change. 

One easy way to fit this into our team's everyday flow is to ask the champion to select a candidate story that is well suited to implementing this change. For example, if the team has chosen to implement Behavior-Driven Development (BDD), then the BDD champion(s) would work with the rest of us to select a candidate story. When the story is pulled into the to-do column, the champion, with assistance if necessary, would work this story to completion using BDD. Estimate the story bearing in mind that the BDD framework will need to be set up.

Before working on the candidate story, the team should work together to set up the experiment with a hypothesis. We described a hypothesis template in the Hypothesis-Driven Development (HDD) section in Chapter 9, Seeking Value – How to Deliver Better Software Sooner.

Measuring the experiment's success is key to whether the team will carry the improvement forward into their everyday work, or at the very least expand it into other areas to see if it works in the broader setting.