Agile Contracts
Upcoming SlideShare
Loading in...5
×
 

Agile Contracts

on

  • 4,788 views

Presentation given at Turku Agile Day 2013.

Presentation given at Turku Agile Day 2013.

Statistics

Views

Total Views
4,788
Views on SlideShare
4,617
Embed Views
171

Actions

Likes
11
Downloads
38
Comments
5

2 Embeds 171

https://twitter.com 170
http://blogs.sourceallies.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

15 of 5 Post a comment

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Agile Contracts Agile Contracts Presentation Transcript

    • Agile ContractsLL.M. Juha IlolaTurku Agile Day27.2.2013Wednesday, May 15, 13
    • © Copyright Reaktor 2013legal guy @ Reaktorpreviously @ major law firm, Sulakedoing legal IT stuff since 2001Wednesday, May 15, 13
    • © Copyright Reaktor 2013Agenda1.Contracts and Lawyers2.Pitfalls of Waterfall3.Agile ContractsWednesday, May 15, 13
    • © Copyright Reaktor 20131. Contracts and LawyersWednesday, May 15, 13
    • © Copyright Reaktor 2013people really do hatelawyers.Wednesday, May 15, 13
    • © Copyright Reaktor 2013lawyerunnecessary complexityWednesday, May 15, 13
    • © Copyright Reaktor 2013drafting contracts is similarto writing code.Wednesday, May 15, 13
    • © Copyright Reaktor 2013a beautiful contract:a contract thatprovides the simplestpossible solution to enablethe purpose of the contract.Wednesday, May 15, 13
    • © Copyright Reaktor 2013negotiation of collaborativecontracts should not beapproached as a zero-sumgame.Wednesday, May 15, 13
    • © Copyright Reaktor 2013optimize contracts forsuccessful outcome, not forthe (imaginary) interests ofone party.Wednesday, May 15, 13
    • © Copyright Reaktor 2013current economic climatedoes not favor beautifulcontracts.nevertheless, such beauty isworth fighting for.Wednesday, May 15, 13
    • © Copyright Reaktor 20132. Pitfalls of WaterfallWednesday, May 15, 13
    • © Copyright Reaktor 2013waterfall contract=fixed price + fixed scopeWednesday, May 15, 13
    • © Copyright Reaktor 2013“the Supplier will deliverto the Customer thesoftware described inAnnex 1 for EUR [price] by[deadline].”Wednesday, May 15, 13
    • assumptions inthe contract dicatate whatwill be done, not real(discovered) needs.Wednesday, May 15, 13
    • © Copyright Reaktor 2013Change Managementthe Supplier will allowchange only if there isenough money on thetable.Wednesday, May 15, 13
    • © Copyright Reaktor 2013Fixed priceencourages theSupplier to dominimum atmaximum price.Wednesday, May 15, 13
    • © Copyright Reaktor 2013The contract gives theCustomer illusion ofcontrol, but in factthe Supplier operatesas a black box andhas no incentives fortransparency.Wednesday, May 15, 13
    • © Copyright Reaktor 20133. Agile ContractsWednesday, May 15, 13
    • © Copyright Reaktor 2013Risks of a software project are bestaddressed by using agile methods.Not with contract.Agile contract should make it possibleto capitalize on the ability of agilemethods to provide the Customer withbest value for a given budget.Wednesday, May 15, 13
    • © Copyright Reaktor 2013EmpiricSpecifiedWednesday, May 15, 13
    • © Copyright Reaktor 2013BacklogSpecified in detailRecognized, requiredfunctionalitiesRelease 1Fuzzy ideasPriorityWednesday, May 15, 13
    • © Copyright Reaktor 2013the object of an agilecontract should be theperformance of service(as opposed to delivery ofspecified results).Wednesday, May 15, 13
    • © Copyright Reaktor 2013team members subjectto approval of theCustomer.the Customer has theright require thechange of a teammember at any time,for any reason.Wednesday, May 15, 13
    • © Copyright Reaktor 2013contents of theservices (i.e. backlog)are agreed inaccordance with theagile method.no separate changemanagement isnecessary.Wednesday, May 15, 13
    • © Copyright Reaktor 2013charged on time &material basis on thebasis of realizedhours / days.set max budget?charges are not tiedto the approval of theresults.Wednesday, May 15, 13
    • © Copyright Reaktor 2013alternatively targetprice can be used.target price is notideal, as it requiresscope and changemanagement.saved or overrunbudget should bedivided 50/50.Wednesday, May 15, 13
    • © Copyright Reaktor 2013Reaktor’s satisfactionguarantee:if the Customer feels thatReaktor has not performedwith satisfactory level, theymay notify Reaktor andreceive discount of chargesrelating to last sprint - noquestions asked.Wednesday, May 15, 13
    • © Copyright Reaktor 2013indefinite termcontract with2 - 4 weeks’ noticeperiod.trial period at thebeginning of thecontract?Wednesday, May 15, 13
    • © Copyright Reaktor 2013the Customer shouldreceive all rights orunlimited license tothe results of theservices.Wednesday, May 15, 13
    • © Copyright Reaktor 2013Thanks!... remember to further the beauty ofsimplicity when drafting contracts!Wednesday, May 15, 13