Skip to main content
Project Management

Return to Question

Clarified question and converted to Q&A format; modest grammar and semantic edits throughout; retagging.
Source Link
Todd A. Jacobs ♦
Todd A. Jacobs ♦
  • 50.7k
  • 7
  • 60
  • 181

Time limited minor How should we handle a 10-15 minute time-limited bug on a Scrumban board?

During the planingplanning, our product ownerProduct Owner introduced a bug to the development teamDevelopers and said: "let's, "Let's take this bug and see if we can fix it quickly otherwise. Otherwise, let's put it back toon the backlog"backlog." I have asked what youthe Product Owner mean bytby saying "quickly""quickly," and she said "within 10-15 mins"minutes."

Now I want to understand what is the correct way to handle this kind of bugs because as muchbug. As far as I know, neither in Kanban nor in Scrumban there ishas a way to bring a story or a bug to sprintinto Sprint with time limit andlimits or a way to drop it onsuch an item into the work flow halfway through if it iswill not completebe completed within the frameworks of the specific timeSprint.

P.S. I know about time limited Spikes-limited story spikes, but those are usually research tasks which are not meant for 10-15 mins solutions.

Time limited minor bug on a Scrumban board

During the planing our product owner introduced a bug to the development team and said: "let's take this bug and see if we can fix it quickly otherwise let's put it back to the backlog". I have asked what you mean by saying "quickly", she said "within 10-15 mins".

Now I want to understand what is the correct way to handle this kind of bugs because as much as I know neither in Kanban nor in Scrumban there is a way to bring a story or a bug to sprint with time limit and drop it on the halfway if it is not complete within the frameworks of the specific time.

P.S. I know about time limited Spikes, but those are usually research tasks which are not meant for 10-15 mins solutions.

How should we handle a 10-15 minute time-limited bug on a Scrumban board?

During planning, our Product Owner introduced a bug to the Developers and said, "Let's take this bug and see if we can fix it quickly. Otherwise, let's put it back on the backlog." I have asked what the Product Owner mean tby saying "quickly," and she said "within 10-15 minutes."

I want to understand the correct way to handle this kind of bug. As far as I know, neither Kanban nor Scrumban has a way to bring a story or a bug into Sprint with time limits or a way to drop such an item into the work flow halfway through if it will not be completed within the Sprint.

P.S. I know about time-limited story spikes, but those are usually research tasks which are not meant for 10-15 mins solutions.

Source Link
Narek
Narek
  • 255
  • 2
  • 8

Time limited minor bug on a Scrumban board

During the planing our product owner introduced a bug to the development team and said: "let's take this bug and see if we can fix it quickly otherwise let's put it back to the backlog". I have asked what you mean by saying "quickly", she said "within 10-15 mins".

Now I want to understand what is the correct way to handle this kind of bugs because as much as I know neither in Kanban nor in Scrumban there is a way to bring a story or a bug to sprint with time limit and drop it on the halfway if it is not complete within the frameworks of the specific time.

P.S. I know about time limited Spikes, but those are usually research tasks which are not meant for 10-15 mins solutions.