[almighty] Relation between Stories and Bugs for the Planning
Michael Kleinhenz
kleinhenz at redhat.com
Wed Oct 19 14:36:55 UTC 2016
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
--
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
More information about the almighty-public
mailing list