A Scrum Master, an Entrepreneur and a             Lawyer ...
A Scrum Master, an Entrepreneur,Entrepreneur and a            A Scrum Master, an and a                           Lawyer .....
What are you havin’, boys?
I’d like a contract that promotes the    spirit required for true Agility...
... collaborate with customerswithout company boundaries getting              in the way.
I see that I’m going to be writing a          lot of fine print!
We get a lot of your type,around here...
Agile Contracting the     Good Parts
Agile Contracting the           Good PartsNancy Van Schooenderwoert - Bartender / CoachRobert Feigin - LawyerSteve Holyer ...
Our companies:
1. Contracting Landscape2. Problem we are working on3. Chartering - the other side
1. Contracting Landscape2. Problem we are working on3. Chartering - the other side
Risk modelsPeter Stevens, 10 Agile Contractshttp://agilesoftwaredevelopment.com/blog/peterstev/10-agile-contracts
Customer      The Contract                     Developer
1. Contracting Landscape2. Problem we are working on3. Chartering - the other side
User Story is considered finished once:• the implemented tests and/or features were deployed on the test and/or stage serve...
7.6.2 Domain model      will be supplied upon completion.8. Client Responsibilities8.1 The Client agrees to provide the De...
The present project is organised according to the diagram below§. The roles are allocated afollows:   Advisory group: The ...
7.6.2 Domain model      will be supplied upon completion.8. Client Responsibilities8.1 The Client agrees to provide the De...
1. Contracting Landscape 2. Problem we are working on3. Chartering - the other side
Fabienne Steiner’s (BizDev/ Scrum Coach) Four Keys
Chartering Activity
“... das ist völlig Quatsch!”
Chartering Activity Guts
Chartering ActivityGutsContract Specifics
Chartering ActivityGutsContract SpecificsTranscending thePO Role
CHARTERINGOn-Boarding Get all members fully committedDiscovery  Product  Process  Team
1. Contracting Landscape 2. Problem we are working on3. Chartering - the other side
overIndividuals and interactions          processes and toolsWorking software                      comprehensive documenta...
Contract Fluency ... Where are you?
Open Space - Chartering New Expeditions  Wiki: http://contracts.labs.ws/foswiki
Nancy Van Schooenderwoert | @vanschoo NancyV@leanagilepartners.com www.leanagilepartners.comSteve Holyer | @zurcherart  St...
Agile Contracting - The Good Parts
Agile Contracting - The Good Parts
Agile Contracting - The Good Parts
Agile Contracting - The Good Parts
Agile Contracting - The Good Parts
Agile Contracting - The Good Parts
Agile Contracting - The Good Parts
Agile Contracting - The Good Parts
Agile Contracting - The Good Parts
Agile Contracting - The Good Parts
Agile Contracting - The Good Parts
Agile Contracting - The Good Parts
Agile Contracting - The Good Parts
Upcoming SlideShare
Loading in …5
×

Agile Contracting - The Good Parts

