YDS: What is the Definition of Ready in Scrum?

[@fredrikvestin752]

I find it useful, especially for new teams finding their way. For a mature and performing team not so much. Especially if the team find that it is unclear what they are supposed to build in the sprint a DoR can help, but I would prefer to keep it simple e.g. estimated, max 1/2 sprint in size, acceptance criteria.

[@tenchulds]

Thank you guys for sharing your thoughts.

[@minnickelfamilia1772]

Love your channel! I have used many of your videos with my team and I listen to you both while making breakfast for my kids. Ryan, the first two episodes of Wanda Vision were slow but then it gets crazy good - I recommend it. Todd, I won't go chase waterfalls with my team 😄

[@elsvandooren]

Interesting talk.Especially how you both have an opinion on DOR. In my opinion, definition of Ready could be really helpful when you are in an Agile transformation fase, where a monolitic codebase is still in place, more than 60 teams are working and dependencies + defects are big part of the sprints. It helps teams keeping frustrations to a minimum and focus on the changes that are happening. When you work with mature teams who have full ownership on the product, a definition of ready could impact the opportunity to challenge the PO or other stakeholders. An example could be the dependencies on other teams, teams got demotivated because of this. I like the name "Refinment policy". It's basically the same, only another way of thinking about User stories.

[@kensaiyeahyeah123]

A checklist would still be useful if we treat it as a guide. Like "These are things that will help us understand the PBI".

[@melvinsng9909]

Fully concur with Todd that the DoR is only for newly formed Scrum Team to have them aware what are the areas that the user stories should cover. Once things get going, this is no longer needed as it feels like a contract.

[@supergirls3985]

I agree with Ryan. This DoR should not exist at all. 1. It's not in Scrum Guide. 2. It's so easy to get confused with DoD. Even with new startup team, it's better not to use it 5o avoid confusion in the long run. Thanks.

[@rajadas6432]

I agree to your points, Todd & Ryan. At the same time, I would like to place an argument in favor of DoR. All organizations are not at the same level of agile theory/mindset/framework maturity. For economic constraints, various combinations of team structures are in place like (combination of offshore, near shore, multiple vendors, contractors, sub-tractors, FTE etc.). Or there is no dedicated /knowledgeable/ empowered PO to collaborate with team throughout the sprint. In such high matrix environment competition/penalty/survival takes precedence over collaboration. To maximize the 'individual silo team's' success, teams try to use DOR. I see this as anti-pattern but I can't ignore the ground reality. Until the leadership/C-level executive don't consider as impediment and fix it, people will see value in DoR.

[@dkuzmar]

Question: Is the DOD for the Sprint increment the same as the DOD for each PBI in the Sprint? What is your recommendation as to how DOD should be applied at various levels in Scrum (i.e. PBI vs Increment vs Organizational Standard, etc.)? BTW, love the content. Keep it coming!

[@ShadesDon]

6:25 summarized!

[@ben-sykes]

In response to Todd's example of a PO creating an "empty" story at the top of the backlog right before planning... Yeah, I understand the PO has the power to do this, but how can a developer/team realistically begin work on an item like this?

[@AgileforHumans]

@Ben what's happening!!! I wasn't saying the PBI was completely empty. Vague sure and something the team needs to perhaps refinement during planning but not completely empty. This, of course, shouldn't happen ALL the time but may from time to time and the team shouldn't get upset at it. As a previous PO, there have been times where I have a sudden idea or have a hallway conversation with a stakeholder right before planning. We don't want to deter this because it's the nature of complex work :)

[@ben-sykes]

@@AgileforHumans Hey Todd! It's been awhile, hope you're doing well! I appreciate the clarification, the two of you describe some of the more extreme violations of DoR and that's how I took your example here. I could agree that a formal DoR isn't necessary (I believe this was the point of this video), but I disagree with completely abandoning DoR. Having a mutually agreed upon informal idea of DoR provides everyone (including the PO) with a baseline understanding of what's required before work can realistically begin. To me this is the transparency you said DoR doesn't provide. I should also stress that I'm not saying this should be used to get upset about POs prioritizing new/empty work or the outright refusal of work, but rather a baseline to guide discussions to acquire the 'stuff' necessary to begin work. Just my thoughts though, would love to discuss why I'm wrong haha! Loving the videos btw, keep it up!

