Re: Backlog of technical tasks?
- --- In email@example.com, "Stephen Bobick" <sbobick2@...> wrote:
>I have no issue with making things visible. I think that transparency/visibility is good and
> If the organization ignores the Team repeatedly - a Team who predicts
> failure if they aren't listened to regarding technical debt and an
> unmaintable code base, and the organization drives the Team over a cliff,
> well, why not point that out?
healthy for teams and I would encourage that. We are in violent agreement on this point.
I do however have an issue with finding fault. The quote from Mike D "When it crashes
down you will have the documentation to help management find a new PO," read (to me)
as if as thought he was advocating using the Backlog to attribute fault should a project
not work out. This is something that I don't agree with because, when projects go bad, I
believe it's everyone's responsibility.
Having said all that, I could well have interpreted Mike's words incorrectly, or considered
them out of context, which is why I asked the questions that I did.
- --- In firstname.lastname@example.org, "Jeppe N. Madsen" <jeppe@...> wrote:
> I've been skeptical about putting technical tasks on the backlog forYes, and there's really no contradiction between these
> many of the same reasons listed in this thread. I think we should
> make "the world a better place" one step at a time, by refactoring the
> code as it's touched due to new requirements.
approaches once we see the Sprint Planning Meeting
as a good faith negotiation.
Normal technical debt should be paid off through
the definition of "done" for product feature stories.
Things like this might include refactoring away
duplicate code, complex conditional logic, long
modules, nested "catch" blocks, poorly named
methods and classes, normal database schema
changes, normal upgrades to third-party
> If there really are technical debt that hindersYes, when progress on multiple fronts is impeded
> progress, this is an impediment.
by severe fundamental underlying debt issues
(often at the infrastructure level, like platform
changes, major database changes, major library
changes) it may be useful for the team to make
it visible in the product backlog as a step toward
breaking the repayment work into manageable
pieces. Anyone can add items to the Product
Of course we still expect some feature delivery