Difference between revisions of "Stakeholder requirement"
(Created page with "==Types== ===User story=== :''Main wikipage: User story'' ===Epic story=== :''Main wikipage: Epic story'' ===Product epic=== :''Main wikipage: Product epic''") |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | ==Definitions== | ||
| + | According to the [[BABOK Guide|BABOK Guide (3rd edition)]], | ||
| + | :[[Stakeholder requirement]]. A description of the needs of a particular stakeholder or class of stakeholders that must be met in order to achieve the business requirements. They may serve as a bridge between business requirements and the various categories of solution requirements. | ||
| + | |||
| + | [[Category: Business Analysis]][[Category: Articles]] | ||
| + | |||
==Types== | ==Types== | ||
===User story=== | ===User story=== | ||
| Line 8: | Line 14: | ||
===Product epic=== | ===Product epic=== | ||
:''Main wikipage: [[Product epic]]'' | :''Main wikipage: [[Product epic]]'' | ||
| + | |||
| + | ==Draft descriptions== | ||
| + | Stakeholder Requirements define the needs of a particular group of stakeholders and what they require of a particular solution. They are not always so different from Solution requirements except that they are from a stakeholders perspective and they show clear traceability to the business requirements. This is important since business requirements can be achieved in many different ways. This sometimes requires a compromise between competing needs of different stakeholder groups for the greater good of the enterprise. In this way Stakeholder Requirements are the bridge between business requirements and solution requirements. A few key points are: | ||
| + | |||
| + | Stakeholder Requirements define WHAT each specific stakeholder/group needs from a solution | ||
| + | Stakeholder Requirements identify the use cases of a solution | ||
| + | Stakeholder Requirements are the bridge between business requirements and solution requirements | ||
| + | |||
| + | Stakeholder requirements as per BABOK guide: | ||
| + | |||
| + | Describe the needs of stakeholders that must be met in order to achieve the business requirements. | ||
| + | |||
| + | Stakeholders requirements represent the requirements of individual stakeholders. | ||
| + | |||
| + | Stakeholders requirements are more individualistic. They serve as a bridge between business and solution requirements. | ||
| + | |||
| + | Stakeholders may specify their requirements specific to the project as per their needs (the division or business unit they represent). | ||
| + | Example of stakeholder requirements | ||
| + | |||
| + | In our Bank’s customer service management project, one of the stakeholders may state the following requirement: | ||
| + | |||
| + | We would like to have a mechanism to monitor the response time for each and every customer support request on a daily basis in order to improve the response time. The report should be generated daily, monthly or on on-demand basis. | ||
| + | |||
| + | Stakeholder requirements define the needs of stakeholders and how they will interact with a solution. Stakeholder requirements bridge between the high-level business requirements and the more detailed solution requirements. | ||
| + | |||
| + | Stakeholder requirements : describe the needs of stakeholders that must be met in ord bridge er to achieve the business requirements. They may serve as a between business and solution requirements. | ||
Latest revision as of 09:18, 7 July 2020
Definitions
According to the BABOK Guide (3rd edition),
- Stakeholder requirement. A description of the needs of a particular stakeholder or class of stakeholders that must be met in order to achieve the business requirements. They may serve as a bridge between business requirements and the various categories of solution requirements.
Types
User story
- Main wikipage: User story
Epic story
- Main wikipage: Epic story
Product epic
- Main wikipage: Product epic
Draft descriptions
Stakeholder Requirements define the needs of a particular group of stakeholders and what they require of a particular solution. They are not always so different from Solution requirements except that they are from a stakeholders perspective and they show clear traceability to the business requirements. This is important since business requirements can be achieved in many different ways. This sometimes requires a compromise between competing needs of different stakeholder groups for the greater good of the enterprise. In this way Stakeholder Requirements are the bridge between business requirements and solution requirements. A few key points are:
Stakeholder Requirements define WHAT each specific stakeholder/group needs from a solution Stakeholder Requirements identify the use cases of a solution Stakeholder Requirements are the bridge between business requirements and solution requirements
Stakeholder requirements as per BABOK guide:
Describe the needs of stakeholders that must be met in order to achieve the business requirements.
Stakeholders requirements represent the requirements of individual stakeholders.
Stakeholders requirements are more individualistic. They serve as a bridge between business and solution requirements.
Stakeholders may specify their requirements specific to the project as per their needs (the division or business unit they represent). Example of stakeholder requirements
In our Bank’s customer service management project, one of the stakeholders may state the following requirement:
We would like to have a mechanism to monitor the response time for each and every customer support request on a daily basis in order to improve the response time. The report should be generated daily, monthly or on on-demand basis.
Stakeholder requirements define the needs of stakeholders and how they will interact with a solution. Stakeholder requirements bridge between the high-level business requirements and the more detailed solution requirements.
Stakeholder requirements : describe the needs of stakeholders that must be met in ord bridge er to achieve the business requirements. They may serve as a between business and solution requirements.
