Definition of Done formalization

Hi Marco,

about DoD I recommend you to read great article of Ian Mitchell

https://www.scrum.org/resources/blog/walking-through-definition-done

maybe, it’ll help you somehow. If not, please ask.

You're correct, the definition of "Done" is not a Sprint Backlog item.  The definition of "Done" applies to the Increment.  The DoD may include non functional requirements (e.g. security, performance) as well as other details such as unit test coverage, quality, etc.  In the real world, it may be written down by the Development Team or the Development organization, and made transparent, as everyone needs to understand what "Done" means. 

Some teams may have it written on their white board or on a large sheet of paper, and have it hanging in their team room, otherwise known as an Information radiator, which is what I prefer.  Other teams may be distributed, so they prefer a web site or a wiki page.  Other teams may be mature Scrum teams and have a verbal agreement of what it is.  Regardless, the Development Teams can find the best way to make it transparent so everyone is on the same page.

The Sprint Goal is something different than the definition of "Done".  The Sprint Goal guides the Development Team, and is their objective  and 'north star' for the Sprint.  The Sprint Goal gives the Development Team a focus and purpose for the Sprint.  For example: "Provide an way for our customers to purchase insurance policies on their mobile devices".  

Much can be answered here: https://www.scrumguides.org/ 

Chris

Thanks Marcin, thanks Chris

now I understand better.

Should Sprint Goals be expressed in information radiators too?

If Sprint Goals are so high-level, as in your mobile insurance purchase example, could they be shared across multiple Sprints?

Thanks again

Marco

Should Sprint Goals be expressed in information radiators too?

The Sprint Goal is a coherence that causes the Development Team to work together rather than on separate initiatives. Individual developers ought to commit to the goals of the team. What are your thoughts about expressing the Sprint Goal via an information radiator?

If Sprint Goals are so high-level, as in your mobile insurance purchase example, could they be shared across multiple Sprints?

The purpose of a Sprint is to meet a Sprint Goal. Do you think it would make sense for a Goal to repeat across multiple Sprints?