Product backlog. Let's talk about these major Scrum artifact. So product backlog, it's a kind of holies of items. And not always user stories. We have just in our illustration user story, but not always, actually, product backlog is ever since it doesn't own involves the product. And of course, the loose least shouldn't be prayer diced, and they will wait.

In our case, we see example whole Asian story points. But that's just one of the way to operate as a product backlog items. So some teams could evaluate in hours in mandates and so on. And so there are multiple ways to make evaluation. This illustration is predefined but that's only one of the way how this could be done. Well, let's look at Bollinger Bands basic characteristic of the product backlog.

So product backlog He's a prescribed Scrum artifact. So, when we are saying prescribed, we always considers at least one data artwork. Product Backlog is equal to the product development plan. So it's absolutely correct the way how equals is fallen. So, Product Backlog contains ever since it is known about product development, and it's prioritized count is actually in that way equal to the product development plan. So, final point is it one product backlog is dedicated to one product.

So what we are saying here is that we should avoid situation one, there is multiple product backlogs and one product because there will be a number of issues, dependency issues, issues, we discard donation amount This is not good approach. To use multiple backlogs for one product, so ideally, or good, standard practice is to hear just one single product for one single broadening book. So let's talk about product backlog and details. And the first is to review their true statements regarding the product as well as it's true that product managers tend prioritized by as a product owner sells that's absolutely correct. As a product owner solely responsible to manage the product backlog and product owner have final say on it. It actually at least include Saul's aspects, regardless of product backlog management, but there could be a few points.

The first point is that product owner could allow to the development team to manage the product backlog as well. But in this case product owner should clearly define and adjust the approach that will be used it so that the development team could use this approach and do not distract ever since that is related to product backlog management. Also, it's very important that the product owner explained to the development team to the scrum master to the stakeholders as they approach it to use it for back look, management. So that's another very important point. What if to summarize the statement that it's absolutely correct product owner manage and purge is broken? That's correct.

Well, that's my one. eats Drew's at Bing but look can be updated or adjusted to anytime. Yes, that's absolutely correct. product owner could add new items to the product backlog or removes items from the product backlog. Whenever he or she wants to do this it's Drew's that development team is responsible for estimation of work. That's absolutely correct.

And this is general approach that how our work should be evaluated by someone who actually is going to do this work. So in our case, the role of my team will do the work and it's why is the development team should evaluate or estimate the work he's Drew's a technical dependencies could have an impact on the order as a product backlog. Yes, that's also correct. product owner may not be happy overseas, but sometimes this happens. For example, product owner may want to create registration We have social networks and my health is a development team to do this, but they could explain to the product owner that they can't do it now because first of all, they need to do a regular registration and all after that they can do registration, we are social networks. This is just URL example.

But there could be many other points are actually holding this because it will force the product owner to order the product backlog items in particular way because of technical dependencies. So this statement is true. So wherever you improve statements involves a product backlog. Now let's talk about incorrect or false statements regarding the product backlog. It's false statements that during the sprint planning a new member of the development team could take ownership over the product backlog item This statement is not correct. It's false.

And the reason is why because we always consider that responsibility belongs to the entire development team. Even if it's sprint planning event, even if product backlog item has been completely done by a particular member, in all the cases will always consider that responsibility belongs to the entire development team. And because of that, a particular team member could never be the owner of the particular product backlog item. So this statement is false. It's false that brawling backlog items should be ordered from the top to bottom, whereas the most valuable items is the top and the less valuable items at the bottom. So we're old this approach makes sense and some product owner works according to this approach.

They actually use this approach so they put the most valuable items to the top and the less valuable to the bottom but itself statement is not correct. And the reason is why because a product owner should decide which approach shouldn't be used. So for example, for one product owner, this approach is applicable 1401. It's not applicable. So therefore, we count the actual assays if this statement is true. So once again, it's up to the product owner to decide on the approach to order the product backlog items.

It's false statements that if multiple teams works on the same product, as they should use separate product backlogs, where each team refer to its own product backlog. So this statement is not correct. And we know that for one product, we should have one product backlog. Even if multiple teams working on the same product is they should always refer to a single product backlog. Otherwise there will be problems. We see management of work and synchronization between multiple product backlogs so this statement is not correct.

Let's move on it's false statements that prompting backlog refinement or grooming in other words should be limited to prescribes Chroma West. So, we have four prescribes Chroma lens and normally we will not be able to refine or groom our backlog your exam. So, we will need to spend more time around done percentage of time allocation for this requirement or grooming activity. So, the statement is not correct, because we should never limit team requirement or grooming activity to the prescribed a once is false that product backlog should only contains a user stories. That's not correct. Product Backlog is ever since it is known about the product, including user stories, other issues, marks and so on.

So the statement is not correct. It's false statements, the development team should estimate work in house cars is only one of many ways to estimate the work. We of course can use hours for estimation, but the statement is false because there are many other ways to estimate the work, which is applicable for Scrum as well. So we already viewed one of their major artifacts. It was a product backlog, he prescribed Scrum artifact. Now let's talk about the next artifact which is sprint backlog.