Definition of Done: Essential for efficient for scrum development

Definition of Done is highly essential for an efficient scrum based development.It actually helps in judging the status(completed/resolved) of work items.The status and completeness of work items can only be judged by Definition of Done.DoD actually helps in making the item potentially shippable.The definition of done is different for function,feature and release.In order to avoid confusion or make it more clear what scrum team/master can do is further breakdown the definition of done for better understanding.
Imagine scrum team has a coding task,design task requirement task etc .In that case for each different types of task the DoD can be arrived and can be tracked for the success of sprint.
Definition of Done for various lifecycle tasks are listed below which in turn can result in success of feature

  Design task
·     Has the design undergone review and whether all review comments are closed or not?
·    Does the design contain the high level block diagram with intermodular interfaces decided?
·     Is design developed is following certain set of guidelines?
· Has design considered factors like portability, scalability and other non functional requirements ?
·   Is Design document available in the Configuration management system in specified folder location and file name

Coding task
·   Has code undergone review and whether all the review comments are closed or not ?
· Has code been checked with  respect to coding guidelines with respect to programming languages (Ex:-C,C++,Java) ?
·    Has the code undergone static analysis and whether all the comments are closed or not ?
·    Does the code files have appropriate and sufficient  comments present in it(Code :comment ratio) ?
· Are coding files  available in the Configuration management system in specified folder location and file name ?

Testing task
·    Are all the test results documented?
·     For all the failed test results is appropriate analysis been done and documented?
·    Are all the test cases cross checked with respect to acceptance criteria of requirements ?
·  Are all the testing files  available in the Configuration management system in specified folder location and file name ?

 Bug
·   Has the Root cause analysis of bug done?
· Are all the associated work products like code,test cases,design & requirements etc document history  are updated /modified w.r.t  bug resolution
·  Is the new code base checked in to configuration management system with the appropriate naming convention etc?

Leaving the above I feel for a sprint and release it is much more easier to define with respect to the type/client of project. Definition of done is essential in judging the quality of workproduct.The DoD criteria should be auditable checklist rather it should not be detailed checklist

Comments

Popular posts from this blog

100 mostly used abbreviations(full forms) across daily life

Decoding Maruti’s Success

Green Marketing