Prioritizing requirements
Requirement prioritization is done based on the need and urgency to deliver the feature to the end users. While prioritizing the requirements, the project team also considers its complexity and the efforts required to accomplish the requested tasks. The project team can take actions based on the level of priority.
For example, if the feature request is of critical priority, that means that its importance is very high and its timeline very short. Hence, all the things needed to achieve the aforementioned tasks, such as data, tools, permissions, a skill set, and resources, are acquired within a short period and the project team tries to achieve its goal as per the set timelines.
Jira has four different priority types ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access