Work Product Descriptor (Artifact): Stakeholder Request
This artifact represents the wants and needs of stakeholders. The requests may or may not be turned into requirements.

The purpose of this artifact is to capture and track requests made by anyone who is materially affected by the outcome of the project.

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

Relationships
Fulfilled Slots
RolesResponsible: Modified By:
Input ToMandatory: Optional:
  • None
External:
  • None