Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
We refer to that as "Context-Switching" in our group and it's indeed very dread-upon by any devs in our team.
When we plan the sprints with the team, we try to keep the task of the same type to the same person to avoid "context switching" as much as possible.
In our group, there's 2 types of "context switching" :
Avoidable Context Switching (Usually caused by bad planning)
Unavoidable Context Switching (Usually caused by support)
The unavoidable cannot be planned since it's caused by end-users interruptions, the way we handle those if by dedicating someone to end-users support in a sprint, meaning that we know that person is going to be less efficient, so we plan accordingly for him/her. For the avoidable one, it's the responsibility of both the employee and the sprint owner to make sure they handle that properly.
