In actual development, it often occurs that the members of the project team are not exclusive to this project team, but serve multiple project teams and switch between different project teams according to actual needs.
This is the case with my current project team. Project requirements analysis and research, system design, art design, and complex report business processing and development, etc., are all in charge of several specialized members in the middle of several project teams. Often there is a need to switch between several project groups.
In practice, however, these projects require members that do not require full-time commitment. Like DBAs and GUI designers, these projects don't completely take up all of their work time.
However, for the current project team, it is enough to use a relatively stable time for these members to switch project tasks.
The technical aspects they are mainly responsible for are consistent, and they are mainly switched on specific project business. The relatively stable time can be switched by weeks. From Monday to Friday, participate in an iteration of a project, ending on Friday.
However, in this way, the milestone setting of the project will be affected, and it is not suitable for setting in the middle of the week.
In this way, members can use the weekend as a time to rest and prepare for changing work content, which has better results.
Try to ensure that the members responsible for multitasking only complete the work of the same project a week, instead of doing two projects, so that the efficiency will not improve, but will be counterproductive.