Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Definition of done vr 2
Transcript of Definition of done vr 2
What: Development of the code that will solve the functional and technical acceptance criteria of a story.
Why: No code, no new or improved functionality
How: Through experimentation, quality focus and understanding
What: Quality assurance
Why: To deliver quality functionality across the board
Acceptance testing on dev.fronter.net
Unit testing (should never be lower then when you started)
Automation tests (Selenium, Jmeter)
Review and demo
What: Codereview and demo
Why: To make sure what we deliver lives up to the standards we have decided upon and that it gives the result we would like.
How: Codereview that covers that the functionality actually does what the developer intended, and that it follows our standards.
Demo for product owner and other stakeholders.
Standards: coding standard, refactoring guidelines, linting, REST best practise, design guidelines, accessibility guidelines, data security concerns
What: The way from the developers local environment to production
Why: Until something is in production it has less value (some might even say no value)
How: All critical bugs are fixed.
Enough documentation is in place.
Database scripts are ready (if needed).
Strings are synced
Handover to operation is done (if needed)
Configuration changes are done.
The commit has been released into production.
Measure and validate
Review and demo
Measurement and validation
"DONE MEANS NO MORE WORK TO DO"
What: Measurement and validation
Why: To learn and to verify direction
How: After a story is released into production it should be possible
to measure impact of it both on performance and if it achieved
what we wanted.
Preferably we would also like customer validation that the
implementation was a success.