2,654 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,654
On SlideShare
0
From Embeds
0
Number of Embeds
18
Actions
Shares
0
Downloads
40
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Agile Contracting - The Good Parts

    1. 1. A Scrum Master, an Entrepreneur and a Lawyer ...
    2. 2. A Scrum Master, an Entrepreneur,Entrepreneur and a A Scrum Master, an and a Lawyer ... Lawyer walk into a bar...
    3. 3. What are you havin’, boys?
    4. 4. I’d like a contract that promotes the spirit required for true Agility...
    5. 5. ... collaborate with customerswithout company boundaries getting in the way.
    6. 6. I see that I’m going to be writing a lot of fine print!
    7. 7. We get a lot of your type,around here...
    8. 8. Agile Contracting the Good Parts
    9. 9. Agile Contracting the Good PartsNancy Van Schooenderwoert - Bartender / CoachRobert Feigin - LawyerSteve Holyer - Scrum Masterand David Campey - Entrepreneur
    10. 10. Our companies:
    11. 11. 1. Contracting Landscape2. Problem we are working on3. Chartering - the other side
    12. 12. 1. Contracting Landscape2. Problem we are working on3. Chartering - the other side
    13. 13. Risk modelsPeter Stevens, 10 Agile Contractshttp://agilesoftwaredevelopment.com/blog/peterstev/10-agile-contracts
    14. 14. Customer The Contract Developer
    15. 15. 1. Contracting Landscape2. Problem we are working on3. Chartering - the other side
    16. 16. User Story is considered finished once:• the implemented tests and/or features were deployed on the test and/or stage server,•the technical documentation has been written, and•the Product Owner confirms that the test criteria have been met.Organisation chartThe present project is organised according to the diagram below. The roles are allocated asfollows: Advisory group: The advisory group decides the strategic direction that the project takes and verifies compliance with all contractually agreed arrangements. Product Owner: At the Customer end, the Product Owner is responsible for the commercial success of the project and is in charge of ensuring that the project remains within budget. The Product Owner sets the common goal based on the defined User Stories . The team then works towards meeting this goal. The Product Owner regularly decides on the priority that each product backlog item should take and, in doing so, defines the features that the development team will endeavor to implement in the subsequent Sprint cycle. The Product Owner, therefore, has full control over the implementation process and determines, within the set budget, the range of functions that the software will have. Product Owner Assistant: At the Liip end, the Product Owner Assistant actively helps the Product Owner. The Product Owner Assistant contributes to the development of the User Stories, ensures that the team implements the decisions made by the Product Owner and verifies compliance with the project specifications. The Product Owner
    17. 17. 7.6.2 Domain model will be supplied upon completion.8. Client Responsibilities8.1 The Client agrees to provide the Developer with all information requested by theDeveloper in order for the Developer to fulfill its responsibilities as outlined on thisagreement.8.2 The Client will nominate and make available a Product Owner as described below.8.3 The Client will make payment as per agreements below.9. Product Owner9.1 The Client will nominate a natural person to perform the role of Product Owner.9.2 The Product Owners responsibilities include: 9.2.1 Prioritizing the Product Backlog 9.2.2 Attendance at Scrum Meetings: Backlog Estimation, Sprint Planning 1 & 2, Sprint Review. 9.2.3 Attendance at Daily Standup 9.2.4 Participation as required in Definition of Done for Stories during Sprintwhere Attendance can be physical or by telephone/VoIP/video call.10. Warranties of Rights and Conflict of Interest10.1 The Client warrants that it has rights and no conflict of interest in developing theApplication.10.2 The Software Developer warrants that it has relevant rights, licenses and no conflict ofinterest in developing the Application.
    18. 18. The present project is organised according to the diagram below§. The roles are allocated afollows: Advisory group: The advisory group decides the strategic direction that the project takes and verifies compliance with all contractually agreed arrangements. Product Owner: At the Customer end, the Product Owner is responsible for the commercial success of the project and is in charge of ensuring that the project remains within budget. The Product Owner sets the common goal based on the defined User Stories . The team then works towards meeting this goal. The Product Owner regularly decides on the priority that each product backlog item should take and, in doing so, defines the features that the development team will endeavor to implement in the subsequent Sprint cycle. The Product Owner, therefore, has full control over the implementation process and determines, within the set budget, the range of functions tha the software will have. Product Owner Assistant: At the Liip end, the Product Owner Assistant actively helps the Product Owner. The Product Owner Assistant contributes to the development of the User Stories, ensures that the team implements the decisions made by the Product Owner and verifies compliance with the project specifications. The Product Owner Assistant is also responsible for ensuring that deadlines are kept and coordinates all wor carried out as part of the project with the Customer’s web host and design agency. Development team: The development team assesses the effort that each individual User Story entails. In the subsequent Sprint cycle, the team carries out the agreed tasks that can be feasibly achieved with the scheduled resources at its disposal. The team self organises to meet the agreed Sprint goals within a time box (the Sprint) and has the righ
    19. 19. 7.6.2 Domain model will be supplied upon completion.8. Client Responsibilities8.1 The Client agrees to provide the Developer with all information requested by theDeveloper in order for the Developer to fulfill its responsibilities as outlined on thisagreement.8.2 The Client will nominate and make available a Product Owner as described below.8.3 The Client will make payment as per agreements below.9. Product Owner9.1 The Client will nominate a natural person to perform the role of Product Owner.9.2 The Product Owners responsibilities include: 9.2.1 Prioritizing the Product Backlog 9.2.2 Attendance at Scrum Meetings: Backlog Estimation, Sprint Planning 1 & 2, Sprint Review. 9.2.3 Attendance at Daily Standup 9.2.4 Participation as required in Definition of Done for Stories during Sprintwhere Attendance can be physical or by telephone/VoIP/video call.10. Warranties of Rights and Conflict of Interest10.1 The Client warrants that it has rights and no conflict of interest in developing theApplication.10.2 The Software Developer warrants that it has relevant rights, licenses and no conflict ofinterest in developing the Application.
    20. 20. 1. Contracting Landscape 2. Problem we are working on3. Chartering - the other side
    21. 21. Fabienne Steiner’s (BizDev/ Scrum Coach) Four Keys
    22. 22. Chartering Activity
    23. 23. “... das ist völlig Quatsch!”
    24. 24. Chartering Activity Guts
    25. 25. Chartering ActivityGutsContract Specifics
    26. 26. Chartering ActivityGutsContract SpecificsTranscending thePO Role
    27. 27. CHARTERINGOn-Boarding Get all members fully committedDiscovery Product Process Team
    28. 28. 1. Contracting Landscape 2. Problem we are working on3. Chartering - the other side
    29. 29. overIndividuals and interactions processes and toolsWorking software comprehensive documentationCustomer collaboration contract negotiationResponding to change following a plan
    30. 30. Contract Fluency ... Where are you?
    31. 31. Open Space - Chartering New Expeditions Wiki: http://contracts.labs.ws/foswiki
    32. 32. Nancy Van Schooenderwoert | @vanschoo NancyV@leanagilepartners.com www.leanagilepartners.comSteve Holyer | @zurcherart Steve.Holyer@liip.ch www.liip.chDavid Campey | @davidcampey campey@informationslogistics.co.za www.informationlogistics.co.zawww.agile42.com

    ×