Dont create new artefacts and commitments

[gabrichidze1]

The Scrum guide construction of three artefacts and three commitments (product goal for product backlog, sprint goal for spint backlog and increment for Definition of Done) is simple, beautyful and very efficient
It is possble to add additional metrics or reqirments like Definition of ready. But complicating existing commitments like Definition of Outcome Done, or whole new artefact-commitment line like " For the Increment that is a candidate update for the Product, it is the Definition of Output Done." will only make already near heavily overleaded framwork even more complicated.

[rjocham]

@gabrichidze1 thanks for your input. In the SGEP we have

We have 4 Artifacts with 1 Commitment each:

• Product -> Def of Outcome Done
• Product Backlog -> Product Goal
• Increment -> Def of Output Done
• Sprint Backlog -> Sprint Goal

Would a Definition of Ready make it more complicated? Also, you would have to fulfill it always, even if not needed. That is where Refinement comes into play. The Refinement creates readiness through conversation creating understanding until the Product Developers feel they have a good enough understanding.

[ViralGoodAgile]

@gabrichidze1 - I posted a discussion on what is optional in the SGEP. See Optionalality in the SGEP at #104

We don't currently plan to add a Definition of Ready in the September 2025 update; while Definition of Ready can be useful, @rjocham and I (and many Scrum thought leaders) are a bit concerned it is maybe not good context-free advice.

[rjocham]

#105 is an article about the Definition of Outcome Done by @ViralGoodAgile.
Often the Def of Ready is abused as contract by the Developers because they burned in the past. We won't add a Def of Ready in the September release.

[rjocham]

We are thinking about replacing commitment with another word. We are entertaining the word 'agreement'.
The more we are working the Product vs Increment the more we are happy with the description with the Increment being the candidate release for the Product.

Thoughts about this?

[gabrichidze1]

Commitment is a great word. Artefact > commitment structure explains the whole framework perfectly Nick Gabrichidze http://www.datainventors.com Tel. and WhatsAPP: +32 475506266

…

On Sun, Jul 27, 2025 at 10:40 AM Ralph Jocham ***@***.***> wrote: We are thinking about replacing commitment with another word. We are entertaining the word 'agreement'. The more we are working the Product vs Increment the more we are happy with the description with the Increment being the candidate release for the Product. Thoughts about this? — Reply to this email directly, view it on GitHub <#84 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BCQDBSFXNLWDNF46LBP7Y4D3KSGARAVCNFSM6AAAAAB7LWWQNSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOJQGA2DMMQ> . You are receiving this because you were mentioned.Message ID: <ScrumGuides/ScrumGuide-ExpansionPack/repo-discussions/84/comments/13900462 @github.com>