Artifact: Method User Guidelines |
|
 |
This work product documents usage guidelines for the organization's method library and its included method assets. |
Domains: Software Capability Improvement |
|
Purpose
This artifact helps project teams identify, access, and use the right set of method assets for their
projects. It also supports consistent process application across the organization to ensure that applicable standards
are met and objectives are achieved.
|
Relationships
Roles | Responsible:
| Modified By:
|
Tasks | Input To:
| Output From:
|
Description
Main Description |
This artifact is a "how-to" manual for an organization's method library. Aside from describing the basics of how
teams access and use the deployed method assets, this artifact includes policies for tailoring the assets to meet the
needs of individual projects - this allows teams to comply with the intent and purpose of the organization's
method assets in a manner that is consistent with their own projects' constraints, environment and
objectives. This artifact ensures teams are not over-burdened with unnecessary or unproductive activities.
Typical examples of method asset tailoring include:
-
Modifying the lifecycle model (for example phases and milestones).
-
Modifying work products or tasks content.
-
Changing the order in which tasks are performed.
|
Brief Outline |
This artifact typically contains the following sections:
-
Overview of available assets and their usage
-
Instructions for accessing the method assets
-
Guidance for tailoring and extending the method assets using method authoring tools
-
Policies for tailoring, including any required approvals
|
Key Considerations
Balance the need for consistently applying processes with allowing flexibility for project teams. Consider variables
such as project scale, team maturity, and technical domain, which can impact both the type and formality of the process
needed.
|
Tailoring
Impact of not having | Without this artifact, method assets may be used inconsistently across the organization. Results cannot be monitored
to determine if process improvements are helping the organization meet its identified objectives. |
Reasons for not needing |
This artifact is not needed when:
-
The organization has no standard method library or method assets
-
Only one set of assets is available, and it is used "as-is" with no tailoring
|
Licensed Materials - Property of IBM
© Copyright IBM Corp. 1987, 2012. All Rights Reserved.
|
|