Agile Contracts for Software Consultants

You’re ready to go with all the best Agile practices: you’ll develop incrementally and iteratively, you’ll have sprints and retrospectives, and you can’t wait to tell your clients about your velocity and show them your burndown charts. But all of your prospective clients are telling you they want firm quotes, and contracts with detailed specifications and delivery dates. Clients almost always start with a preference for these types of traditional contracts. Such contracts provide them with a sense of security and confidence that they will get what they want.

How do you convince them a traditional contract is actually riskier than they think, and persuade them to instead sign an Agile (time and materials) contract? This is the most significant challenge facing consultants who want to follow Agile practices. In this talk we’ll discuss:

  • The specifics of the language in a contract that distinguishes an Agile contract from a traditional contract. This includes important clauses to protect both the consultant and the client.
  • The persuasion and negotiation process for getting your prospective client to sign an Agile contract. We’ll discuss real-life situations from our experience at PromptWorks
  • Signing the contract is just the first step – you and your client must then work together to deliver a successful project. We’ll discuss what do if things go wrong, to get a struggling Agile consulting project back on track and avoid costly legal difficulties.

Michael’s talk is now available on the Chariot Solutions site.

Location: Salon A Date: April 8, 2015 Time: 10:15 am - 11:15 am Michael Toppa Michael Toppa