27
“Done” Are We There Yet? Paul Rayner

"Done" - Are We There Yet?

Embed Size (px)

DESCRIPTION

One of the core values expressed in the agile manifesto is “working software over comprehensive documentation” because working software is what delivers value to our customers. Agile development requires a sofware development team have working software ready to deploy at the end of each iteration; but accomplishing this can be harder than it seems, especially when first starting with agile. In this highly interactive session you will understand how a team definition of “Done” is necessary to making agile delivery possible, and what you can do to make it happen while avoiding the pitfalls.

Citation preview

Page 1: "Done" - Are We There Yet?

“Done”Are We There Yet?

Paul Rayner

Page 2: "Done" - Are We There Yet?

Write them down on a sticky note…

Questions?

Page 3: "Done" - Are We There Yet?

• Individuals and interactions

– over processes and tools

• Working software

– over comprehensive documentation

• Customer collaboration

– over contract negotiation

• Responding to change

– over following a plan

Agile Manifesto

Page 4: "Done" - Are We There Yet?

• Individuals and interactions

– over processes and tools

• Working software

– over comprehensive documentation

• Customer collaboration

– over contract negotiation

• Responding to change

– over following a plan

Agile Manifesto

Page 5: "Done" - Are We There Yet?

• Highest priority: satisfy the customer through early and continuous delivery of valuable software.

• Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

• Working software is the primary measure of progress.

Agile Principles

Page 6: "Done" - Are We There Yet?

Definition of “Done”

Roleplay!

Page 7: "Done" - Are We There Yet?

Definition of “Done”

Why?

Page 8: "Done" - Are We There Yet?

An Agile Framework: Scrum

Page 9: "Done" - Are We There Yet?
Page 10: "Done" - Are We There Yet?
Page 11: "Done" - Are We There Yet?
Page 12: "Done" - Are We There Yet?
Page 13: "Done" - Are We There Yet?
Page 14: "Done" - Are We There Yet?
Page 15: "Done" - Are We There Yet?

Definition of “Done”

Group Exercise

Page 16: "Done" - Are We There Yet?

Brainstorming:

What do we need to do, as ateam, to ship software to ourcustomers/stakeholders?

Page 17: "Done" - Are We There Yet?
Page 18: "Done" - Are We There Yet?

Categorization:

How should we group theseactivities/artifacts?

Page 19: "Done" - Are We There Yet?

Categorization:

How should we group theseactivities/artifacts?

Focus on customer value

Page 20: "Done" - Are We There Yet?

Sorting & Consolidation:

Where are the duplicates?

Page 21: "Done" - Are We There Yet?

Sorting & Consolidation:

Where are the duplicates?What % is writing code?

Page 22: "Done" - Are We There Yet?

Non-Iteration Artifacts:

Which of these things can notbe done every iteration? Why?

Page 23: "Done" - Are We There Yet?

Agree => Iterate

Gain consensus, review regularly…and refine

Page 24: "Done" - Are We There Yet?
Page 25: "Done" - Are We There Yet?

Review

Page 26: "Done" - Are We There Yet?

Resources

http://delicious.com/virtualgenius/Done

Note: Much of the materials for the exercises inthis session can be found in the “Done ListCreation Exercise” by Mitch Lacey and“Building a Definition of Done” by Chris Sterling

Page 27: "Done" - Are We There Yet?

Paul [email protected]

303.374.4370@virtualgenius (Twitter)

http://virtualgenius.spaces.live.com

Agility. Craft. Architecture.