Artifact: Stakeholder Request |
This artifact represents the wants and needs of stakeholders. The requests may or may not be turned into requirements.
Domains: Requirements
Purpose
The purpose of this artifact is to capture and track requests made by anyone who is materially affected by the outcome of the project.
Relationships
Tasks | Input To: Manage Changing Requirements | Output From:
Description
Brief Outline | Following is an example of the type of information captured in a stakeholder request: Name and contact information of the submitter Profile of the submitter (for example, job title, key responsibilities, how he will interact with or use the solution) Short description of the request Detailed description of the request Submitter's assessment of how important this request is to him Impact of not having this request Collect enough information to help you understand the request, and to be able to contact the submitter for more information, or to inform him of the disposition of his request.
Key Considerations
Stakeholder requests can come from many different sources. Examples of sources for the Stakeholder Requests are: Results of stakeholder interviews Results from requirements elicitation sessions and workshops Statement of work Request for proposal Mission statement Problem statement Business rules Laws and regulations Legacy systems Business models
Tailoring
Impact of not having | Without this artifact, you run the risk of missing some requests made from stakeholders, or having all requests automatically becoming considered as requirements.
Reasons for not needing | Project teams may find that their change management system is sufficient for collecting stakeholder requests. They may not choose to manage stakeholder requests any differently from the typical change requests submitted by developers and testers. Project teams with a clear understanding of accepted and valid requirements may not need this artifact. Project teams who have constant collaboration with stakeholders may also not need this artifact.
Representation Options | Stakeholder requests are best managed in a database, such as IBM® Rational® ClearQuest® or IBM® Rational® RequisitePro®, in order to track status, prioritize, generate reports, and establish traceability. Tailoring involves deciding on the information (attributes) to be documented for each stakeholder and each stakeholder request.
© Copyright IBM Corp. 1987, 2009. All Rights Reserved. © Copyright ABC Corp. 2009. All Rights Reserved. Includes materials licensed from IBM and Eclipse. See IBM copyright and Eclipse copyright .