[almighty] Relation between Stories and Bugs for the Planning

[Michael Kleinhenz]

@adam yes, and the order of execution of bugs is normally directly
determined by the severity of the bug.

For later, we have to define other processes anyway for bugs appearing
in production. We're building a b2c product, so we have to have
something in place to deal with high-severity bugs that require
immediate action. But that's possibly even a different team then, like
in a SLA scenario.

-- Michael

On Thu, Oct 20, 2016 at 3:46 PM, Adam Jolicoeur <ajolicoe at redhat.com> wrote:
> Agreed - as one who files bugs, I’m not expecting them to take priority over
> anything already in the Sprint. Rare cases may call for something to be
> triaged quickly, but I have never felt that bugs are always a ‘do this now’
> type of item.
>
> -Adam
>
> On Oct 20, 2016, at 5:47 AM, Ranjith Varakantam <rvarakan at redhat.com> wrote:
>
> Same goes for research activities (Spikes). We need to define a Story when
> our aim or goal is to answering a question or gathering information and
> schedule it in a Sprint just like any other story along with estimation.
>
> 1. We should clearly define it the acceptance criteria, in this case what
> are we trying to find out and to what degree of confidence
> 2. Also time box it. That is to say that we will spend a maximum of 2 days
> on it and make a decision based on that information.
>
> Ranjith
>
> On Thu, Oct 20, 2016 at 12:58 PM, Thomas Mäder <tmader at redhat.com> wrote:
>>
>> What he said. Same with "technical debt tasks". Let's do it!
>>
>> /Thomas
>>
>> On 10/19/2016 04:36 PM, Michael Kleinhenz wrote:
>>>
>>> Hi,
>>>
>>> because this topic was popping up in today's plannings. My 2ct on bugs
>>> vs. stories in the planning process:
>>>
>>> Usually bugs are treated like stories in the planning process. They
>>> should be part of the backlog and should be part of the order of
>>> execution. They should also be estimated and placed into sprints like
>>> stories. In an ideal case this leads to a backlog that consists of
>>> stories ("new features") and bugs ("debts") that are treated equal in
>>> terms of planning an iteration.
>>>
>>> Comments?
>>>
>>> -- Michael
>>>
>>
>> _______________________________________________
>> almighty-public mailing list
>> almighty-public at redhat.com
>> https://www.redhat.com/mailman/listinfo/almighty-public
>
>
>
>
> --
> Ranjith Reddy V.
> Agile Coach
> _______________________________________________
> almighty-public mailing list
> almighty-public at redhat.com
> https://www.redhat.com/mailman/listinfo/almighty-public
>
>



-- 
Michael Kleinhenz
Principal Software Engineer

Red Hat Deutschland GmbH
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany

RED HAT | TRIED. TESTED. TRUSTED.
Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht München,
HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
Michael O'Neill