Agile Ball Point Game - kimschles/schlesinger-knowledge GitHub Wiki

From Kyle Coberly

Everyone is part of one big team.
Each ball must have air-time.
Each ball must be touched at least once by every team member.
Balls cannot be passed to your direct neighbour to your immediate left or right.
Each ball must return to the same person who introduced it into the system.
There are a total of five iterations.

Point out that they wouldn't have done as well if you'd given them all the planning time up front and only one iteration
Note that processes have a natural velocity, and you can't beat that philosophy by working harder, you actually need to change the process
Team ownership of the goal is important- if you had just given everyone what their final roles were and everyone just did their jobs, no one would be high-fiving at the end
Face to face communication is higher resolution than anything else
Even without formal leadership roles, people figure out how to work together just fine
Point out the importance of pull systems- if the next person isn't ready for the ball, throwing it to them anyway just jams up the system

Have students go through the manifesto and try to identify the opposite of the values and principles
What would it look like if we valued processes and tools over people and interactions? If the most important thing weren't satisfying our customers through continuous delivery of valuable software, what else could be the most important thing?