Product backlog refinement and
Definition of Done
Paving the way to agility
Christian Vos
Rood Mitek Software
Feedback

Quick Feedback
Feedback
• Quick
• Many times

Feedback

Improve

Inspect

Adapt

• Learn
• Helps goal reaching
Feedback & Iterative Development
Feedback

All steps
for
shipment

Empirical
management

Learning
by review,
test

• Quick...
Why Definition of Done ?

Inspect , Adapt and Improve

• All steps of software life cycle (dev to
deployment) get feedback...
Why Definition of Done ?
Almost done is not done at all
• PO and Dev in discussion
•
•
•
•
•
•

Is it done ?
Yes, almost
C...
Why Definition of Done ?

Better release planning

• No need for hardening iterations.
Iterations where bugs are solved, t...
Release planning
Product Backlog
5

• UserStory

1

• UserStory

3

• UserStory

3

• UserStory

2

• UserStory

4

• User...
Definition of Done
Release

Iteration

undone
work

Iteration

undone
work

Unsolved Bugs
Integration/Regression Test
Depl...
Definition of Done

Iteration

undone
work

Iteration

undone
work

Iteration

undone
work

Iteration

undone
work

Test
I...
Definition of Done

Iteration

undone
work

Iteration

undone
work

Iteration

undone
work

Iteration

undone
work

Test
I...
Definition of Done

Iteration

undone
work

Iteration

undone
work

Iteration

undone
work

Iteration

undone
work

Releas...
Definition of Done
Release burndown chart

Actual work
remaining
Definition of Done
Release burndown chart

Undone work

work remaining
Definition of Done
Release burndown chart

Actual work
remaining

Delta of ideal
Definition of
Done and Actual
Defintion o...
Definition of Done
Release burndown chart

Actual work
remaining
Why Definition of Done ?

Minimize the delay of risk

• Undone work reveals itself in production !
Why Definition of Done ?

Defines the agility/quality/maturity of the team

• A team should be able to complete a (new)
fe...
Definition of Done
Two definitons of done :
-Competence -> Automation (Can’t)
-Maturity - > Won’t

In Use/ Current
• Trans...
Definition of Done
Ideal
•Code checked in
•Code build green on build server
•Coding Quality Check Green(er) (Sonar)
•Unit ...
Definition of Done
Ideal
•Code checked in
•Code build green on build server
•Coding Quality Check Green(er) (Sonar)
•Unit ...
Definition of Done
Conclusion
Definition of Done helps you with :
•
•
•
•
•

Improving team quality/agility/maturity
Trans...
Product Backlog

• List of whatever needs to be done in order to successfully deliver a
working software system
• Features...
Product Backlog Refinement

•
•
•
•
•
•
•
•
•
•

Time boxed meeting +- 1,5 hour every week whole team
Product owner should...
Product Backlog Refinement
Clear-Fine Items
1.--2.--3.--4.--Vague-Coarse Items
-------------------------------------------...
Product Backlog Refinement
Clear-Fine Items
5
1.--1
2.--3
3.--3
4.--2
5.--5
6.--2
7.--2
8.--3
9.--5
10.--1
11.--3
12.--3
1...
Product Backlog Refinement
Iteration
Retrospective

Product Backlog

Iteration
Planning 1

Iteration
Planning 2

Refinemen...
Planning
Planning session 1 :

Determine capacity of team
Pick userstories based on
“feeling” and velocity in mind
Time : ...
Definition of Done
Product Backlog Refinement
Any Questions ?
Upcoming SlideShare
Loading in...5
×

Definition of Done and Product Backlog refinement

790

Published on

How to use the Definition of Done and the product backlog refinement in an Agile/Scrum project

