Loading Profile...
EMPLOYEE
Chores should represent Code Debt and put a project "In the red."
On many projects, especially with large codebases, Chores are created for refactorings, technology changes, cleanups, etc. Every Chore could have a debt-amount, -1 maybe for simplicity. With 3 Chores, you are -3 in debt. Add 10 Chores and you are now -13 in the red.
This Code Debt concept would help communicate to project customer the reason for and value of Chores that often don't make sense. While it is true that Agile promotes engineers making engineering decisions, Chores-as-debt could communicate the value of those engineering decisions, or more appropriately, communicate how those engineering actions will improve the product even if there is no business-facing changes.
This Code Debt concept would help communicate to project customer the reason for and value of Chores that often don't make sense. While it is true that Agile promotes engineers making engineering decisions, Chores-as-debt could communicate the value of those engineering decisions, or more appropriately, communicate how those engineering actions will improve the product even if there is no business-facing changes.
I’m excited
1
person likes this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
-
Inappropriate?Cool -- but if we do this can we have some sort of neutral story.. I like to use chores for design stories since they don't mess with the development velocity.
I’m happy that everybody wants a tracker feature
-
Inappropriate?Yes, chores-as-chores are a very good thing. Perhaps what is needed is a new concept, a Code Debt concept that is an options just like chores, features, etc.
EMPLOYEE
