Review comments(not a defect/bug)/Recommendations can be part of product backlog
Hi Team,
Can you please suggest review comments(not a defect/bug)/recommendations can be part of product backlog.
Regards
Bala
Hi,
Stake holder review feedback can be part of product backlog.
Thanks,
Beenish
Can you please suggest review comments(not a defect/bug)/recommendations can be part of product backlog.
Do they describe any work which the Product Owner values and which still remains to be done?
I may be wrong, but in my opinion everything - from user stories to retrospective action items tasks - can be part of the product backlog.
@Ian - are you saying there has to be value for the PO in order for an item to be listed in the PB? My understanding (and practice) has been quite different
are you saying there has to be value for the PO in order for an item to be listed in the PB?
I think that would be a fair comment, in so far as the Product Owner is responsible for maximizing the value of the product, and the sole person responsible for managing the Product Backlog.
Hi Bala,
According to me yes..it can be listed as part of PB to have in concurrence with PO. However the team has to strategies on how the prioritization will be done for the comments or recommendations
Thanks for providing your views on maximising value on product backlog.
Different question If I have any internal defects during inspection from Dev Team.How the traction will be applied in real time scrum projects to fix the internal defects.
If I have any internal defects during inspection from Dev Team.How the traction will be applied in real time scrum projects to fix the internal defects.
Do these “internal” defects mean additional work must be performed during the Sprint in order to create a Done increment of release quality? If so, is there any reason for the Development Team not to replan the Sprint Backlog accordingly?
It's a rework to get the outcome when you have internal defects.Until outcome does not have internal defects and meet DOD it can't move done increment.However my question is if I have internal defects as a scrum team how would I handle the traction to produce done increment.Any examples will be helpful on some testing defects.