Published in: Business, Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
790
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
25
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Definition of Done and Product Backlog refinement

  1. 1. Product backlog refinement and Definition of Done Paving the way to agility Christian Vos Rood Mitek Software
  2. 2. Feedback Quick Feedback
  3. 3. Feedback • Quick • Many times Feedback Improve Inspect Adapt • Learn • Helps goal reaching
  4. 4. Feedback & Iterative Development Feedback All steps for shipment Empirical management Learning by review, test • Quick • Many times Inspect adapt improve • Learning • Effective goal reaching
  5. 5. Why Definition of Done ? Inspect , Adapt and Improve • All steps of software life cycle (dev to deployment) get feedback • Product feedback : Test performance, Demo etc. • Process feedback : Coding Quality, Peer Review, Deployment etc.
  6. 6. Why Definition of Done ? Almost done is not done at all • PO and Dev in discussion • • • • • • Is it done ? Yes, almost Can we go to production ? No, not yet Why not ? Some bugs, some tests, not sure it works on prod, Webservice not reachable in business domain, manual has to be written, etc • When can we go to production ? • I am not sure…..
  7. 7. Why Definition of Done ? Better release planning • No need for hardening iterations. Iterations where bugs are solved, tests are done, deployment is prepared • Estimate / plan on iterations
  8. 8. Release planning Product Backlog 5 • UserStory 1 • UserStory 3 • UserStory 3 • UserStory 2 • UserStory 4 • UserStory 5 Iteration 1 • UserStory 23 • Total story points Iteration 2 Velocity of 6 Iteration 3 Iteration 4 Done and Release !
  9. 9. Definition of Done Release Iteration undone work Iteration undone work Unsolved Bugs Integration/Regression Test Deployment packages Documentation Performance issues etc Iteration undone work Iteration undone work
  10. 10. Definition of Done Iteration undone work Iteration undone work Iteration undone work Iteration undone work Test Iteration Release Iteration Release
  11. 11. Definition of Done Iteration undone work Iteration undone work Iteration undone work Iteration undone work Test Iteration Release Iteration Release
  12. 12. Definition of Done Iteration undone work Iteration undone work Iteration undone work Iteration undone work Release Iteration Release Iteration Release
  13. 13. Definition of Done Release burndown chart Actual work remaining
  14. 14. Definition of Done Release burndown chart Undone work work remaining
  15. 15. Definition of Done Release burndown chart Actual work remaining Delta of ideal Definition of Done and Actual Defintion of Done
  16. 16. Definition of Done Release burndown chart Actual work remaining
  17. 17. Why Definition of Done ? Minimize the delay of risk • Undone work reveals itself in production !
  18. 18. Why Definition of Done ? Defines the agility/quality/maturity of the team • A team should be able to complete a (new) feature in one iteration and release it immediatly to production with all steps defined in the DoD necessary to guarantee best quality.
  19. 19. Definition of Done Two definitons of done : -Competence -> Automation (Can’t) -Maturity - > Won’t In Use/ Current • Transparant for Product owner • Represents capability of the team • What to improve Optimal/Ideal • Where do you want to go
  20. 20. Definition of Done Ideal •Code checked in •Code build green on build server •Coding Quality Check Green(er) (Sonar) •Unit Test build server OK •Unit Test build server OK (Code Coverage 80 %) •Peer reviewed •(Automated) Deployed on CI Server •One click on Demo Server •(All deployment is including automated database deployment on all mentioned servers) •(Automated) Integration Test run on CI •(Automated) Acceptance Test run on CI •(Automated) Performance Test run on CI •(Automated) Deployed on ST Server •(Automated) Deployed on UAT Server •Exploratory testing done on ST Server •Integration (chain) testing done on UAT Server •Demo-ed and approved by Product Owner •All sprint related bugs solved •Deployment Guide up to date •Interface documentation up to date •Use Cases up to date •RMS up to date •Release Notes up to date •User Manual up to date •SRS updated •Iteration Test Rapport (up to date) •Technical Design updated (when absolutely necessary) •Product Backlog up to date Two definitons of done Current •Code checked in •Code build green on build server •Coding Quality Check Green(er) (Sonar) •Unit Test build server OK •Peer reviewed •(Automated) Deployed on CI Server •(All deployment is including automated database deployment on all mentioned servers) •(Automated) Integration Test run on CI •(Automated) Acceptance Test run on CI •(Automated) Deployed on ST Server •Exploratory testing done on ST Server •Demo-ed and approved by Product Owner •All sprint related bugs solved •Deployment Guide up to date •Interface documation up to date •Use Cases up to date •RMS up to date •Product Backlog up to date Delay of Risk Manifestation in production
  21. 21. Definition of Done Ideal •Code checked in •Code build green on build server •Coding Quality Check Green(er) (Sonar) •Unit Test build server OK •Unit Test build server OK (Code Coverage 80 %) •Peer reviewed •(Automated) Deployed on CI Server •One click on Demo Server •(All deployment is including automated database deployment on all mentioned servers) •(Automated) Integration Test run on CI •(Automated) Acceptance Test run on CI •(Automated) Performance Test run on CI •(Automated) Deployed on ST Server •(Automated) Deployed on UAT Server •Exploratory testing done on ST Server •Integration (chain) testing done on UAT Server •Demo-ed and approved by Product Owner •All sprint related bugs solved •Deployment Guide up to date •Interface documentation up to date •Use Cases up to date •RMS up to date •Release Notes up to date •User Manual up to date •SRS updated •Iteration Test Rapport (up to date) •Technical Design updated (when absolutely necessary) •Product Backlog up to date Two definitons of done Current •Code checked in •Code build green on build server •Coding Quality Check Green(er) (Sonar) •Unit Test build server OK •Peer reviewed •(Automated) Deployed on CI Server •(All deployment is including automated database deployment on all mentioned servers) •(Automated) Integration Test run on CI •(Automated) Acceptance Test run on CI •(Automated) Deployed on ST Server •Exploratory testing done on ST Server •Demo-ed and approved by Product Owner •All sprint related bugs solved •Deployment Guide up to date •Interface documentation up to date •Use Cases up to date •RMS up to date •Product Backlog up to date •User Manual up to date
  22. 22. Definition of Done Conclusion Definition of Done helps you with : • • • • • Improving team quality/agility/maturity Transparancy to stakeholders Giving burndown charts sense Better release planning Minimizing delay of risk
  23. 23. Product Backlog • List of whatever needs to be done in order to successfully deliver a working software system • Features, functionality, technology, issues, emergent items • Prioritized, estimated • Product Owner responsible for priority • More detail on higher priority items • Anyone can contribute • Posted visible and Maintained
  24. 24. Product Backlog Refinement • • • • • • • • • • Time boxed meeting +- 1,5 hour every week whole team Product owner should attend Split , clarify and estimate work items, user stories, RFC’s Share new insights with the team Re-estimate when necessary Priority determined by Product Owner Goal is the have a “ready” Product Backlog for next planning Prevent discussions in the planning session Visualize release planning (also known as Backlog Refactoring, Backlog Maintenance, Backlog Grooming)
  25. 25. Product Backlog Refinement Clear-Fine Items 1.--2.--3.--4.--Vague-Coarse Items --------------------------------------------------------------------------------------------------------------------------- Items that are detailed and small enough to be picked up by development for implementation Need more details, more discussion, more acceptance criteria, smaller etc.
  26. 26. Product Backlog Refinement Clear-Fine Items 5 1.--1 2.--3 3.--3 4.--2 5.--5 6.--2 7.--2 8.--3 9.--5 10.--1 11.--3 12.--3 13.--- Iteration 1 Iteration 2 Iteration 3 Release Refinement visualizes the release planning
  27. 27. Product Backlog Refinement Iteration Retrospective Product Backlog Iteration Planning 1 Iteration Planning 2 Refinement Iteration 2 weeks Iteration Review 1 Product Baclog Refinement
  28. 28. Planning Planning session 1 : Determine capacity of team Pick userstories based on “feeling” and velocity in mind Time : 5-10 minutes Planning session 2 : Define tasks and hours Time 2 hours
  29. 29. Definition of Done Product Backlog Refinement Any Questions ?
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×