[@igorlakic2686]

This channel is brilliant such as Ryan and Todd. :)) I have one question for you guys and I hope you will answer me. What's your take on Cone of Uncertainty?

[@AgileforHumans]

Great suggestion! We will talk about the Cone of Uncertainity on a future episode of the show! Thanks again for the awesome suggestion.

[@igorlakic2686]

@@AgileforHumans Thank you for your kind reply. :)) Can't wait to see video about that. :))

[@supergirls3985]

@@igorlakic2686 Me too.

[@ManifestationsX]

Love your channel guys! Keep up the great content.

[@AgileforHumans]

Thank you! Will do! Thanks for watching, sharing, and commenting!

[@jonathancaballa]

Watch WandaVision! It starts slow but pays off (so far, the last episode is on Friday).

[@AdamSchumph]

WandaVision is excellent if you like the MCU

[@AgileforHumans]

Alright, I'm (Ryan) in! I'll start watching WandaVision today! Thanks for the nudge. Can't wait to report back on the show.

[@abhishekdixit8581]

Thanks for an insightful episode! 👍🏼 Q. What are the attributes of a Product Backlog Item?

[@blkngld08]

Why does it have to be a checklist? If you create checklists that just eliminates the possibility of any conversation. The act of checking the box becomes paramount. Pick and place in any context. If you create a ‘definition’, that leaves room for interpretation, thus creating wanted dialogue.

[@supergirls3985]

Hi Ryan and Todd, I just saw a power point from Scruminc, created by Jeff Sutherland. In it, it specifically mentions " Product Owner Responsibility•Get one sprint READY backlog •Team can get started •Get two sprints READY backlog •Team can accelerate sprint to sprit". It's not from Scrum.org, but as the co creator of Scrum, Jeff's company makes it different than what we learned from Scrum.org. Kind of confused. What's your opinion about this? Thanks! Junlong.

[@AgileforHumans]

I'm not sure I totally understand what you are saying, perhaps I'm missing a bit of context. We are not implying that a Product Owner shouldn't have work that is "ready" to be brought into a Sprint on the Product Backlog. In fact, we suggest that the Product Backlog has two-three Sprints worth of PBI's that have been refined and are "ready" to be brought into the Sprint. We do not, however, like the DoR as we've seen it turn into a contract between the PO and Devs. "We will not bring that urgent PBI into the Sprint because it doesn't meet the DoR". An extreme example but we see the DoR cause these types of problems.

[@supergirls3985]

@@AgileforHumans Thanks Ryan and Todd (don't know who replied me lol). I do agree with you. But I do have the real life concern about it. I'm working for the government and as you know government has more rules than private sectors. If it's urgent and PO from business wants to include it to the current Sprint. But Developers say we have to analyze it to meet certain government rules, which are parts of DoR. My question 1 is How can you deal with that situation? Also, some Agilest promotes this DoR (which I don't like). For example www.leadingagile.com/2015/07/definition-of-ready/. My question 2 is if some organizations want to use DoR, is that ok? Thanks! --Junlong.

[@baertheblader9402]

Did you watch WandaVision? I thought it was good. I recommend it.

[@AgileforHumans]

WandaVision was really good! What's next?

[@lololima5533]

Just too many confusion in the agile body. Parts of the reasons executives can't trust agile wholeheartedly. One Agile Coach comes around, he coaches the teams of DoR, here comes another, he says "trash it". I use DoR, it's a living document with that team can change it whenever it's needed.

[@matthewhodgson1168]

I think for me the Definition of Ready fails because of how Sprint Review works. If in Sprint Review everyone collaborates on what to do next, then the DoR suddenly puts a gate in place which says no we can't pivot to do X or Y because it doesn't yet meet the DoR checklist. M (PST)

[@rolemodel99]

i go by goria morein's wishlist of ready, so that ready doesnt become a stage-gate.

[@rolemodel99]

DoR sometimes teams use it as a weapon and deterrent from overbearing stakeholders. agreed that collaboration that is fostered through trust and support works better for WoR.