During one of nlScrummeetups I heard about The Retrospective Smells Cards. A tool for Scrum masters, agile coaches, and anyone who facilitates agile retrospectives to recognize smells and solve problems or mitigate the impact.
Good user stories follow Bill Wake’s INVEST model. They’re Independent, Negotiable, Valuable, Estimable, Small, and Testable. The small requirement drives us to split large stories. But the stories after splitting still have to follow the model.
Value Stream Mapping (VSM) is a -very- useful tool to gain insight in the workflow of a process and can be used to identify both Value Adding Activities and Non Value Adding Activities in a process stream while providing handles for optimizing the process chain. Read this blog-post on how to create a VSM: https://xebia.com/blog/how-to-create-a-value-stream-map/
Now that many organisations are scaling their agile process one way or the other, Product Owners are faced with the challenge of scaling their already busy role. Kai Stevens created The agile product management @scale game that helps Product Owners identify how to focus on the essential product management activities while making sure that other product management activities will be handed over to other members of their team.
Liberating Structures are easy-to-learn, easy-to-facilitate techniques that build real engagement and involvement in groups of any size. Christiaan Verwijs wrote a nice piece about having a good invitation is crucial for running a Liberating Structure.
To demonstrate the power of time-box or Sprint that makes the heartbeat of an agile framework like Scrum.
Type: Team Game
Time Needed: 45 minutes
Number of people per team: 6
Used Printer Paper 50 per team
One flip chart and a marker to keep score
The goal of the game:
The goal of the game is for each team to create as much high quality
tested planes that can fly a distance of at least 30 meters . The world
record holder last checked in June 2016 was somewhere in Germany
Each iteration last 9 minutes.
3 minutes for planning,
3 minutes of actual build ( test included) time,
3 minutes for review/retrospective –
Rules for playing the game:
Build as many paper planes as you can in a 3-minute time box.
One player can only do one fold at a time. That rules stays true for all three time-boxes.
The planes should be built
and tested in the 3-minute increment
Only planes that cross 30 meters will be counted
Each team should give a count of how many planes they are going to build before the time-box starts.
Subtract the final count of planes that actually flew from the
planes that were built but were not tested or completed. Eg: Team A
said they will make 4 planes, 7 planes flew all the way but 5 were WIP (
work in progress). Subtract WIP so the actual is 7-5 =2
The team has to come up with one idea of improvement at the retrospective. Have one member in the team be the counter.
The front of the plane should be blunt to avoid injury to the team members.
You cannot crush the plane into a ball and throw.
Please recycle the paper once done
Debrief: ( pick any two )
Each table talks about what made them improve over the three iterations
Talk about what would have happened if the time box was not there
Talk about how waterfall may be different from this.
Talk about who made the final design decisions in the team.
Talk about any wastes they removed from the system that helped them get better.
Original Creator: Not me. I am still trying to find out. I learned it from another trainer.
There are many variations of this game. This is one way I use it in my workshops