Back to Forum

Technical Stories & PBR

Last post 02:13 pm August 30, 2018 by Ian Mitchell
1 reply
Alan Evans
10:33 pm August 29, 2018

Hi,

I've got a Team that have a large number of Stories that are very technical in nature. When it comes to Product Backlog Refinement Sessions, they won't give even a rough Story Point Estimation to these Stories. Instead, they prefer to have one or two 'Technical Discussion' meetings, lasting around 45 minutes, to flesh out the technical details of each Story, and then only estimate come Sprint Planning time.

I don't think this is the best way of doing this, as it means that valuable time is taken up during the Sprint dealing with fleshing out these details, and that the Stories themselves become more a Technical 'To-Do' list, rather than a 'proper' story. I think that possibly putting these more technical stories into a Spike and then processing them as part of a Sprint would be a better way, but I'd be interested to hear what others think on how to deal with these?

Cheers

Ian Mitchell
02:13 pm August 30, 2018

The Product Owner owns the Product Backlog, and must be able to value and order the work described on it. Is the PO able to do that satisfactorily, and how is he or she accounting for the amount of work which remains to be done?

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.