Teams

Teams are the basic sections of an agile framework. They are the groups of people that complete work items. Information about each team should be kept on file to keep track of who controls the team, who is in the team, how to contact them, what type of team it is, what the team is for, and how quickly it completes work items.

The section explaining who controls the team should include the team manager and the team owner. This section is important because it keeps track of who needs to be informed or consulted if the team is changed, or if the team needs to change.

The second section should list team members. It should include the team member, their job on the team, and how many hours they are available to work with the team. This section is important because it keeps track of roles on the team, and how available the different team members are. A member who is only working part time on the team will not be able to complete as much work as one working full time.

The third section should include different ways of contacting the team. It may include a telephone number, fax number, or email. This section should contain the information for the team manager, because they will be able to get in contact with the rest of the team. Furthermore, keeping track of the information for each member would be difficult and is unlikely to be used. This section is important because it explains how to contact the team manager when the team is changed.

The fourth section should say what kind of team it is. Examples of team types are portfolio and project governance teams, who prioritize work items at the portfolio and project level, and agile teams, who complete work items. The type of team is important because it records the team capabilities and what level of work items the team can prioritize or complete, so it affects the type of work items assigned to the team.

The fifth section should explain what the purpose of the team is. This section should mention the type of work that the team should do and why the team was created. It is important because it creates consensus on the team's purpose and keeps track of what the team should be doing. What the team should be doing can be compared with what the team is doing, to keep it on track.

The sixth section should keep track of how quickly the team completes work items. It should include the team's velocity, which is the number of points it completes per iteration, and the length of iterations that the team uses. This section is important because it keeps track of how much work the team is expected to do in a certain amount of time and is used to plan iterations.

The information about teams should be recorded and edited whenever there is a change to the team. This allows the business to keep track of what the team is doing, and how the team is changing. This information can be used to assign work to the team, making sure that the right kind of work is assigned.