Definition of "Done"
•
6 gostaram•2,984 visualizações
This paper shall describe the structure, composition, attributes of good definition of “Done” & how to effectively document that. “Done” has 3 important focus areas; the product quality, business value to customer, and software best practices. The good definition will also address the contextual meaning to various focus groups at individual, team and organizational levels. Standard definition of “Done” statement that suits all situations in an organization across teams is impossible to create; done has a contextual reference specific to a team that suits their unique environment and stories. Also the definition should address not just the functional but also the non-functional requirements and standards like usability, performance, capacity & maintainability. The paper also discusses the responsibility & contributions from team, product owner and organization in authoring good definition for the word “Done”.
Recomendados
Mais conteúdo relacionado
Destaque
Destaque (17)
Mais de Naveen Nanjundappa
Mais de Naveen Nanjundappa (9)
Último
Último (20)
Definition of "Done"
- 1. ARE YOU REALLY DONE? UNDERSTANDING 3 IMPORTANT FOCUS AREAS, FOR DEFINITION OF “DONE” Naveen Nanjundappa Sept 2012 PMPC 2012 1
- 2. “I am done with my work” Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 2
- 3. Your work is not complete without … Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 3
- 4. Think ? Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 4
- 5. Naveen Nanjundappa Agile Coach, SolutionsIQ India. • Organizational Agile Transformations • Scrum Coaching / Training PMPC 2012 5
- 6. Agenda • User Stories • Definition of “done” – DoD Focus Areas – DoD for potentially shippable product • Creating definition of done List Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 6
- 7. Agile An attitude to deliver business value to customer using common sense approach Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 7
- 8. USER STORIES <WHO> < W H AT > <WHY> Card Confirmation Conversation Photo Credit - http://www.freedigitalphotos.net/ Ref: Mike Cohn – User Stories Applied PMPC 2012 8
- 9. DEFINITION OF “DONE” A l l t h a t “we need to do” t o “claim” t h a t w e a r e “done” w i t h t h e u s e r s t o r y Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 9
- 10. “Definition of Done” is Important • Team focus on “goal” • Improves productivity of team • Do as much as required to satisfy the acceptance • Track the progress of the story Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 11
- 11. Big Challenge How to know we are done s u f f i c i e n t l y? PMPC 2012 12
- 12. Focus Area - Product Quality • Quality Assurance Activities – Unit, Integration, System, Performance Testing and so on… Every check that is required to ensure the product quality is high and low/no defects Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 13
- 13. Focus Area - Business Value • Functional & Non Functional Requirements • Regulatory specifications • Licensing and legal specifications So on… Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 14
- 14. Focus Area - Software Best Practices • Code Reviews, Pair Programming. • Continuous Integration, Deployment • Test Automation So on… Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 15
- 15. Potentially shippable product increment Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 16
- 16. DoD for an User Story Quality checks • Unit test passed. • Testing complete on all target environments Software practice checks • Code review or pair programming for code / test development done • Code is committed in the version control system Business need checks • User story done meets all the acceptance criteria. • All requirements related to the user story are completed. PMPC 2012 17
- 17. DoD for an Iteration Quality checks • Is the performance tested? • Have all the integration tests run and passed without errors? Software practice checks • Was the code continuously integrated during development? • User story status updated as required. Business need checks • Is the goal of the sprint met? • Did product owner accept all user stories? Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 18
- 18. DoD for a Release • Did customer accept all user stories in the release plan? • Is the release documentation complete? • Has the new product passed the Certification/Regulatory, licensing & compliance requirements tests and approved? • Does the product owner(s) feel confident about the product? Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 19
- 19. STEPS TO CREATE DONE LIST DoD - User Story Check list User story 1 User Story 2 User Story 3 DoD 1 DoD 2 DoD 3 DoD 4 Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 20
- 20. ACCEPTANCE BY PRODUCT OWNER & CUSTOMER Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 21
- 21. Conclusion • Critical for a team. • No – “One list fit all” • Quality, Business Value & Best Practice Create DoD for your team Today ! Photo Credit - http://www.freedigitalphotos.net/ PMPC 2012 22
- 22. There are no secrets, Open for discussion Thank you Photo Credit - http://www.freedigitalphotos.net/ For all photos in this presentation PMPC 2012 23
- 23. Thank You Naveen Nanjundappa Agile Coach, SolutionsIQ (India) naveenn@solutionsiq.com naveen.nanjundappa@gmail.com Mobile: +91 9980505003 PMPC 2012 24
Notas do Editor
- People claim they are done with their work, the work that is assigned to them.They are always in a hurry to finish their part of work.
- Think what are you missing ?
- Short introduction.
- Agenda for the presentation.
- What is agile.
- User story and the life cycle of the user story
- DoD