Forums

By posting to our forums you are agreeing to the Forum terms of use.
Do somebody apply scrum on Bug-fix project?
Last Post 26 Sep 2013 07:31 AM by Chee-Hong Hsia. 3 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
magicduan
New Member
New Member
Posts:1
magicduan

--
22 Sep 2013 04:18 AM
    Hi,

    I have a project which mission is to solve bugs in Phone system. The bugs are coming from Bug system everyday, my team mission is fixed them. Do somebody have experience to apply scrum method on this type project? How can I define Product backlog and sprint backlog?

    Any Suggestion?

    Thanks.

    Duan
    Chee-Hong Hsia
    New Member
    New Member
    Posts:61
    Chee-Hong Hsia

    --
    22 Sep 2013 05:48 AM

    Posted By magicduan on 22 Sep 2013 05:18 AM
    Hi,

    I have a project which mission is to solve bugs in Phone system. The bugs are coming from Bug system everyday, my team mission is fixed them. Do somebody have experience to apply scrum method on this type project? How can I define Product backlog and sprint backlog?

    Any Suggestion?

    Thanks.

    Duan


    Hi Duan,

    What kind of bugs are we talking about? Operational bugs that randomly comes which makes the priority fluctuate, needs to be fixed and put in production a.s.a.p.?

    If that is the case, perhaps you should check out Kan Ban?

    It is not a good idea to use Scrum just for the sake of using Scrum. The goal is to be Agile and there are any other methodologies to enable Agility.

    Cheers, Chee-Hong


    Ian Mitchell
    Advanced Member
    Advanced Member
    Posts:571
    Ian Mitchell

    --
    23 Sep 2013 06:36 AM
    Using Scrum for everyday defect fixing implies that you have a Product Owner who can prioritize each of these defects on a backlog, and help the rest of the team plan them into a Sprint Backlog with a meaningful Sprint Goal.

    Is that a realistic prospect in your situation? If not, you might want to consider Kanban as Chee-Hong suggests. In my experience, Kanban is well suited for Business As Usual (BAU) work such as templated changes and defect fixes. Scrum is well suited for project work where there is greater scope uncertainty to be de-risked, and where backlog items are more likely to align to Sprint Goals and the corresponding potential release of business value.

    Chee-Hong Hsia
    New Member
    New Member
    Posts:61
    Chee-Hong Hsia

    --
    26 Sep 2013 07:31 AM
    I do strongly believe that once a team adapts Scrum to its fullest, Kan Ban is like the next step in terms of becoming Agile. I see that happening to the last couple of companies that I have been coaching. It is quite an interesting transformation from a organisational point of view.

    Once the team starts deliver increments in a steady pace, has a stable velocity and product ownership has been applied correctly, the whole idea of a Sprint becomes more and more irrelevant. At some point, it is not about “which high value items can a team deliver in a Sprint” but more towards “which item has the highest value that can be delivered first”.

    For me Kan Ban is like the next step in Agility, but unfortunately it’s not implementable for every situation. I’m just happy that I had the opportunity to coach these kind of transformations.
    You are not authorized to post a reply.


    Feedback