A team is a collection of roles on a project. You can divide the people on a team into two categories: scheduled members and nonscheduled members.

Scheduled team members are those people for whom you want to track the hours, utilization, and financial impact (costs, revenue, and margin). Your scheduled team members for a project can also be referred to as the delivery team. Nonscheduled team members of a project comprise the extended team and include project team members whose time is not specifically tracked.

Subteams enable you to classify your people on your project into logical groups. For example, you may have resources on a project that you can group into consultants, administrative staff, and engineers, or, you may have people grouped into
subteams for different phases of a project.

For a project, you can enter general staffing information such as the default calendar, role list, initial team template, and advertisement rules. The role list controls access for the roles that you can add to your project. The initial team
template indicates the name of the team template that was used to create requirements on the project upon initial project creation.

The advertisement rule controls the visibility of requirements both inside and outside of the organization. Oracle Projects comes seeded with a project manager role, and requires that you designate one project team member as a project manager. While you can have only one project manager at any point in time, you can change the project manager role
assignment as necessary.

Note: Approved contract projects must have a project manager for the duration of the project. A project manager is not required for indirect projects or capital projects.

You can also define people as team members in order to facilitate distribution of Projects reports to responsible parties

Project/Team Roles
A project role is a collection of default information about a team member assigned to a project, such as competencies, job information, and security. You create project roles to represent the typical team member roles needed for projects within your organization.
Examples of project roles include project manager, project administrator, database administrator, and consultant. Each role can have a different set of competencies, job information for forecasting and menu to control security access to projects.

A team role represents either a requirement or an assignment on a project or task. You use the project role as a template for your team roles. When you create a team role, you specify the project role from which to obtain all the default information. The default information is copied from the project role to the team role. Thereafter, you can modify the information on the team role as appropriate for that role on that particular project. Any changes you make to the team role are exclusive and do not affect the definition of the project role.

For example, you have a project role called DBA. You create a team role on a project called Lead DBA based on the DBA project role. All the defined competencies, job information, and security information is copied from the DBA project role to this new Lead DBA team role. You decide to add more competencies to the Lead DBA team role and to change the job level. These changes are only reflected on this particular team role.

Each project role has a security structure determining the features users can access and the functions they can perform. This security structure is referred to as role-based security. Though role-based security is optional, it offers you more flexibility than responsibility-based security because the role of a user can change from project to project. Therefore, the function access a user may require can change from project to project. For more information on security,
In the application, the team role is the value displayed on most pages. The project role is only available on the assignment and requirement details pages.

Creating Team Roles
Oracle Projects provides two ways of creating team roles for your project, and they relate to how you staff your project and assign resources to tasks:

• Adding a Requirement: When you define a requirement for a scheduled resource, you also create and define a team role based on a project role. You can then create a project assignment for the requirement once you find a person resource that is appropriate for it.Adding a requirement is also the first step in the "top-down" staffing method, which you can use in conjunction with Oracle Project Management. With top-down staffing, you can create a set of project roles, and then have the system generate a planning resource.
• Creating a Team Role from a Planning Resource List: You can generate team roles based on resource assignments that utilize a planning resource list. This is part of the "bottom-up" staffing method, which you can use in conjunction with Oracle Project Management. With bottom-up staffing, you assign planning resources to tasks in your project and then generate project team roles for those resource assignments.

Role Lists

You use role lists to categorize your roles into logical groupings. Role lists enable control and ease of use when you assign team members to a project. For example, you may have a role list called Consulting to which all roles relating to consulting are assigned.