Please enable JavaScript.
Coggle requires JavaScript to display documents.
Digital, EV DEV
Minimum Usable SubseT;
incremental delivery, Tech…
Digital
Contract
Price and Payment
-
Time and materials - simple, straightforward and recommended. Progress measured in usable systems each iteration - highly transparent - termination possible after each iteration. Variations: capped per iteration / capped per project or release...
Fixed price per iteration (per unit of time). simple. predictable. requirements defined and agreed before the iteration.
Termination
Ability to stop further effort at the end of Feasibility/Foundations or at the end of any Evolutionary Development iteration.
Principles / Risk
Collaboration, transparency and trust "customer collaboration over contract negotiation"
Builds deployable (not partial) components iteratively - accepted and usable at each two-week iteration. Like trading up a model of a car every two weeks - reduces risk vs a sequential project with a big bang deployment
-
DOD - Definition of done, defined and evolved at each iteration. (e.g. Coded, integrated, tested, documented)
Acceptance
incremental and adaptively agreed upon for each iteration. Only the framework for acceptance must be contractually clear
Avoid
Deliverables detailed in statement of work or quality plan - avoid such regidity and focus on working software.
FPFS - Fixed Price Fixed Scope. Lose Lose. These appear to shift risk to the supplier but this is an illusion. customers often do not get what they need and suppliers can easily lose money. efforts by suppliers to deliver something within price/scope will often degrade the quality of their work - increasing tech debt / future cost. At worst, these are abused as part of a blame game to shift pain to the other party.
VPVS - Variable Price Variable Scope PROGRESSIVE contract
Master service agreement / umbrella framework defines the overarching relationship and pricing scheme per iteration, but does not define scope. Risk controlled because termination can occur at the end of any iteration.
ABC - Contracting for Agile: is it possible? Webinar with Steward James and Andrew Craddock and Richard Stephens.
We define means: dedicated team members and the compétences needed. the contractor engages to respec the agile Framework. The contract is renewed every 2 or 3 sprints. The PO decides if the job is to be continued or stoped.
Emily - we've done this for about a couple of years now, it's been reasonably successful - has needed some in depth agreement with our Procurement and Legal teams, but they're on board. Like Nick, the focus is on the outcome (what does success look like to the business). We've found it quite empowering to scrap things we said we'd do, because they no longer make any sense to do them, and re-shape deliverables with each sprint.
The two key parts of our standard agreement specify 1) how much work we're going to do and 2) more importantly, what is the outcome that the customer wants
Nick - how do you define the 'how much work'? Do you use velocity/effort points? Or finished products?
= Effort. As little emphasis on product as possible.
T&M: Shouldn't be concerned because customer has right to terminate if not satisfied, if not delivering usable working software. Good visibility of what's going on with iterative incremental delivery (vs waterfall with long development cycles).
We've developed a flexible contract. Standard company conditions, but an iterative contract that is reviewed with each sprint, and 're-signed' with agreed changes based on the evolving work.
CONTRACT EXAMPLES:
Practical Law (Agifall); LexisPSL (behind paywall); GDS DOS contract (sequential, iterative, drafting); Norwegian PS-2000 (need to pay for licence); Danish K03 Contract (sequential, iterative). AGILE BUSINESS CONSORTIUM = free DSDM template.
-
-
-
-
-