Definition of Ready
I heard on many websites and e-courses that we cannot change Definition of Ready in the scrum, but Definition of Done can be modified in the journey. I believe Scrum is based on Empiricism and always support adaptation. Then why is it so?
What websites and e-courses are you referring to?
The concept of a Definition of Ready does not appear in the Scrum Guide. In fact, the word "ready" appears once:
Product Backlog items that will occupy the Development Team for the upcoming Sprint are refined so that any one item can reasonably be "Done" within the Sprint time-box. Product Backlog items that can be "Done" by the Development Team within one Sprint are deemed "Ready" for selection in a Sprint Planning. Product Backlog items usually acquire this degree of transparency through the above described refining activities.
Unlike a Definition of Done, there's no Definition of Ready in Scrum. That doesn't mean that it's not useful for a team to develop and maintain a Definition of Ready that defines what it means for a Product Backlog Item to be ready for selection in Sprint Planning. Since adaptation is a key pillar of Scrum, I would expect teams to adapt their way of working. The outcome of adaptation may be something that is no longer Scrum, but I don't believe that the addition of a Definition of Ready would make your way of working not Scrum, since Scrum "functions well as a container for other techniques, methodologies, and practices."
Does Scrum Guide say anything about Definition of Ready ?
I heard on many websites and e-courses that we cannot change Definition of Ready in the scrum, but Definition of Done can be modified in the journey. I believe Scrum is based on Empiricism and always support adaptation. Then why is it so?
Did those sources provide an example of a "Definition of Ready" which they consider to be immutable?
One risk I see with a "definition of Ready", is that there isn't necessarily a universally understood meaning of how it should be applied. The Scrum Guide doesn't offer very much in that area.
I have seen definitions of Ready prevent teams from taking on the most valuable items on the Product Backlog, in favour of better understood items.
Should, a development team ever agree to take on work that does not yet meet their definition of Ready?
What if a sprint could be used to not only get something "Done", but also begin with getting something ready?
Product Backlog items that can be "Done" by the Development Team within one Sprint are deemed "Ready" for selection in a Sprint Planning.
– Scrum Guide
Given what the Scrum Guide says, are teams and organizations really looking for a definition of ready?
Might it be sufficient to see "Ready" as something that can be "Done" within a sprint?
Could it be that these teams and organizations instead need help in understanding what "Ready" is in their context?
Rather than defining a list of things to be completed upfront, could teams inspect and adapt towards an understanding of when something is probably "Ready", according to what the Scrum Guide already says?
Please be careful with DoR becoming a hardcore stage/phase gate.
+1 !
inspect & adapt in order to minimize waste