eBook: 'Are We There Yet? Doneness Criteria'
On the last stop of the Agile Expedition, we explored Automated Testing’s role in Agile development. This time around, we’ll be discussing a favorite word among developers: 'Done'.
Why devote an entire ebook to defining what Done means? Isn’t it obvious when something is done? Not if everyone’s definition of Done is different. That’s why it’s important for the team and other stakeholders to know where the goal line is. Download your copy of the 'Are We There Yet? Doneness Criteria' eBook and learn how to:
- Define done
- Communicate done
- Eliminate waste
You'll also learn more about the importance of sprint lengths and how to use the 'Five Whys' to understand the root cause of an impediment.
Excerpt: Most traditional Waterfall projects end with an uncomfortable period of customer sign off, due to Waterfall’s predictive planning approach. For example, on a yearlong Waterfall project, Done is determined a year in advance. This is one of the many problems with predictive planning methods.
On an Agile project, releasable features of the application are developed in short sprints, so the team’s definition of Done is constantly reevaluated through the “inspect and adapt” process. There’s less chance of disagreement at the end of a sprint because the definition of Done is revisited at least every six weeks.