This question is locked. New answers and comments are not allowed.
I'm wondering what the best approach is for handling routine code maintenance? What do we log our time against? How should we track? A story? A task on a story that we push through each sprint?
For auditing purposes, every check-in that happens in our repo needs to be associated to some sort of teampulse "item".
From the definitions I have read, and please correct me if I am mistaken, but it seems like a story doesn't fit the criteria for code maintenance work. (how would you write that story? "I am a developer, so my code needs to be formatted correctly so it is easy read"?)
By maintenance I mean any of the routine tasks that a developer will typically perform on a code base throughout the projects lifecycle that isn't impactful enough to warrant a story or bug, but should probably be noted / tracked so we can see how much time is being spent, on say, fixing other developers lazy formatting vs. completing stories.
thoughts?
For auditing purposes, every check-in that happens in our repo needs to be associated to some sort of teampulse "item".
From the definitions I have read, and please correct me if I am mistaken, but it seems like a story doesn't fit the criteria for code maintenance work. (how would you write that story? "I am a developer, so my code needs to be formatted correctly so it is easy read"?)
By maintenance I mean any of the routine tasks that a developer will typically perform on a code base throughout the projects lifecycle that isn't impactful enough to warrant a story or bug, but should probably be noted / tracked so we can see how much time is being spent, on say, fixing other developers lazy formatting vs. completing stories.
thoughts?