Skip to main content

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.

Is every request from customers counts as PBI even the scrum team doesn't going to develop?

Last post 05:55 pm November 1, 2022 by Ratnakumar Umavenkata Lekkala
5 replies
03:43 pm October 14, 2022

Dear Collegues,

I have a question and as the scrum masters on our company, we fall apart. We' ve got many projects and each project has also a support team. We are trying to find a better way to follow up customer requests. So, I' ve got a question. Is every request from customers counts as a PBI and stays at PB, even the scrum team not going to develop it ?

Thanks.


11:59 pm October 14, 2022

Why is the Scrum Team never going to develop it? How do you know for certain that it will never be developed?


06:00 am October 15, 2022

I have a question and as the scrum masters on our company, we fall apart.

That's because it may not really be a question for them.

Is there a clear Product, with exactly one Product Backlog, and exactly one Product Owner who is accountable for value? That's the person who ought to be able to explain what a PBI is, and the value it represents, and to whom.


12:12 pm October 19, 2022

Why is the Scrum Team never going to develop it? How do you know for certain that it will never be developed?

Actually, some requests doesn' t add any value to product. On the other hand, product infrastructure may not meet the request.


12:11 pm November 1, 2022

Actually, some requests doesn' t add any value to product. On the other hand, product infrastructure may not meet the request.

If the request does not add any value, then the Product Owner should not allow it to become a Product Backlog Item in the first place. Since the Product Owner is accountable for, among other things, creating and ordering Product Backlog Items, the Product Owner should also make sure that things that don't make sense to do never end up on the Product Backlog in the first place.

If something is valuable, but there are dependencies that need to be satisfied first, that doesn't change the nature of the request being valuable. It just means that you need to implement those dependencies, either as separate Product Backlog Items or as tasks to satisfy the Product Backlog Item. If it doesn't make sense to satisfy those dependencies, then see the first paragraph - the request doesn't add value (or the value is too low for the cost) and it should never be a Product Backlog Item in the first place.


05:55 pm November 1, 2022

Actually, some requests doesn' t add any value to product. On the other hand, product infrastructure may not meet the request.

That answers your question. Your Product owner can determine if any request adds value and add them to the product backlog. Developers can then work on these PBIs when they surface to the top of the ordered Product Backlog.


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.