Skip to main content

DoD and DoR for Change Requests

Last post 12:30 am January 20, 2024 by Ian Mitchell
2 replies
10:54 am January 19, 2024

Hello,

Our client is working in Hybrid delivery model with Change requests for enhancing the existing requirements.

They are looking to define the DoR and DoD for the change requests?

Can you please let me know some criteria for them? 

Thank you!


07:31 pm January 19, 2024

Why do you need a Definition of Ready and Definition of Done for Change Requests? Why do you even need Change Requests to begin with?

If you're talking about features or functionality yet to be delivered, you shouldn't need a Change Request for stakeholders to talk to the Product Owner and then the Product Owner to update the Product Backlog. And once a feature or functionality has been delivered, Product Backlog Items become the Change Request.

I would recommend revisiting the value in a formal change request process. This kind of process is useful in plan-driven methods, where late changes can be impactful since you've invested a lot of time into getting your requirements right and then specifying a design that can satisfy those requirements, and then implementing that design. A requirement change can have a large, expensive, and time-consuming ripple effect. Agile methods, like Scrum, mitigate the need for expensive change control processes by making tolerance and acceptance of change a part of the way of working.


12:30 am January 20, 2024

If they don't understand their workflow policies, their delivery model can't really be said to be a hybrid of anything.

It's more likely that organizational constraints are forcing compromises from the outset. Unless these are identified and challenged, nothing will really change even if some kind of DoR and DoD policy is cooked up.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.