Comments on: How Detailed should the Product Backlog be? https://www.romanpichler.com/blog/product-backlog-right-details/ Expert Training & Consulting in Agile Product Management Mon, 07 Mar 2022 15:30:07 +0000 hourly 1 https://wordpress.org/?v=6.7.1 By: Guilhem https://www.romanpichler.com/blog/product-backlog-right-details/#comment-2629 Wed, 19 Aug 2015 08:30:23 +0000 http://www.romanpichler.com/?p=9505#comment-2629 In reply to Roman Pichler.

Many thanks! Common sens indeed but helpful to read!

]]>
By: Roman Pichler https://www.romanpichler.com/blog/product-backlog-right-details/#comment-2628 Tue, 18 Aug 2015 14:58:53 +0000 http://www.romanpichler.com/?p=9505#comment-2628 In reply to Guilhem.

Thanks for your feedback and your question Guilhem. I like to suggest the following rule: If an idea is helpful to achieve the release/product goal then it should be captured in the product backlog. If that’s not the case but the idea helps progress the product in the future, then capture it on the product roadmap. Otherwise forget about it. If it turns out to be relevant in the future, it’ll come back to you. Hope this helps.

]]>
By: Guilhem https://www.romanpichler.com/blog/product-backlog-right-details/#comment-2627 Tue, 18 Aug 2015 14:55:25 +0000 http://www.romanpichler.com/?p=9505#comment-2627 Hi Roman and thank you very much for all your articles and precious information!

A question is still popping up without any good answer. What about all the ideas that cross our POs/PMs life. Everyone has a good idea and we receive tones of it.
So either it’s an actionable one and it will be in the “short term” backlog or, if it’s just an idea, and we forget it (at least to follow it up correctly and to give feedback to the person who gave it)

I have in mind this sentence saying that “if it’s really important, your customers won’t let you forget it. (37 signals)”

]]>