Interface TeamProfile

All Superinterfaces:
BreakdownElement, Classifier, DescribableElement, Element, org.eclipse.emf.ecore.EObject, MethodElement, NamedElement, org.eclipse.emf.common.notify.Notifier, PackageableElement, ProcessElement, Type
All Known Implementing Classes:

public interface TeamProfile
extends BreakdownElement
A representation of the model object 'Team Profile'. A Team Profile is a Breakdown Element that groups Role Descriptors or Resource Definitions defining a nested hierarchy of teams and team members. Work assignments and Work Product responsibilities can be different from Activity to Activity in a development project. Different phases require different staffing profiles, i.e. different skills and resources doing different types of work. Therefore, a process needs to define such different profiles in a flexible manner. Whereas Core Method Content defines standard responsibilities and assignments, a process express by a breakdown structures needs to be able refine and redefine these throughout its definition. Role Descriptors, Resource Definitions, as well as Team Profiles provide the data structure necessary to achieve this flexibility and to provide a process user with the capability to define different teams and role relationships for every Activity (including Activities on any nesting-level as well as Iterations or Phases). Hence, in addition to the work breakdown and work product breakdown structures defined so far, Team Profiles are used to define a third type of breakdown structure: team breakdown structures. These are created as an Activity specific hierarchy of Team Profiles comprising of Role Descriptors and Resource Definitions. These structures can be presented as well-known Org-Charts. Just as with any other Breakdown Element and Descriptors, Team Profiles can be defined within the scope of any Activity in a breakdown structure. In other words every Activity can define its own Team Profiles consisting of Activity specific Role Descriptors and Resource Definitions. Typically, Team Profiles are defined on the level of Iterations or Phases or other higher-level Activity.

The following features are supported:

See Also: