When adding resources to Kelloo you can add them into your resource pool as either named resources or resource teams.


If you create a sprint, you can specify the sprint team which can consist of a mix of named resources and resource teams.


Read on to understand the differences and how each can be used.



Named resources


Named resources are individual people such as "Sarah Smith" and are assigned a role such as "Engineer".


Use this type of resource if you need to assign and track work against individual people.


When Kelloo reports data about things like work and utilization, it will be summarized under both the resource and the role they are in.



Resource teams


Sometimes you do not need to track or allocate work to individuals. If this is the case you can create your resources as teams. 


This makes it easier to set up your resources as you do not list the individual members of the team. Instead you just specify how many people are in the team.


There are two different types of resource teams you can create:


1. Team (role based)


With a role based team, you specify the number of people in the team and the team's role.


An example might be "Bob's Engineering Team" consisting of 5 people who are "Engineers"


Use this resource type if all the resources in the team have the same role.


When Kelloo reports data about things like work and utilization, it will be summarized under both the resource team and the role it is in.



2. Team (cross functional / agile)


Cross functional / agile teams are similar to role based teams, except they have no role assigned. An example might be "Mobile Product Team" consisting of 5 people.

Use this resource type if the team contains people with different roles or tracking work at the role level is unimportant. 




The resource pool


The resource pool is made up of your resources. 

Named resources and role based teams are organized under roles. Cross functional / agile teams do not have a role.


Here is an example resource pool in Kelloo showing a mix of roles, named resources and teams.





Considerations


Resource typeConsiderations
Named resourceUse this if you need to track and allocate work to individuals.

Has a role assigned.

Work will be summarized at the resource and role level.
Role based teamUse this if you don't need to track and allocate work to individuals.

Less data to maintain (you only specify the number of people in the team).

Has a role assigned.

Work will be summarized at the resource and role level.
Cross functional / agile teamUse this if you don't need to track and allocate work to individuals.

Less data to maintain (you only specify the number of people in the team).

Has no role assigned.

Work will be summarized at the resource level.