Label records can be used to help organize and govern projects.
There are many instances where standardization across the enterprise is
needed to help organize and govern projects. Label records enable you to define
a set of names which appear in the user interface (for example, as drop-down
lists on records).
Most Labels consist of a Name and a Description.
The following labels can be shared across the database instance:
- ALMCategoryTypeLabel: Categories provide the means to classify projects,
and create a hierarchy of types of categories. By defining more than one category
type, you can create hierarchies of categories belonging to one category type
or another. For example, you can define category types such as Solution, Product,
SOA Service, Re-Usable Component, and Business Unit, and create an appropriate
hierarchy for these types.
- ALMPhaseLabel and ALMIterationLabel: Many processes, including the Rational
Unified Process recommend dividing projects into Phases, where each phase
can have one or more iterations. Doing so helps to divide a project into more
manageable units. For example, the Rational Unified Process suggests
for Phase labels: Inception, Elaboration, Construction, and Transition. An
iteration is a planned, time-boxed interval typically measured in weeks. Iterations
focus the team on delivering incremental value to stakeholders in a predictable
manner. A Phase can also be used to define milestones for an agile development
process. By using Phase and Iteration labels you can ensure consistent adoption
of terminology across your organization.
- ALMReleaseLabel: Releases are used to identify the version of the software
being developed. Some organizations standardize by using release names or
numbers. You can use a Release Label record to identify a release label that
will be used by others in the organization. For example, IBM® uses a four
digit release numbering scheme for all products, such as ClearQuest® 7.1.0.0.
- ALMResolutionCodeLabel: When units of work are completed, a resolution
code is set to provide a history and context for the type of resolution. For
example, not all work is completed in a project. Sometimes there are duplicate
requests, or a reported problem can not be reproduced or works as designed.
You have the opportunity to define a set of resolution codes to be used by
your organization.
- ALMRoleLabel: Role labels help to ensure a consistent use of roles across
the organization. Analyst, Architect, Project Manager, Developer, Tester are
examples of role names.
- ALMStatusLabel: A status label can be used to report the status or health
of a Project, Phase, or Iteration. Some examples of a status are Healthy,
Suspect, and Critical. Some organizations use color coding such as Green (for
healthy), Yellow (for caution), and Red (for critical).
- ALMTypeLabel: Requests, Tasks and Activities vary from organization by
organization, therefore each of these record types has a set of work Type
labels that can be viewed in a Type drop-down list. The names that
appear on that list come from the work Type record. You start by defining
the work Type Label. The value is the name of the type (for example, Enhancement).