In this blog post I would like to share some Tips and Tricks you can use Requirement management effectively
If you are getting confused by when user Requirements, User Stories, Project tasks, sub-tasks, and Features, it's simple
Created by Business users or consultants which reflect business needs that need to be passed through the approval process
Requirements can be broken down into user stories. User stories should be sliced small enough to fit into a sprint. Contain story points
A collection of user stories ready for Deployment
Administrative or Logistical tasks are typically not part of development or configuration.
Additional breakdown of a user story or Project task
Requirements are broken down into user stories, and user stories are broken down into sub-tasks
Read this blog post to bring Requirements quickly into the system. You can bring an entire hierarchy of Requirements including relations via Excel Upload
You can easily create Tags manually or via Excel upload. This is flexible but remember "With great flexibility comes great chaos"
Establish some naming convention of tags before you start using them. Example
risk: high
risk: medium
risk: low
or
LOB: Finance
LOB: Manufacturing
LOB: Sales
establishing name-value pairs will help you in the long run by analyzing your data later
Read this blog post to see how views work and how you can save them as Tiles. In simple terms when you make adjustments to your filter settings and column results, you can save them as a view and set your preferred view as default. This can save you a lot of time as you can create views for as an example
The Requirement application has some hidden features behind the type filter settings. if you change the Type filter, you get additional create options
What is means is that the Requirement and Tasks app can enable multiple types and then they can be accessed in the Gantt chart
Read this blog post to understand how the Gantt chart can help you see and manage hierarchy. You can also select items and create relationships easily.
You can see Requirements, user stories, and sub-tasks in a hierarchy.
Since Requirements can have multiple moving parts like user stories and sub-tasks, how do you know when is the right time to change the status of a Requirement. You should use the Requirement Traceability application.
Hope you enjoyed this post. Please visit the Master Blog post and bookmark it.
To understand an end to end picture, please visit
Expert Portal for Implementation and stay connected
- Understand what is what
- Use Mass uploads
- Assign Requirements to processes
- Use Tags with naming conventions
- Create views
- Know how the Type filter works
- Use the Gantt chart
- Use Traceability reports
Understand when to use what
If you are getting confused by when user Requirements, User Stories, Project tasks, sub-tasks, and Features, it's simple
Requirements
Created by Business users or consultants which reflect business needs that need to be passed through the approval process
User stories
Requirements can be broken down into user stories. User stories should be sliced small enough to fit into a sprint. Contain story points
Features
A collection of user stories ready for Deployment
Project tasks
Administrative or Logistical tasks are typically not part of development or configuration.
Sub-tasks
Additional breakdown of a user story or Project task
Understand Hierarchy of Requirements
Requirements are broken down into user stories, and user stories are broken down into sub-tasks
Use Mass uploads
Read this blog post to bring Requirements quickly into the system. You can bring an entire hierarchy of Requirements including relations via Excel Upload
Create a naming convention for Tags
You can easily create Tags manually or via Excel upload. This is flexible but remember "With great flexibility comes great chaos"
Establish some naming convention of tags before you start using them. Example
risk: high
risk: medium
risk: low
or
LOB: Finance
LOB: Manufacturing
LOB: Sales
establishing name-value pairs will help you in the long run by analyzing your data later
Create views/Save Favorites
Read this blog post to see how views work and how you can save them as Tiles. In simple terms when you make adjustments to your filter settings and column results, you can save them as a view and set your preferred view as default. This can save you a lot of time as you can create views for as an example
- High Priority open Requirements
- Requirements awaiting approval
- High priority blocked requirements
- ....
Understand the "Type" filter
The Requirement application has some hidden features behind the type filter settings. if you change the Type filter, you get additional create options
What is means is that the Requirement and Tasks app can enable multiple types and then they can be accessed in the Gantt chart
Use Gantt chart
Read this blog post to understand how the Gantt chart can help you see and manage hierarchy. You can also select items and create relationships easily.
You can see Requirements, user stories, and sub-tasks in a hierarchy.
Use Traceability Reports
Since Requirements can have multiple moving parts like user stories and sub-tasks, how do you know when is the right time to change the status of a Requirement. You should use the Requirement Traceability application.
Next steps
Hope you enjoyed this post. Please visit the Master Blog post and bookmark it.
To understand an end to end picture, please visit
Expert Portal for Implementation and stay connected
- SAP Managed Tags:
