dod
Chronicles of a Scrum master #19 : User stories guide to better development and further refinement
In the world of agile, requirements come in the form of user stories and it is important to understand that the details contained in the stories are needed to absolute clarity for anyone who is going to be working to get this stories done. Consequently, here are several practices which can be adapted to organizations […]
Read More
Chronicles of a Scrum master #16 : Definition of Done (DoD) Part 2
Note : This is a continuation of my Definition of Done (DoD) Part 1 here. 3. Quality The important assessment of a story after its development or work that needs be done is completed (may not be Done yet) is the quality of the work that is produced. This is usually performed by the QA […]
Read More
Chronicles of a Scrum master #15 : Definition of Done (DoD) Part 1
What is a story that is considered done in a sprint ? Each scrum team may have their own version of the Definition of Done (DoD) for each story as long as they agree on the common concept as a whole (from product owner, business analyst to scrum master, developers and testers. It is essentially […]
Read More