This question is locked. New answers and comments are not allowed.
I have two departments that started using TeamPulse recently and since 95% of the stuff they work on is small (an hour of work) they don't like creating a story and then creating a task since it is almost always a 1-1 relationship. But then I have two departments treating "stories" like tasks and two other departments using stories as they were meant to be used as containers for tasks.
Please advise on the best way to handle this.
Please advise on the best way to handle this.
1 Answer, 1 is accepted
0
What issues are you facing? Do these teams work on the same project? Is it that you want to track time on the work these teams do? Or you have issues with the reports that TeamPulse genereates from the existing data?
Many teams work exactly like you describe - each with its own preferences and workflos, and it is Ok. because introducing overhead (like making them create data that is not used after all) is not a good practice.
Many teams work exactly like you describe - each with its own preferences and workflos, and it is Ok. because introducing overhead (like making them create data that is not used after all) is not a good practice.