Agile 1's Game
Seb Rose, Cucumber
The agile manifesto lists some values. Agile methods often give you rules and guidelines. Understanding ‘why’ some recommendations are useful is often skipped. The “Agile 1’s game” simulates swarming, story decomposition and WIP limits to give teams a visceral understanding of why some counter-intuitive practices actually lead to more regular delivery of value for the customer.
Often called the ‘Kanban 1’s game’ I’ve found that this game is very useful for teams trying to get an understanding of basic agile practices, irrespective of which flavour of agile they are going to adopt. We’ll spend a lot of time in this session playing, which is fun, but there is a serious point too. And, by the end of the session, delegates will be in a position to run the game themselves.
Seb Rose has been aConsultant, coach, designer, analyst and developer for over 30 years.Seb has been involved in the full development lifecycle with experience that ranges from Architecture toSupport, from BASIC to Ruby. He’s a partner in Cucumber Limited, which helps teams adopt and refine their agile practices, with a particular focus on collaboration and automated testing. Regular speaker at conferences and occasional contributor to software journals. Contributing author to “97 Things Every Programmer Should Know” (O’Reilly) and lead author of “TheCucumber for Java Book” (Pragmatic Programmers). He blogs at cucumber.io and tweets as @sebrose.
