We have a standard issue tracking system to track flaws / enhancements from a standard user and project management perspective. However, we also need to keep track of the flaws in the internal team, which may involve refactoring some code or changing something in the app which is not interacting with the end user
Is it a Is it best to keep track of these defects and enhancements in the tracking system? My reservation with it is that the project manager who sees the user's flaws will be confused with these internal requests and will cause unnecessary worry. Are we standing another fault tracking system for the use of internal team?
Low system is always (almost) always better, as long as you take away from the time of coding Enjoy additional administration.
I like that the decisive tracker separates these things from which you are talking to confusion, and to keep a clear focus on the customer. User flaws are "worms", internal objects that do not have visible customer benefits, they are "work" and do not appear in many ideas because they do not distribute customer value (no user is not a story).
So I would think that most of the issues trackers have ways to break the type of issues and I differentiate "paying technical loans" with different bugs.
You should also consider why you do not know about the project manager. You have to reserve these methods again in such a way that it becomes clear why this work should be done. Therefore instead of "Refactor User Authentication", "Increase user maintenance system maintenance", or whatever work is the underlying goal.
Obviously, there is a need to provide business value to every technical work and think about how it will be saved (besides "my code is more elegant") a good practice.
Comments
Post a Comment