When is ‘Done’, truly 100% ‘Done’?
5 Dec 2017
When working through any Product Backlog, it’s essential that the whole Scrum Team have a clearly defined and mutually agreed understanding of when each backlog item can be deemed as complete. Without this collective and transparent agreement, teams may struggle to get product backlog items 100% truly ‘Done’ within a Sprint. This is explained further by the Scrum Guide; “When a Product Backlog item or an Increment is described as “Done”, everyone must understand what “Done” means. Although this varies significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the definition of “Done” for the Scrum Team and is used to assess when work is complete on the product Increment.” The Scrum Guide (p.16) The below example of ‘Done’ is fairly typical for a team early on in its adoption of Scrum within a corporate environment. Activity (Example) Criteria (Example) Detailed Analysis Acceptance Tests approved by Product Owner. Wiki updated. Detailed Design Consistent with approved design patterns and UI standards. Design approved by Architect. Overall Design Doc updated. Build & Unit Test Consistent with coding standards. Peer Reviewed. 90% automated unit test coverage. All unit tests […]
The term Agile originates from the Agile Manifesto of 2001, but the first Agile approaches emerged in the 1990s with Scrum and eXtreme Programming (XP). The agil8 approach brings expertise built over 20 years with these early Agile methods right through to the latest developments such as Lean Kanban.
The agil8 approach is to help you select, tailor, define and implement the best Lean and Agile approach for your own particular circumstances. What is right for one organisation or project is not necessarily right for another. Whilst many of the challenges that different organisations face in implementing Agile are often the same, the solutions to those challenges are, like the organisations themselves, always unique. Moreover, organisations and circumstances change so what is the best solution today is unlikely to be the best solution tomorrow. Above all else, the agil8 approach emphasises the important of continuous evolutionary improvement.
This kind of expertise only comes with years of experience. Lean and Agile is fine in theory, but without a deep practical understanding of the different approaches and how to make them work in the real world their potential is very difficult to realise.
The agil8 enablement approach can be applied at any scale from the individual team, departmental or enterprise level. It covers everything that you need to make your transition to Lean and Agile effective and successful including Initiation, Training and Education, Coaching, Reviews and Retrospectives, and Transformation Management.
Scrum is the most popular agile method by far, and is usually at the heart of the approach adopted by agil8 clients. However, Scrum’s apparent simplicity raises challenges when attempting to map it onto a complex organisation, so the agil8 approach involves applying Scrum in the best possible way for each unique circumstance.