CX Works

CX Works brings the most relevant leading practices to you.
It is a single portal of curated, field-tested and SAP-verified expertise for SAP Customer Experience solutions

Prioritized Requirements List (PRL) | Template Download

5 min read

As part of release planning, the Feature Roadmap is produced and updated. This will clearly indicate what is in the scope of the current release, and what will be deferred to a subsequent or future release. The features for the current release are further categorized as "must-have" and "should-have" requirements. The artifact can be maintained as a stand-alone document, or it can be exported from JIRA. 

Table of Contents


The Header section represents the information regarding the PRL document:

Field name Description
Project Title Name of the project for which the PRL document is dedicated
Customer Name Official name of the client
Release # Project release number
Version Version of the PRL document

Release "X" PRL

This tab contains all the Features of the current release in the form of a Prioritized Requirements List (PRL). An Epic can represent a group of features.  All Features in the current Release must have a Story Point estimation and a MUST-HAVE or SHOULD-HAVE priority.

Field name Description
ID# Unique ID of the feature
Epic Epic name to which specific feature is assigned. Describes entire functionality. The drop-down provides a list of commonly used epics
Feature One part of the entire set of features assigned
Issue Type Distinguish if the ticket is a user story or a task
Story Points Number of points. The cost/effort of the feature to be implemented
Description More information related to the feature
Priority Must-Have or Should-Have priority
Tracking tool ID# External link to the system where the features development status is tracked. e.g. JIRA
Status The status of the ticket (e.g. In-Progress, Blocked, Completed)

Features Roadmap

This tab contains all the Features for the current release as well as all future releases. It is useful to have a Story Point estimate for Features in future releases, but it is not strictly necessary. If there is not enough information available yet to add Story Points, it may be preferable to defer the estimation until later. Following the lean principles of avoiding waste, these Features can be mere placeholders for desired functionality, and will be described in detail closer to implementation.

Field name Description
ID# Unique ID number of the feature
Epic Describes entire functionality
Feature One part of the entire set of features assigned to one epic
Story Points Number of points. The cost/effort of the feature to be implemented
Schedule Describes information when a specific feature is going to be implemented. Specific release
Business Owner Feature business-side-owner. They describe the requirements, the reason(s) why this feature must be delivered, and what business value it is going to provide
Tracking Tool ID# External link to system where the feature us tracked by its statuses, issues, etc


This tab is used to track changes to the document.  It gives a summary view of the change of story points over the updated version of the prioritized requirements list. 

Field name Description
Change for version <version #> Description what has been modified, and shows information regarding the historical and actual value
Date Date when a specific change has been made to the document
SP Number of story points that are required to be used n order to implement the change


The epics worksheet shows a complete list of epics, the completion status and the total sum of story points. This gives a high-level view of the release. 


The features worksheet gives a more detailed view of all the user stories, their associated epics and the completion status.


During the Explore phase of a specific release, the features for that release are re-evaluated and broken down into finer-grained sub-features. Sub-features and the associated features are documented in a Prioritized Requirement List (PRL) and a revised release roadmap.