Understanding and Apply Scrum [P7]: Done - Walking through a Definition of Done

Question 1

Explain “Scrum begins with Done”

Answer 1

• must define the end before we can start
• knowing when you are Done frames the work which must be undertaken in order to get there

Question 2

Why does an understanding of what makes in increment truly releasable and therefore genuinely Done provide?

Answer 2

transparency over the work a Dev team plans to do, and the tasks it brings into progress

Question 3

Why is Done so important? I.e. what happens without having a DoD?

Answer 3

• incomplete work has a nasty habit of mounting up, and without visibility of how much effort truly remains, the deficit can quickly get out of hand
• TD - The tyranny of work which isnearly done, but notreally done, can put a team in servitude to technical debt —> always chasing to pay off TD and its compounding interest

Question 4

Explain the example of a DoD item: “1. Environments are prepared for release”

Answer 4

• check no unintegrated work in progress has been left in any development or staging environment
• check that CI framework is verified and working, including regression tests and automated code reviews
• build engine should be schedule a build on check-in (also hourly/nightly)
• check that all test date used for validation has been validated

Question 5

Explain the example of a DoD item: “2. Handover to support is complete”

Answer 5

• All design models and specifications, including user stories and tests, must be accepted by support personnel who will maintain the increment henceforth
• support must be satisfied that they are in competent control of the supporting environment

Question 6

Explain the example of a DoD item: “3. Review Ready”

Answer 6

• sprint metrics available - including burn down and burn up charts
• uncompleted user stories re-estimated and returned to PB

Question 7

Explain the example of a DoD item: “4. Code Complete”

Answer 7

• Resolved TODO annotations
• source code comments at satisfactory level
• source code refactored - understandable, maintainable and promotes future change
• tests cases for all features + clear naming convention for req tracing + all pass
• known agreed code coverage level + met
• pair reviews done
• merged with main branch
• automatic deployment into elevated envs verified

Question 8

Explain the example of a DoD item: “5. Test Complete”

Answer 8

• functional testing done - automated and manual
• test report generated
• outstanding defects elicited and resolved or accept by team as not being harmful to the release
• regression completed and previous working functionality still good
• all functionality works on all required platforms

Question 9

What is meant by a deficit for release?

Answer 9

• Done criteria which are needed to effect a release, but which cannot yet be observed
• create a list for this — move them out of DoD

Question 10

Is the DoD influenced by the org? Why

Answer 10

Yes

need to combine org’s DoD with PO and Dev’s DoD

• e.g. non-functional reqs - docs, scalability

⇒ minimize waste! - on the same page regarding org wide things