How do you track the team progress/efficiency in a fast-paced environment? I have seen priorities shift drastically making developers switch context way too many times to keep up with the shuffles. In these scenarios, it becomes tricky to track time spent vs work done. We brought in the concept.of ticket score, and measuring it during the retros. however, it helps only so much! Could you suggest how you would have tackled this?
Efficiency is hard to track in advance when every task is really unpredictable.
We have a roadmap and everyone has ownership about its high level milestones, but success is rather tracked by the engagement of our users and the retention of the users who came with the announcement of the feature (ofc, also tested, documented..).
You have to go out with your project as soon as possible to get feedback, even if your solution is very far from done or even good, only this way you can see if you are building the right thing.
There are systems and frameworks like scrum which allow tracking at a lower level, but they can only bring benefit if you already have a product and can pretty much define what needs to be done and how.
We are basically forced to trust in everyone to do their best and can only help to make the right decisions.
The team has such a high level of ownership about the codebase, no one's work gets unnoticed.
Does this help?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How do you track the team progress/efficiency in a fast-paced environment? I have seen priorities shift drastically making developers switch context way too many times to keep up with the shuffles. In these scenarios, it becomes tricky to track time spent vs work done. We brought in the concept.of ticket score, and measuring it during the retros. however, it helps only so much! Could you suggest how you would have tackled this?
Efficiency is hard to track in advance when every task is really unpredictable.
We have a roadmap and everyone has ownership about its high level milestones, but success is rather tracked by the engagement of our users and the retention of the users who came with the announcement of the feature (ofc, also tested, documented..).
You have to go out with your project as soon as possible to get feedback, even if your solution is very far from done or even good, only this way you can see if you are building the right thing.
There are systems and frameworks like scrum which allow tracking at a lower level, but they can only bring benefit if you already have a product and can pretty much define what needs to be done and how.
We are basically forced to trust in everyone to do their best and can only help to make the right decisions.
The team has such a high level of ownership about the codebase, no one's work gets unnoticed.
Does this help?