The document discusses integrating game mechanics into software development to enhance the agile process and make it more engaging. It proposes workshops that encourage participants to explore and customize game mechanics relevant to agile practices while reflecting on their potential impact. Additionally, it critiques traditional methods like waterfall, emphasizing the importance of adaptability and learning from experiences.

1. Software
Development
Game with Purpose

2. Software
Game
is a
Development
Shhhhh….
Don’t tell anyone OK?

3. We could have FUN
while we build something useful

7. Development is like exploration…
The game’s decisions are
made on imperfect information

9. Product Release
Developing
a
is like an RPG
Adventure
§ Goal to accomplish
(Biz Value to realize)
§ Party self-organizes
§ Gain tools & experience

10. Product
Development
is like an RPG
Campaign
§ Priorities from distant
netherworlds
§ Based on the needs
of the Imperium
(Business)
§ Experience carries
from one release to
the next
§ And each release is
continued learning

11. Let’s do some
Research
Experimentation
&

12. Exercise Time
• In breakout rooms, we will see what game mechanics you think
apply or can apply to some typical Agile development events and
practices; here’s a list of mechanics, but feel free to describe your
own (a bit longer than your handout)
– https://www.boardgamegeek.com/browse/boardgamemechanic
• Trello board breakout rooms
– https://trello.com/b/yEofXhSO/agc-agile-dev
• Try and describe the items in terms of game mechanics/ game play.
The handout is a helper, Video Game Mechanics, Role-Playing
Mechanics, or even making up a mechanic if it is clear to you is OK.
(I’ll show a stand-up as an example momentarily.) [8 min or return to
room early if you finish early.]
• Elect a spokesperson.

13. Debrief
Time to

14. SHU HA RI
Thinking in terms of game mechanics:
• Add mechanics for new circumstances
• Remove mechanics that reduce effectiveness
• Customize mechanics
• Gamify around mechanics

15. Exercise Time
• You will go back into your breakouts (this will take a little longer
since I’ll be placing you in the same groups)
• Use the Trello board breakout rooms of 5
– https://trello.com/b/yEofXhSO/agc-agile-dev
• Try and take 1-2 key mechanics and see how you might give a
reward via scoring to the item. Be sure to think of possible
detrimental side effects. Record this into the description of the card.
[5 min or return to room early if you finish early.]
• Elect a spokesperson.

16. Debrief
Time to

17. What Take Aways Do You Have?
• Take 1 min and write down something you are taking
away that you may try from this workshop?
• This could be –
– Specific mechanic to emphasize
– Scoring attached to a mechanic
– Changing out mechanics

18. So how does
‘Waterfall’
compare?

20. It’s always
sold as a
happy
project…
…with a
happy
team …

21. Look! Here’s
the happy
(a.k.a. critical)
path…
…planned
in one
direction…

22. Delivering in B I G
Batches…

23. What a
great
product…
Just stick to
the path!

24. And look,
there are
some
wondrous
shortcuts
we can take
early on…

25. What do
you mean I
can get
stuck here?
And here?
And here
also?

26. That’s not the
way Waterfall
was promised
to work!
You’re right!
It’s more like…

28. It gets
worse

29. A
can take you
from
to

30. That’s like…
You Failed Your Tests
“Looks like a design flaw”
“Are you sure you got
that requirement right?”

31. Management’s
reaction?
And

33. Feel Free to Reach Out!..
Paul Boos
paul.boos@excella.com
@paul_boos
703.307.4322
IT Executive Coach
Chair
Agile Coach Camp Initiative
Agile Coach Camp Worldwide
Member
Agile Coaching Initiative
Principle 12 Initiative
Games for Agility, Learning, &
Engagement (GALE-DC) Meet-up