Imagine a typical project of a typical analyst.
After the analysis is completed, the analyst is considered to have finished his job, and is transferred to the next project. Hence, when real implementation starts, and massive questions arise, the analyst is fully occupied by his next initiative, and is not very happy of this distraction.
Professional distinctiveness, you say, nothing can be done, just relax and put up with this?
My talk will explain why it’s not a good idea, and describe some tips and tricks that can help to reduce the pain of context switching.