1 / 24

XP CONFERENCE 2001 THE CONTRACT

XP CONFERENCE 2001 THE CONTRACT. Frank Chan Partner Hesketh Henry.

esme
Download Presentation

XP CONFERENCE 2001 THE CONTRACT

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. XP CONFERENCE 2001THE CONTRACT Frank Chan Partner Hesketh Henry

  2. This powerpoint presentation was prepared by Frank Chan, Partner of Hesketh Henry, for theXP Conference 2001 9-10 October 2001.This presentation is an overview of the legal issues relevant to an XP contract.Frank is working with the New Zealand XP Users Group to develop an XP Contract. If you have any comments, questions or ideas please contactFrank Chan by email at:frank.chan@heskethhenry.co.nz

  3. User’s Expectations • What do I get? • When do I get it? • What will it cost?

  4. Developer’s Obligations • What do I do? • When must I do it? • What will I get paid?

  5. Common Contract Problems • Mismatch of expectations • Cost overruns • Wrong/defective delivery • Deadline not met

  6. Inherent Contract Problems • Capacity to perform • Financial integrity

  7. Competing Interests Certain vs Flexible scope Fixed vs Variable cost Fixed vs Managed timeframe

  8. XP is • A culture • A process • A contract ?

  9. Key XP features ? • Confidence in developer • Interactive capability • Discrete releases • Regular payments

  10. User has less risk • Sees work in progress • Small at risk component

  11. When is XP an option? • Project nature • Educated users • Symbiotic relationship

  12. But What About - • Programming “blocks”? • Unforeseen problems? • Quality?

  13. Is an XP contract • Open-ended? • Pay as you go (t & m)?

  14. Converting the 4 XP values into a contract • Communication • Simplicity • Feedback • Courage

  15. Communication • Availability • At the right level • Decision-making

  16. Simplicity • Project management • Processes • Decision-making

  17. Feedback • Regular communication • Constant flow • Action focused

  18. Courage • Flexibility vs certainty • Risk & return • Confidence & capability

  19. XP Contract Components • User stories • Prioritised • Agreed form

  20. Customer on site • Authoritive feedback • Regular meetings

  21. Timesheets at approved rates • Approval • Payment

  22. Regular & short releases • Customer’s acceptance • Developer’s role

  23. Termination at any time

More Related