Previous
¶ Team Setup
¶ What it is
Team setup is to determine the resources and team structure of all the people that would be involved in a product team.
¶ Why it is useful
Each team member has a different skill set. They may have multiple projects in parallel. They need to collaborate but may be located in different time zones. They take time off sometimes. In addition, the scope of a project is subject to change.
All these factors need to be taken into account when building a team to ensure the team has the capability to complete a project in an achievable timeline.
¶ When to use it
Once the project is confirmed, the team setup should be executed based on the requirements and the effort estimation. So the resources would be allocated appropriately, and all the team members would get involved in the project as soon as possible.
¶ How is it done
- Figure out the budget, timeline, tech stack or other required skill set of the project.
- Check the current capability of the team members by considering the potential upcoming projects. Determine if external resources (e.g. vendor) are needed.
- Select a structured team that covers all the roles needed in the project.
- Make a backup plan for catering the uncertain situations that may affect the timeline.
¶ Do's & Don't
Do's
- Record the assigned projects and workload of each team member, and keep it updated.
- Create a well-maintained vendor pool.
- Take the uncertainty into account.
Don't
- Do not rely on a single team member too much, if possible. Or it could be difficult to find a backup in case he/she is not available in the future.
¶ Tools needed
¶ Example
