In this workshop we play card games to investigate the topic of Agile contracts. How we can improve the performance of Agile teams looking at the organization around them and the contracts for the projects they work on. For this we will compare rules of play for games with contracts. If things go wrong: no matter what they tell you, it is a people problem. This means that contracts don't solve problems but they have influence. Using three card games we create awareness of this infuence and we offer a platform to discuss how contracts can stimulate an Agile way of working. Take these games to your team/managers/organization to let them experience what you already feel to be true. Agile works!

1. Agile Contracting Games
Experience What It Takes to Build a Cooperative Environment
v2.0 – December 2011

2. Introduction 2
Who are we
Wing Yu Chong Remi-Armand Collaris
Product Manager at ABZ Agile Facilitator at Ordina

3. Introduction
Workshop

4. Introduction 4
Schedule
Introduction
Survey
Let’s Play
Game 1
Evaluation
Rules of Play
Game 2
Evaluation
Rules of Play versus Contracts
What’s at Stake?
Game 3
Evaluation
Summary & Conclusions

5. Introduction 5
Definition of a Contract
General:
• A contract is an agreement between two or more parties which can be legally
enforced.
• Contract implies an offer and an acceptance of that offer.
• Offer: delivering a product or service.
• Acceptance: rewarding the successful delivery.

6. Introduction 6
Agile Manifesto on Contracts
We have come to value
…
Customer collaboration over contract negotiation
…
What does this statement mean?
• No contract (negotiations)?
• Focus contract on collaboration?

7. Introduction 7
What Comes Into Play
What is the goal of playing a game?
• Winning
• Team play
• Improve your skills (Learning)
• Satisfaction
• …
What emotions come into play?
• Motivation
• Creativity
• Hope
• Disappointment
• …

8. Let’s Play!

9. Let’s Play 9
Game 1: Playing the Game
• Number of players: 2 + observers. Goal:
• Available time: 2 min 30
to win!
Assumptions:
• Each participant knows how to play
cards.
• The players can interact and discuss
Material:
• Two stacks of cards

10. Let’s Play 10
Evaluation
• Observations:
• The rules of play.
• The goal of the game
• What if € 1000.- were at stake?
• Put experience into practice

11. Rules of Play

12. Rules of Play 12
Game 2: The Rule Manager
• Available time: 5 min Goal:
• Roles: n players + 1 rule manager + 1
observer. To win a game of ‘Jacks’ (pesten)!
• Preparation:
• each player gets 5 cards.
• stack of cards face down with one card Assumptions:
facing up at the side
• Each participant knows how to play
• Rounds: cards.
• Player 1 plays a card.
• If rule is applicable the rule manager • The players can interact and discuss.
explains the rule. • The rules have been described and
• The rule is executed handed over to the rule manager.
• Player 2 plays a card.
• etc.
• Game end and score: Material:
• The first player who has played all his or
her cards wins.
• Stack of cards.
• Rule paper.

13. Rules of Play 13
Game 2: Evaluation
• Observations:
• The Rules of Play
• Roles
• Strategy
• Changing Rules
• Put experience into practice

14. Rules of Play 14
Structuring Rules of Play
• Context
• number of persons
• duration of the game
• ages of participants
• Goal of the game
• Materials
• Roles
• Preparation
• Rounds
• steps
• situations
• examples
• exceptions
• Game end
• Scoring

15. Rules of Play 15
Simple ‘Contracts’?
Game end
Context, Persons & Age
Materials & Roles
Rounds & Scoring
Goal Examples
Preparation
Rounds & Examples

16. What’s at Stake?

17. What’s at Stake? 17
Game 3: Saboteur
Available time: 10 min Goal:
Roles: 4 - 6 players (builders, saboteurs)
+ 1 observer.
Create a road spanning 5 lanes.
Score
Preparation: • builders win when a road is created.
• Each player gets 4 cards. • saboteurs win when no road is created.
• Prepare construction site
• Put down a closed deck of cards
Assumptions:
and have a discard pile • The players may not discuss their roles.
Game end : • As a saboteur it is wise to not show your
intent to early.
• Time is up
or Material:
• All cards have been played. • Deck of cards.
• Rule paper.

