Forums

By posting to our forums you are agreeing to the Forum terms of use.
Backlog containing mostly bugs
Last Post 18 Feb 2014 01:17 PM by Joshua Partogi. 6 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Mircea
New Member
New Member
Posts:7
Mircea

--
17 Feb 2014 08:05 AM
    Hello,

    My team has to work with a product backlog that contains lot of bugs most of them legacy but also bugs that are coming from late testing stages (bugs identified after one month or so after feature complete). We were advised to not provide story points for these bugs as the story points are reserved for new features. However, if do not provide story points it will be difficult for us to estimate a velocity.

    Which is the best way to handle the estimations in this case? Currently, for a bug we are estimating only the number of hours that are required to fix it. We are using Rally as Agile tool so for each story we can have both story points and hours.

    Thanks,

    Mircea
    Ian Mitchell
    Advanced Member
    Advanced Member
    Posts:562
    Ian Mitchell

    --
    17 Feb 2014 09:21 AM
    > We were advised to not provide story points for these bugs as the story points are reserved for new features

    Who advised you of this? In Scrum the Development Team is responsible for the estimation of its own work. If these bugs represent work that the team is expected to do, then they must be in a position to estimate it, and no-one has the authority to forbid the team from doing so.

    > Currently, for a bug we are estimating only the number of hours that are required to fix it.

    For bugs that are raised in-sprint a defect can be raised as a task against the story. It's reasonable to estimate tasks in hours.

    For bugs that are raised out-of-sprint (i.e. against work that has already been accepted as Done), the defects should be triaged into the Product Backlog and ordered, assuming they do not represent P-Level incidents that require immediate attention. They shoud be estimated the same way as other PBI's (e.g. by story points).
    Mircea
    New Member
    New Member
    Posts:7
    Mircea

    --
    17 Feb 2014 10:12 AM
    Thanks Ian! Very clear answer.
    Charles Bradley
    Basic Member
    Basic Member
    Posts:212
    Charles Bradley

    --
    17 Feb 2014 11:13 AM
    Hi Mircea,

    As a Scrum Coach, I get asked these questions all the time.

    Note that in the post below, if it ends up on the PBL then you would assign whatever units you use to estimate PBI"s, but if on SBL, then whatever units you estimate for items on the Sprint Backlog.

    http://ScrumCrazy.com/bugs

    Note that the above approach is just one approach. Scrum simply dictates that PBI's and items on the Sprint Backlogs have some way of being estimated. It is up to the Scrum Team to decide how that is done.
    Bhuvan Misra
    New Member
    New Member
    Posts:19
    Bhuvan Misra

    --
    18 Feb 2014 04:43 AM
    # Task Items can be sized in Ideal Hours.
    # Backlog Items or User Stories can be sized in (Story) Points.

    Based on how The Development Team is looking at a particular bug, it could end up being an Item or a Task. This selection will govern the unit of size.
    Bhuvan Misra
    New Member
    New Member
    Posts:19
    Bhuvan Misra

    --
    18 Feb 2014 04:50 AM
    Task Items = Task in above post!
    Joshua Partogi
    New Member
    New Member
    Posts:98
    Joshua Partogi

    --
    18 Feb 2014 01:17 PM
    Hi Mircea,

    Scrum doesn't differentiate between Bugs and User Story, both are considered as Product Backlog Items. With that rules applied that means I can also assign points to Bugs?
    You are not authorized to post a reply.


    Feedback