Stevie borne tc scrum day 2015

Agile Contracts:We Can Work It Out

Scrum Day Twin CitiesSeptember 22, 2015

Stevie Borne, CSPCertified Scrum Professional &

Agile Transformation Coachhttp://collaborativeleadershipteam.com

@CoLeadTeam

Stevie BorneCertified Scrum Professional (CSP)

• 15+ years Information Technology withtraditional SDLC and Scrum/Agile

• Passionate about coaching teams to thenext level using a Strengths-basedapproach

• Experienced Product Owner, ScrumMaster, Agile Transformation Coach,Project Manager, Software Developer

• Based in Eagan, MN

2Copyright 2015 Collaborative Leadership Team

Agile Manifesto

Agile Software Development Manifesto

We are uncovering better ways of developing software by doing it and helpingothers do it.

Through this work we have come to value

Individuals and interactions over processes and toolsWorking software over comprehensive documentation

Customer collaboration over contract negotiationResponding to change over following a plan

That is, while there is value in the items on the right,we value the items on the leftmore.

http://agilemanifesto.org


Exercise

• Find 3 other people and form a group• Discuss the following questions

– What comes to mind when you hear “CustomerCollaboration over Contract Negotiation”?

– What kinds of Contracts get negotiated in yourorganization?

• Be prepared to share with the group

Time Box:5 Min.


Traditional Approach

Source: Dynamic System Development Method (DSDM or RAD)


Traditional Contracts

• Created to address any potential risk to clients,known and unknown

• Often based in fear, assuming long delay beforedelivery

• Create false sense of security that everything iswell understood and defined

Copyright 2015 Collaborative Leadership Team6

Traditional Contract Examples

• Business Cases• Requirements Documents• Others….


Changing Perspective

Source: Dynamic System Development Method (DSDM or RAD)


Agile Contracts

• Start with Time and Money• Negotiate features• Reduces risk through frequent

delivery of “done” slices


Agile Contracts

• What problem needs to be solved?• What market need is being fulfilled?• Who is the Customer(s)?


Hearing From the Customer

• Pilot groups• Usability studies• Beta releases• Customer service calls• Sales visits or calls• Sprint Reviews


The Product Owner as the Customer

• Communicates what the Customer wants• Collaborates with the Team, Stakeholders, and the

Customer• Converses in terms of Definition of Done and

Acceptance Criteria


User Stories as Contracts

• Card• Conversation• Confirmation


Exercise

• What types of customer collaboration do you findmost challenging in your organization?

• Who are the customers that are being impactedmost?

• What can be done to improve theseinteractions?

Time Box:5 Min.


Beyond Software ??


Class Discussion

• What are non-software situations in which yousee this Agile value applicable?– Customer collaboration over contract negotiation

• In what ways?


Summary

• Traditional contracts often based in fear withfalse sense of security

• Agile contracts begin with time and money• Know the customer• Agile contracts reduce risk• “Customer Collaboration over Contract

Negotiation” can go beyond software


Questions ??


Wrapping Up

THANK YOU!Please stay in touch!

Stevie Borne, [email protected]

http://collaborativeleadershipteam.com/