18. What’s at Stake? 18
Game 3: Saboteur – Building a Road
Start 1 2 3 4 5 End
Different color
Rank difference <= 2 stack
9
♥
discard
6 7 Same color 10 pile
♠ ♠ Rank difference <= 2 ♣

19. What’s at Stake? 19
Game 3: Saboteur - Examples
Start 1 2 3 4 5 End
9 8 6
♥ ♥ ♥
6
♠
7
♠
4
♣
5
♣
3
♣ 
10
♣
89
♦♦

8 5 3
♣ ♦ ♦

4 5 9
♠ ♠ ♣

20. What’s at Stake? 20
Game 3: Saboteur - Roles
4
♣
Builder Saboteur
4
♣
Builder

21. What’s at Stake? 21
Game 3: Saboteur – Rounds
• Take turns counter-clockwise
• Play a card or put a card on the discard pile
2 •
- 10 Connect to the road. Card must match all adjacent cards.
♦ ♦
• Block a player from building road.
When a player is blocked, he or she may not build the road .
He or she can still do all other actions.
• Unblock a player.
• Destroy a card in the road (not being a start or end card).
• Inspect an end card (secretly, saboteurs are watching!).
• Pick a card of the deck if possible (you then again have 4 cards)

22. What’s at Stake? 22
Evaluation
• Observations:
• Goal
• Roles
• Feelings
• Put experience into practice

23. Summary 23
Contract and Agile Way of Working
1. Provide a clear goal and working arrangements.
2. Work out a clear payment model in advance.
3. Share and discuss the goal and working arrangements.
4. Work as a team and switch roles as needed.
5. Adapt the contract as needed.
6. Less is more.
7. Be explicit about conflicting interests.
8. Regularly demo a usable part of the solution.

24. More info:
www.scrumup.com/agilecontractinggame

25. Rules of Play 25
Game 2: The Rule Manager’s Rule Sheet
Basic rules (explained at start):
Suits
1. Toss a card with similar suits (symbol) or equal
rank (value).
2. If no options: pick a card from the deck.
3. The card for changing suits can be played always.
Advanced rules (only explained when applicable):
• number of cards at hand > 3: • number of cards at hand <= 3:
• 2: pick 2 of the deck • 2: pick 2 of the deck
• 3: pick 1 of the deck • 5, 9, 10: once more
• 7: skip a turn • 6: skip a turn
• 9: once more • Queen: change the suit
• Jack: change the suit • Joker: pick 2 of the deck.
• Ace: change the direction • Ace: exchange all your cards with another
• Joker: pick 5. player.
• Spades: suit is changed to hearts.
• Jack, Queen, King: raises the joker.

26. Agile Manifesto

27. Agile Contracting 27
Obligations versus Rights
XP Bill of Rights
Customer Bill of Rights (Client)
• You have the right to an overall plan, to know what can be accomplished
when and at what cost.
• You have the right to get the greatest possible value out of every programming week.
• You have the right to see progress in a running system proven to work by passing repeatable tests that you specify.
• You have the right to change your mind, to substitute functionality, and to change priorities without paying exorbitant costs.
• You have the right to be informed of schedule changes in time to choose how to reduce the scope to restore the original date. You can cancel the
project at any time and be left with a useful working system reflecting the investment to date.
Developer Bill of Rights (Contractor)
• You have the right to know what is needed with clear declarations of priority.
• You have the right to produce quality work at all times.
• You have the right to ask for and receive help from peers, superiors, and customers.
• You have the right to make and update your own estimates.
• You have the right to accept responsibilities instead of having them assigned to you.