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.

1. “Done”
Are We There Yet?
Paul Rayner

2. Questions?
Write them down on a
sticky note…

3. Agile Manifesto
• Individuals and interactions
– over processes and tools
• Working software
– over comprehensive documentation
• Customer collaboration
– over contract negotiation
• Responding to change
– over following a plan

4. Agile Manifesto
• Individuals and interactions
– over processes and tools
• Working software
– over comprehensive documentation
• Customer collaboration
– over contract negotiation
• Responding to change
– over following a plan

5. Agile Principles
• 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.

6. Definition of “Done”
Roleplay!

7. Definition of “Done”
Why?

8. An Agile Framework:
Scrum

15. Definition of “Done”
Group Exercise

16. Brainstorming:
What do we need to do, as a
team, to ship software to our
customers/stakeholders?

18. Categorization:
How should we group these
activities/artifacts?

19. Categorization:
How should we group these
activities/artifacts?
Focus on customer value

20. Sorting & Consolidation:
Where are the duplicates?

21. Sorting & Consolidation:
Where are the duplicates?
What % is writing code?

22. Non-Iteration Artifacts:
Which of these things can not
be done every iteration? Why?

23. Agree => Iterate
Gain consensus, review
regularly…and refine

25. Review

26. Resources
Note: Much of the materials for the exercises in
this session can be found in the “Done List
Creation Exercise” by Mitch Lacey and
“Building a Definition of Done” by Chris Sterling
http://delicious.com/virtualgenius/Done

27. Agility. Craft. Architecture.
Paul Rayner
paul@virtual-genius.com
303.374.4370
@virtualgenius (Twitter)
http://virtualgenius.spaces.live.com