Definition of Ready: A sprint is a time-boxed development cycle in which items need to be pulled from the prioritized backlog. However, it is very important that the items (User Story) should be in “Ready state”. Pulling unfinished or unrefined user story will make the current sprint delay its deliverables as well as developer will also not be able to develop the expected functionality. “Ready” State is clearly depicted in the below diagram. Definition of Ready is focused on the User Story level characteristics whereas Definition of Ready on Sprint and Release level. Definition of Done: It represents the acceptance criteria for the Sprint. This list is prepared in discussion/agreement with the Product Owner and Development team on what needs to be completed for user story—it is often standardized across the company in order to deliver consistent product quality. A sample of Definition of Done is shown below. As per project needs, this can be tweaked. Test conditions written where beneficial to a story Unit tests written (where crucial) and passing Acceptance tests written,executed,and passing. Functional testing complete System Testing &Blog Fixing, for functionality implemented. Test cases written and passing with expected results,where the work requires it Regression Tested where appropriate. Developer documentation in Wiki(barely sufficient) Code complete Code committed Code pushed Code merged to default branch Code reviewed Meets acceptance criteria