Story Points: BOX or BOX CAR?

curiouswebster
curiouswebster used Ask the Experts™
on
I need to go through the backlog of bug fixes and features and make a quick assessment about the amount of effort involved. So a Story Point approach is obvious.

What kind of advice or procedure can you suggest I try and follow? The temptation is to dig into the details, since that produces more accuracy. And while I will add my findings to the notes, the idea is not for me to solve or architect the changes. I need to stay high level enough that I can get through the entire backlog list quickly.

So, any advice on how to do this?

Thanks.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Topic Advisor
Most Valuable Expert 2016
Commented:
Planning poker would be an option.
curiouswebsterSoftware Engineer

Author

Commented:
Yes, I have used that successfully in the past. In this case, it will be me and another guy, talking by phone.

We cold use Skype and have our number as input then count 1,2,3 enter and each sees the other's answer...
Gerwin Jansen, EE MVETopic Advisor
Most Valuable Expert 2016
Commented:
Planning poker is usually done with 4 (or more) people but I guess, 2 is a minimum :)
CPColinSenior Java Architect
Commented:
If you're going for pure speed, the two of you could take turns giving an estimate and the other person could say, "Sounds good!" or suggest a bump up or down. You can always revise the estimates later, once you have a little more time to think about the issue.
curiouswebsterSoftware Engineer

Author

Commented:
thanks

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial