The Rise Of The Lean Machine An eye opening presentation by Claudio Perrone. I can immediately think of at least 5 steps I'd need right now or in the near future.
Where to Begin Your Transition to Lean-Agile
Alan Shalloway & James R. Trott give us a more practical guide to making a lean/agile transition work.
Common Myths of Kanban This is in context of software.. Kanban now popular enough to have myths!
Managers New to Agile May Not Know What to Do Johanna Rothman explains some of the problems with adopting agile..
How to be happy (but not too much) Dan Jones explains how being happy means you're more open to learning,etc.etc.
Defining What Done Means Another great article by Rachel D.
Six Key Things For Managing Agile Teams Derek Neighbors lists a number of the characteristics of collaborative teams (but not all).
A Root Cause Analysis of Agile Practices Regularly link to Karl Scotland and he does not disappoint again with a summary of a recent open space session with the above topic. Also congratulations to Karl on getting the opportunity to write a book about Kanban!
Showing posts with label Definition of Done. Show all posts
Showing posts with label Definition of Done. Show all posts
Monday, 27 September 2010
Wednesday, 29 April 2009
South UK Scrum User Group, 27th April 2009
Getting an acceptable definition of done
[Notes from 27th April 2009, South UK Scrum User Group]
The level of granularity is important, which is why we define the definition of done at four levels: release, sprint, story and task.
At the task level we look at the following:
- Developer says it is done
- Unit test exists and passes
- The code is in the trunk
- Code coverage is above the target (e.g. 90%)
- More criteria can be used as function points, analysis coverage, cop type coverage
- Tracking system is updated
- Check-in is reviewed
- The work is reviewed
At the sprint level we define the following:
- All agreed stories are done
- Held a retrospective which is documented
- Show and tell demo
At the Release level the criteria are:
- All sprints are done
- Media is produced (e.g. CDs, marketing materials)
- User documentation has been reviewed (e.g. by the user community)
- Install and release notes are ready
- External testing or audits are performed (e.g. security audits)
- PO signs it off
The definition of done for Story include:
- All tasks associated with the story are done
- The story is integrated and tested
- Acceptance criteria is met
- Installation works
- Documentation is done
- Product owner accepts the story
[Notes from 27th April 2009, South UK Scrum User Group]
The level of granularity is important, which is why we define the definition of done at four levels: release, sprint, story and task.
At the task level we look at the following:
- Developer says it is done
- Unit test exists and passes
- The code is in the trunk
- Code coverage is above the target (e.g. 90%)
- More criteria can be used as function points, analysis coverage, cop type coverage
- Tracking system is updated
- Check-in is reviewed
- The work is reviewed
At the sprint level we define the following:
- All agreed stories are done
- Held a retrospective which is documented
- Show and tell demo
At the Release level the criteria are:
- All sprints are done
- Media is produced (e.g. CDs, marketing materials)
- User documentation has been reviewed (e.g. by the user community)
- Install and release notes are ready
- External testing or audits are performed (e.g. security audits)
- PO signs it off
The definition of done for Story include:
- All tasks associated with the story are done
- The story is integrated and tested
- Acceptance criteria is met
- Installation works
- Documentation is done
- Product owner accepts the story
Subscribe to:
Posts (Atom)