Work arrangement
Prioritization is the traditional method to change order of the requirement or task implementation. First we set order for the requirement or task, then sort backlog or board by priority, and start working on the topmost tasks, i.e., the most urgent tasks. Devprom ALM offers a predefined list of priorities which can be changed in the administrator section.
The color scheme of priorities is used when displaying the task and requirement priorities, as well as visualizing cards on the boards.
An alternative way to reorder tasks is numbering of these tasks. Each requirement and each task has "Number” field, value of which is increased automatically at the creation of the corresponding issue. Use sorting settings to reorder tasks by their numbers. You can drag and drop rows and cards on lists and boards, thereby changing their numbers and order interactively, and consequently changing order of their implementation:
Sometimes dependencies between requirements or tasks affect the order of their implementation. One of the examples are technological dependencies when the task cannot be completed without completion of the previous task.
To establish dependencies between primary requirements, use "Dependencies" field. Create dependencies with "Blocks" type. You can use prerequisites for transitions in requirement lifecycle settings to check the completion of blocking requirements. If a requirement is not completed and blocks another requirement, you cannot work on or complete the second requirement.
You can block completion of a requirement without the creation of another requirement. For example, if there are opened issues that do not allow to transfer work on the requirement to further stages. Choose "Block" action and select a reason from the dictionary. You can fill the dictionary with your own reasons, and build a distribution chart of reasons blocking requirements in the project.
Similarly, you can use "Preceding tasks" or “Subsequent tasks" fields to establish dependencies and use them for setting up lifecycle of the tasks.