In this blog post , I would like to explain
so lets get started
Requirements are expectations from Business that need to be fulfilled. They are typically collected as part of Fit-to-standard workshops. Requirements can call into multiple workstreams such as Standard configuration , Extensibility , Analytics .
Also requirements can vary in size and complexity. Some of the requirements may need approval to proceed but some requirements which are business as usual are sent to development without any explicit approval
A Requirement can be broken down into smaller units such as Project tasks and user stories. Even though Project tasks and user stories behave very similarly , we recommend that you use Project tasks for collaboration and clarifications and user stories for smaller definitions of Requirements from user perspective. These Project tasks and user stories can be further broken down into sub-tasks
So your Hierarchy should look like
Please note that decomposition of a Requirement into Project tasks or user stories is optional.
The best way to view the Hierarchy is using the Gantt chart control in Requirements app
You can create requirements in various ways
The recommended way to create Requirement is using the Solution process diagram so that the process context is automatically captured in the Requirement
later you can use the solution process information to filter the requirements easily.
You can just create a Requirement using the create option in the Requirements app
you can download the template
and modify the template to upload requirements along with its children. As an example you can modify the template to look like
Please note the Parent row column should reflect the row in Excel sheet correctly.
Once you upload , you get results like
if you want to see them in a Hierarchy , you need to switch to Gantt view
In the Overview Page there are multiple cards which help you track requirements by status, by scope or by workstreams
also in the Analytics app , there is a chart called Requirement Traceability which helps you decide when to change the status of a Requirement
Tips and Tricks for Requirement Management
Stay tuned for more information. If you want to give feedback or have a question , feel free to drop a comment. Please bookmark these two links
Follow me for latest updates by clicking jagmohansingh.chawla
- What are Requirements
- what is Requirement Hierarchy
- How do you create Requirements
- How do you Track Requirements
so lets get started
What are Requirements
Requirements are expectations from Business that need to be fulfilled. They are typically collected as part of Fit-to-standard workshops. Requirements can call into multiple workstreams such as Standard configuration , Extensibility , Analytics .
Also requirements can vary in size and complexity. Some of the requirements may need approval to proceed but some requirements which are business as usual are sent to development without any explicit approval
What is Requirement Hierarchy
A Requirement can be broken down into smaller units such as Project tasks and user stories. Even though Project tasks and user stories behave very similarly , we recommend that you use Project tasks for collaboration and clarifications and user stories for smaller definitions of Requirements from user perspective. These Project tasks and user stories can be further broken down into sub-tasks
So your Hierarchy should look like
- Requirement
- Project Task
- Sub-task 1
- Sub-task 2
- User story 1
- Sub-task 1
- sub-task 2
- User story 2
- Sub-task 1
- Project Task
Please note that decomposition of a Requirement into Project tasks or user stories is optional.
The best way to view the Hierarchy is using the Gantt chart control in Requirements app
How do you create Requirements
You can create requirements in various ways
From a Solution process
The recommended way to create Requirement is using the Solution process diagram so that the process context is automatically captured in the Requirement
later you can use the solution process information to filter the requirements easily.
Manually using the Requirements app
You can just create a Requirement using the create option in the Requirements app
Mass Upload via an Excel Sheet
you can download the template
and modify the template to upload requirements along with its children. As an example you can modify the template to look like
Please note the Parent row column should reflect the row in Excel sheet correctly.
Once you upload , you get results like
if you want to see them in a Hierarchy , you need to switch to Gantt view
How do you track Requirements
In the Overview Page there are multiple cards which help you track requirements by status, by scope or by workstreams
also in the Analytics app , there is a chart called Requirement Traceability which helps you decide when to change the status of a Requirement
Recommended Blog Posts
Tips and Tricks for Requirement Management
Next Steps
Stay tuned for more information. If you want to give feedback or have a question , feel free to drop a comment. Please bookmark these two links
- Master List for Blog posts in Project, Task and Requirement management
- Expert Portal for SAP Cloud ALM
Follow me for latest updates by clicking jagmohansingh.chawla
- SAP Managed Tags:
