Managing Bugs in Sprint - Feature Request

4 posts, 0 answers
  1. Liz
    Liz avatar
    7 posts
    Member since:
    Apr 2011

    Posted 20 Jun 2011 Link to this post

    Just as in Backlog Management, there's a need for Sprint Management (Current workload). 
    • The Story board & Task board don't show bugs that are assigned for the current sprint. 
    • Also there needs to be the ability to add tasks to Bugs.  Just like a story it can be worked on my multiple people.  Part of it can be tested early, while a secondary part of the bug is still being worked on.
    • The time associated to tasks from bugs should affect the burndown.
    • If bugs are associated to a User Story, it's helpful to show that relationship in the Sprint Management.
    • Have the ability to show a "work-in-progress" bug as another task, and be able to convert it to a bug, if it needs to be carried over.  Anything not fixed in the current sprint is now considered a bug.

    Personally I prefer a hierarchy approach rather than "Boards".  More information is managed in central location for a sprint.
    • Time left on tasks (Can view in one column).  Let's me know if someone needs help on a task or if it can be broken out.
    • Is there a blocker on the task, show with an icon without requiring extra steps of explaining why.  A comment can always be added.
    • Maybe you want to group multiple bugs to be fixed together with one user story.
    • One story could have multiple bugs "shake out", and you want to track it with the story.  It's easier to see them all grouped together in a linear fashion.


  2. Robert Régnier
    Admin
    Robert Régnier avatar
    1 posts

    Posted 23 Jun 2011 Link to this post

    Hi Liz,

     Thanks very much for the great feedback!

    "The Story board & Task board don't show bugs that are assigned for the current sprint"
    "Also there needs to be the ability to add tasks to Bugs.  Just like a story it can be worked on my multiple people.  Part of it can be tested early, while a secondary part of the bug is still being worked on."
    "The time associated to tasks from bugs should affect the burndown"

    Adding bugs to our board views and being able to assign tasks to them is part of our backlog, as is having tasks impact the burndown and not just story points.   I've noted your vote to include these features in a future release.

    "If bugs are associated to a User Story, it's helpful to show that relationship in the Sprint Management."

    Can you describe how you would like to see this relationship displayed?

    "Have the ability to show a "work-in-progress" bug as another task, and be able to convert it to a bug, if it needs to be carried over.  Anything not fixed in the current sprint is now considered a bug."  

    This is an interesting idea.  Our backlog includes the ability to convert entities from one type to another but converting a task to a bug in a good twist we'll add.

    "Time left on tasks (Can view in one column).  Let's me know if someone needs help on a task or if it can be broken out."
    "Is there a blocker on the task, show with an icon without requiring extra steps of explaining why.  A comment can always be added."

    Managing tasks one their own, independent of their parent story, is also in our backlog.  If I understand you correctly, you would like to see a Manage Tasks screen where tasks can be all be managed together in a grid.

    "Maybe you want to group multiple bugs to be fixed together with one user story."
    "One story could have multiple bugs "shake out", and you want to track it with the story.  It's easier to see them all grouped together in a linear fashion."

    Tracking bugs associated to stories is currently possible in TeamPulse by adding a relationship to a story from the bug editing view.  Navigating to story and then to it's bug tab will show you related bugs.  Can you describe in more detail the kind of view on story/bug relationships you'd like to see?

    I've granted you some points for the feature requests we've added to our backlog. :-)

    Kind regards,
    Robert Régnier
    the Telerik team
    TeamPulse R1 Officially Released!
    Do you want to be able to directly talk to our professionals and ask questions about the things that interest you?
    Reserve a seat for the TeamPulse Weekly Live Demo today!
  3. Liz
    Liz avatar
    7 posts
    Member since:
    Apr 2011

    Posted 24 Jun 2011 Link to this post

    I've attached a picture to hopefully convey the concepts.
    It would be an Iteration Management similar to what the Task board, and Story board, but include everything to manage that sprint in a more concise format.
    • For a Scrum Master, they have one place to see blockers, and it stands out with some sort of coloring or icon.
    • For Team Members, they can see there are bugs to start working on and that maybe what's blocking QA. 
    • Team members / Scrum Masters can compare the Estimate, To Do, and Actual columns for tasks that have grown, and that person may need some help, but afraid to ask, or ended up in a rabbit trail.  It may be a sign of scope creep, and need to create a new story.
    • The grouping of bugs shown on the Story help bring the visibility of the problems you are trying to solve.  It maybe "OK" to have stored just associated to the story and they can drill down to it.  But it also provides a way for the QA person to immediately close bugs instead of driling down to the story, then to the bug, and then put notes for closing it.
    • This also shows a rollup of how much work is left to do for a story. 
    • The tasks should be collaspable so you can focus on particular stories, or expand all to see all the stories.

    I worked for one company that would have bug sprints, just fixing bugs, and there could be 20-40 bugs in a 2 week sprint. This is hard to manage on a Task board or Story board.

    I don't think there's a need to manage tasks outside of Stories and Bugs.  I see tasks always associated to those Entities.

  4. Jordan
    Admin
    Jordan avatar
    123 posts

    Posted 28 Jun 2011 Link to this post

    Hello Liz,

    Thanks again for the detailed answer. It is very helpful. Actually when we were planning the backlog our idea was something similar to your suggestion. Backlog contains stories, tasks and bugs. Tasks estimates roll up to their parent story and you can compare the story estimate vs. task estimates.
    The idea to have different colors for different states is something that we didn't consider but we already have something similar for bugs.

    I'll add your additional information to our backlog.

    I have added some Telerik points to your account to compensate for your efforts.


    All the best,
    Jordan
    the Telerik team
    TeamPulse R1 Officially Released!
    Do you want to be able to directly talk to our professionals and ask questions about the things that interest you?
    Reserve a seat for the TeamPulse Weekly Live Demo today!
Back to Top