Evolving Agile Contracts through Validated Learning

378 views
287 views

Published on

This is an update to "Agile Contracting: The Good Parts" presented August 8 at Agile 2013 in Nashville, TN.


The contract is a useful, probably necessary, tool for defining a project undertaken by more than one party. While the contract has traditionally been seen as a tool to manage risk through control and enforcement, tying a project manager's time up in costly (wasteful?) contract negotiation, it should come to be seen as a tool to support collaboration and cooperation. The contract can define a container which holds the project and allows (if not promotes and encourages) the empirical, collaborative, adaptive, safe-to-fail and safe-to-succeed environment necessary for us to do great development work on a complex software system.

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

  • Be the first to like this

No Downloads
Views
Total views
378
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Evolving Agile Contracts through Validated Learning

  1. 1. A Scrum Master, an Entrepreneur and a Lawyer ... Nancy Van Schooenderwoert | Steve Holyer Evolving Agile Contracts Through Validated Learning © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  2. 2. A Scrum Master, an Entrepreneur and a Lawyer ... A Scrum Master, an Entrepreneur, and a Lawyer walk into a bar... © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  3. 3. What are you havin’, boys? © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  4. 4. I’d like a contract that promotes the spirit required for true Agility... © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  5. 5. ... collaborate with customers without company boundaries getting in the way. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  6. 6. I see that I’m going to be writing a lot of fine print! © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  7. 7. Who’s pickin’ up the tab? © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  8. 8. We get a lot of your type around here… We get a lot of your type, around here... © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  9. 9. Evolving Agile Contracts ThroughValidated Learning © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  10. 10. NancyVan Schooenderwoert - External Agile Coach (Bartender) Robert Feigin - Lawyer Steve Holyer - Scrum Master and David Campey - Entrepreneur © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Evolving Agile Contracts ThroughValidated Learning Friday, August 9, 13
  11. 11. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  12. 12. Our companies: © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  13. 13. 1. Contracting Landscape 2. Problem we are working on 3. Chartering - the other side © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  14. 14. 1. Contracting Landscape 2. Problem we are working on 3. Chartering - the other side© August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  15. 15. Risk models Peter Stevens, 10 Agile Contracts http://agilesoftwaredevelopment.com/blog/peterstev/10-agile-contracts © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  16. 16. CUSTOMER COLLABORATION CONTRACT NEGOTIATION Friday, August 9, 13
  17. 17. Friday, August 9, 13
  18. 18. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  19. 19. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  20. 20. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  21. 21. TheContract Developer Customer © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  22. 22. 3. Chartering - the other side 1. Contracting Landscape © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. 2. Problem we are working on Friday, August 9, 13
  23. 23. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  24. 24. 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 chart The present project is organised according to the diagram below. The roles are allocated as follows: 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 Assistant is also responsible for ensuring that deadlines are kept and coordinates all work © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  25. 25. 7.6.2 Domain model will be supplied upon completion. 8. Client Responsibilities 8.1 The Client agrees to provide the Developer with all information requested by the Developer in order for the Developer to fulfill its responsibilities as outlined on this agreement. 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 Owner 9.1 The Client will nominate a natural person to perform the role of Product Owner. 9.2 The Product Owner's 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 Sprint where Attendance can be physical or by telephone/VoIP/video call. 10. Warranties of Rights and Conflict of Interest 10.1 The Client warrants that it has rights and no conflict of interest in developing the Application. 10.2 The Software Developer warrants that it has relevant rights, licenses and no conflict of interest in developing the Application. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  26. 26. The present project is organised according to the diagram below§. The roles are allocated as follows: 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 Assistant is also responsible for ensuring that deadlines are kept and coordinates all work 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 right© August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  27. 27. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  28. 28. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  29. 29. 7.6.2 Domain model will be supplied upon completion. 8. Client Responsibilities 8.1 The Client agrees to provide the Developer with all information requested by the Developer in order for the Developer to fulfill its responsibilities as outlined on this agreement. 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 Owner 9.1 The Client will nominate a natural person to perform the role of Product Owner. 9.2 The Product Owner's 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 Sprint where Attendance can be physical or by telephone/VoIP/video call. 10. Warranties of Rights and Conflict of Interest 10.1 The Client warrants that it has rights and no conflict of interest in developing the Application. 10.2 The Software Developer warrants that it has relevant rights, licenses and no conflict of interest in developing the Application. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  30. 30. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  31. 31. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  32. 32. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  33. 33. 1. Contracting Landscape 2. Problem we are working on 3. Chartering - the other side © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  34. 34. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  35. 35. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  36. 36. Fabienne Steiner’s (BizDev/ Scrum Coach) Four Keys © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  37. 37. Chartering Activity © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  38. 38. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  39. 39. “... das ist völlig Quatsch!” © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  40. 40. Chartering Activity Guts © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  41. 41. Guts Chartering Activity Contract Specifics © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  42. 42. Guts Chartering Activity Contract Specifics Transcending the PO Role © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  43. 43. CHARTERING On-Boarding Get all members fully committed Discovery Product Process Team © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  44. 44. 1. Contracting Landscape 2. Problem we are working on 3. Chartering - the other side © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  45. 45. Individuals and interactions Working software Customer collaboration Responding to change over processes and tools comprehensive documentation contract negotiation following a plan © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  46. 46. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  47. 47. Contract Fluency ... Where are you? © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  48. 48. © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  49. 49. References: Web Resources Sutherland, Jeff; ”Agile Contracts: Money for Nothing and Your Change for Free” (accessed Aug 2, 2013): http://scrum.jeffsutherland.com/2008/10/agile-contracts- money-for-nothing-and.html Cockburn, Alistair; “Agile Contracts” (accessed Aug 2, 2013): http://alistair.cockburn.us/ Agile+contracts Stevens, Peter; “10 Agile Contracts” (accessed Aug 2, 2013): http:// agilesoftwaredevelopment.com/blog/peterstev/10-agile-contracts Larsen, Diana; Shore, James; “Your Path through Agile Fluency” (accessed Aug 2, 2013): http://agilefluency.com Books / Articles Opelt, Gloger, Pfarl, Mittermayr, "Agile Contracts: Creating and Managing Successful Projects with Scrum" Wiley, 2013 © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  50. 50. NancyVan Schooenderwoert | @vanschoo NancyV@leanagilepartners.com www.leanagilepartners.com Steve Holyer | @zurcherart coach@steveholyer.com www.steveholyer.com David Campey | @davidcampey campey@informationslogistics.co.za www.informationlogistics.co.za Robert Feigin rfeigin@hutchingsbarsamian.com © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13
  51. 51. A Scrum Master, an Entrepreneur and a Lawyer ... Nancy Van Schooenderwoert | Steve Holyer Evolving Agile Contracts Through Validated Learning © August 2013, N. Schoonderwoert, S. Holyer, D. Campey, B. Feigin.All Rights Reserved. Friday, August 9, 13

×