Make sure that principle of keeping interchangeable team members is preserved, i.e. in case there is anyone with unique skillset then there should be conducted proper onboarding sessions to share this knowledge to any other person capable of taking this area on. Also, it's useful distribute service ownership between different people while each person is responsible for the particular area while being accountable for the entire system context
Follow the phenomenon of the cross-functional T-shaped teams
Delegate tasks where there is no enough resources or power to cope with, i.e. no access rights -> make request to those who has permissions to fulfill the task, and make sure to request the same access for future same cases
Revisit team seniority pyramid and skillset -> replacements or rotations
Ensure that scope under refinement correspond to team skillset and setup, in case of deviation apply change management in resource plan
Keep Team Setup/Composition balance (skills ratio)
Reach balance between QA &
...
Dev resources
Make succession planning in order to mitigate bus factor
Create and support staffing plan (how we introduce people on the project, who does it and how), training plan (what KT to pass), procurement plan
Be aware of trending resource management methods (lean management, JIT, Kaizen, Theory of constraints, Emotional Intelligence, self-organizing teams) and apply them in practice
Create or enhance Team Charter to define or improve team values, agreements, and operating guidelines for the team
Use "smart staffing" approach when assigning people to the projects.
Ensure that physical resources assigned and allocated to the project are available as planned, as well as monitoring the planned versus actual utilization of resources and taking corrective action as necessary.
Useful materials
Common mistakes to avoid when staffing project team
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|