The Five Dysfunctions of an Agile Contract

14 minutes, 6 seconds


Right click “Save as…”

The traditional approach is to create a project estimate by an architect, which is used to negotiate a contract with the customer. Then a team of people not involved in the original estimate starts the actual work while the PM has to make sure there are no deviations from the plan. Scrum, on the other hand:

  • Creates (reasonably) fixed teams to establish predictability in estimating,
  • Adopts a Money for Nothing and Changes for Free type of commercial approach,
  • Deals with emergent vs existing architecture
  • Deals with risk of ending in the Avalanche anti pattern with enterprise level scrum
  • Develops a strategy when to do scrum and not to scrum

This session looks at how to create usable contracts that can support this flexibility.

Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.