1. Agile contracting games The rules of the game v2.1 – December 2011

2. Introduction Who are we Gert van de Krol Dick van der Sar 2

3. Introduction Workshop

4. Introduction Session structure 4

5. Baseline Statements 1. A project has a joint and shared objective, a game has an individual goal; 2. Rules may change during the game; 3. Everyone must know the contract; 4. Agile projects do not need a contract; 5. With Agile the workplace is detached from management. 5 Agree No opinionDisagree B B B B B F F F F F

6. IT Contract Agile Manifesto The ‘Agile manifesto’ Customer collaboration over contract negotiation. 6 What does this statement mean? No contract (negotiations)? Only contracts focused on collaboration with users?

7. IT Contract XP Bill of Rights Developer Bill of Rights 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. Customer Bill of Rights 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. 7

8. IT Contract Definition 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. IT: What kind of offerings? When is the delivery successful? How does a contract ensure the success? 8

9. IT Contract Offerings: sourcing levels Commitment / Time & material Agreement (posting). Project Agreement. Framework Agreement. Service Level Agreement (SLA) Sourcing levelOther namesDurationManage- ment Method / Way of working Hiring DetacheringTemporaryCustomer Co-sourcing Resource pools, availability and continuity guarantees LengthyCustomer Execution Fixed price, fixed date, Outtasking LengthySupplierCustomer Service Outsourcing, Near shore, Offshore. LengthySupplier 9

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

11. Game 1 Evaluation Observations : The rules of play. The goal of the game Translation into IT : The analogy with contracting. 11

12. Rules of play Example 12

13. Rules of play Structure 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 13

14. Rules of play Structure in the example Goal Scoring Rounds & Examples Preparation Materials & Roles Game end Rounds & Examples Rounds & Examples Context, Persons & Age 14

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

16. Game 2 Evaluation Observations : the rules of play. roles. Translation into IT : the analogy with contracting. 16

17. Agile contracting PRINCE2 and RUP 17

18. Agile contracting RUP-lifecycle 18

19. Agile contracting PRINCE2 and RUP 19

20. Game 3 Cooperation Available time: 10 min Roles: 4 players (builders, saboteurs) + 1 observer. The color of the highest card determines the role: Red : saboteur. Black: builder. (when both colors have the highest card : builder). Preparation: each player gets 4 cards in hand. one card facing up (start card), thee (end) cards facing down. pile of cards facing down Game end : time is up or all cards of the deck have been picked. Goal : Create a road of 5 cards width. Score builders win when a road is created. saboteurs win when no road is created. Assumptions: The players may not interact and discuss there roles. A saboteur must act carefully. Material: Stack of cards. Rule paper. 20

21. Game 3 Evaluation Observations : the rules of play. roles. Translation into IT : the analogy with contracting / project execution. the performance of the individual players. dividing the profit. 21

22. Agile contracting Definition of Success Hiring and co-sourcing: No difference between linear (waterfall) and Agile projects. Execution and Service: Linear (waterfall): success is the well defined completion of a stage in the project based on input from the previous step. Agile (RUP, SCRUM,..): Agile is about the team performance vs. contract is about the performance of a supplier as a part of the team. Can an execution or service level offer be combined with an Agile method? 22

23. 23 Project lifecycle Functioneal design Functioneal design TD Develop- ment Develop- ment Test Linear method Inception Elaboration Construction Transition Iterative method Requirements Test voor project voor project Initiatie- fase Initiatie- fase Laatste uitvoeringsfase Prioriterise & budget Prioriterise & budget Business case Initiatie Proposal Preparation Execution Handover Accep- tance Accep- tance Imple- mentation Imple- mentation Evaluation Discharge Proposal After care Agile contracting Project lifecycle Volgende uitvoeringsfase(n)

24. Summary The Agile IT Contract 1. Make the contract for each project member readable and available. 2. Handle the contract as a project deliverable. 1. Adjust the contract according to the phase and retrospective/evaluation of the project. 2. Add the contract to the CMDB / version management. 3. Use the structure for rules of games for contracts. Goal of the game Roles Preparation Rounds Game end Scoring 4. Decide in advance, how team reward is divided among team members (suppliers) when the team successfully delivers. 24

25. Baseline Statements 1. A project has a joint and shared objective, a game has an individual goal; 2. Rules may change during the game; 3. Everyone must know the contract; 4. Agile projects do not need a contract; 5. With Agile the workplace is detached from management. 25 Agree No opinionDisagree B B B B B F F F F F

26. Discussion