Artifact: Project-Specific Process
This work product describes the process that a project is to follow in order to produce the project's desired results. This work product is also referred to as the Software Development Process.
Purpose
The purpose of the development process is to provide guidance and support for the members of the project. "Information at your finger tips" is a metaphor that aligns well with the purpose of this work product.
Relationships
RolesResponsible: Modified By:
TasksInput To: Output From:
Illustrations
Key Considerations

 

Tailoring
Impact of not having

All teams have a process, although it may be ad-hoc.  A defined process helps team members understand their responsibilities and capture lessons learned.  A team that follows an ad-hoc process is at risk of being confused in terms of responsibilities, may miss opportunities to learn from experience, and is at risk of violating organizational process requirements.

Reasons for not needing

An ad-hoc process may be acceptable when there are no organizational process requirements, the team members understand their responsibilities and are comfortable working without a defined process.

Representation Options

Processes can be captured informally in documents, formally captured in a Method Composer configuration, or specified by configuring tools.  Typically an project will use a combination of these - start with a Method Composer configuration, create a document to describe variations from this configuration, and

More Information