agile contracting games the rules of the game n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Agile contracting games The rules of the game PowerPoint Presentation
Download Presentation
Agile contracting games The rules of the game

Loading in 2 Seconds...

play fullscreen
1 / 26

Agile contracting games The rules of the game - PowerPoint PPT Presentation


  • 79 Views
  • Uploaded on

Agile contracting games The rules of the game. v2.1 – December 2011. Introduction Who are we. Gert van de Krol. Dick van der Sar. Introduction Workshop. Introduction Session structure. Baseline Statements. Agree. Disagree. No opinion.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Agile contracting games The rules of the game' - ros


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
introduction who are we
IntroductionWho are we

Gert van de Krol

Dick van der Sar

baseline statements
BaselineStatements

Agree

Disagree

No opinion

  • A project has a joint and shared objective, a game has an individualgoal;
  • Rules may change during the game;
  • Everyone must know the contract;
  • Agile projects do not need a contract;
  • With Agile the workplace is detachedfrom management.

B

F

B

F

B

F

B

F

B

F

it contract agile manifesto
IT ContractAgile Manifesto

The ‘Agile manifesto’

Customer collaboration over contract negotiation.

  • What does this statement mean?
  • No contract (negotiations)?
  • Only contracts focused on collaboration with users?
it contract xp bill of rights
IT ContractXP 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.
it contract definition
IT ContractDefinition

General:

  • A contract is an agreement between two or more parties which can be legallyenforced.
  • 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?
it contract offerings sourcing levels
IT ContractOfferings: sourcing levels
  • Commitment / Time & material Agreement (posting).
  • Project Agreement.
  • Framework Agreement.
  • Service Level Agreement (SLA)
game 1 playing the game
Game 1Playing 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
game 1 evaluation
Game 1Evaluation
  • Observations:
    • The rules of play.
    • The goal of the game
  • Translation into IT:
    • The analogy with contracting.
rules of play structure
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
rules of play structure in the example
Rules of playStructure in the example

Rounds &

Examples

Game end

Context, Persons & Age

Scoring

Materials & Roles

Goal

Preparation

Rounds & Examples

game 2 changing the rules
Game 2Changing 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.
game 2 evaluation
Game 2Evaluation
  • Observations:
    • the rules of play.
    • roles.
  • Translation into IT:
    • the analogy with contracting.
game 3 cooperation
Game 3Cooperation
  • 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 cardsfacing 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.
game 3 evaluation
Game 3Evaluation
  • Observations:
    • the rules of play.
    • roles.
  • Translation into IT:
    • the analogy with contracting / project execution.
    • the performance of the individual players.
    • dividing the profit.
agile contracting definition of success
Agile contractingDefinition 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 teamperformance 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?

agile contracting project lifecycle
Agile contractingProject lifecycle

Project lifecycle

Prioriterise &

budget

Business case

Proposal

Initiatie

Proposal

Preparation

Proposal

Execution

Handover

Accep-

tance

Imple-

mentation

After care

Discharge

Evaluation

voor

project

Initiatie-

fase

Volgende uitvoeringsfase(n)

Laatste uitvoeringsfase

Functioneal

design

TD

Develop-

ment

Test

Test

Requirements

Linear method

Iterative method

Inception

Elaboration

Construction

Transition

E1

E2

C1

C2

C3

C4

T1

T1

summary the agile it contract
SummaryThe Agile IT Contract
  • Make the contract for each project member readableand available.
  • Handle the contract as a projectdeliverable.
    • Adjust the contract according to the phase and retrospective/evaluation of the project.
    • Add the contract to the CMDB / version management.
  • Use the structure for rules of games for contracts.
    • Goal of the game
    • Roles
    • Preparation
    • Rounds
    • Game end
    • Scoring
  • Decide in advance, how team reward is divided among team members (suppliers) when the team successfully delivers.
baseline statements1
BaselineStatements

Agree

Disagree

No opinion

  • A project has a joint and shared objective, a game has an individualgoal;
  • Rules may change during the game;
  • Everyone must know the contract;
  • Agile projects do not need a contract;
  • With Agile the workplace is detachedfrom management.

B

F

B

F

B

F

B

F

B

F