![]() ![]() Given the descriptions of the work that you have, it seems like 4 of the 5 - Story, Story (dev only), Task, and Bug - will lead to some change in the product. You may meet the Definition of Done PBI-by-PBI or you may take a bundle of PBIs and move them to Done after meeting all of the elements of the Definition of Done. ![]() I interpret this as meaning that a Product Backlog Item cannot be considered Done until the Increment meets the Definition of Done. I find the wording of this sentence a little confusing. ![]() The moment a Product Backlog item meets the Definition of Done, an Increment is born. The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.īased on this, the Definition of Done isn't necessarily applicable to an individual Product Backlog Item, but the Increment as a whole. The definition of "Definition of Done" from the November 2020 edition of the Scrum Guide: Please advise what will be the correct way to go here. Therefore, if we write down in our DoD smth related to testing or user acceptance, it can't be applied to "Story (dev only)", "Bug", "Spike" issues types at all, because it's clear that there is no testing & user acceptance there.Īm I right to understand that if we decide to create DoD for our team, it should be created only for the increment-related issues? I can't see any other options here for now, unfortunately. Task - basically same as a regular story, but without describing the needed scope from the user's POVĪs you can see from the above-mentioned list, only "Story" & "Task" issue types are directly related to the increment and will be released at the end of the Sprint. Story (dev only) - for works that act as enablers for future increment-related worksĢ. Story - for works that will be included in the future releaseĢ. For example, in my team we have the following issue types in Jira:ġ. I am a little bit confused with the DoD concept and whether it's applicable for increment-only issue types or to all PBIs that team has. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |