Prioritization of work-packages

There are two important aspects that needs to be understood about the prioritization of certain tasks/work-packages:

Excessive prioritization and re-prioritization can de-stabilize a process, so it has to follow principles.

First, it needs to be clarified who is entitled to ask for prioritization and which parameters need to be checked before this request is communicated. Secondly, the process-owner needs to assess the implication if the request is fulfilled, and these implications need to be communicated back. Third, the two parties need to "strike a deal" if the prioritization shall be done or not.

The previously mentioned implications of prioritization are that the entire process will perform for a certain period with lower productivity and that other tasks/work-packages could be completed later than planned. This already gives a hint on which downward-spiral a previously intact process can get if excessive prioritization takes place.

A work-package with a low priority that is continuously overtaken by other work-packages will sooner or later become a high-priority activity. Once priorities of new work-packages compete with aged work-packages (that had a low priority initially), the system requires a reset, and rules for requesting/granting a prioritization need to be adjusted.