The implementation of a prioritization scheme is, for an organization, a simple step towards correcting systemic software-development-issues. Those problems demand an institution have rules about placing items into various preference categories. Yet, those guidelines do not tell a company how or when to promote an element to a higher level or demote it to a lower one. That business could use its instincts to elevate and drop one, but it might feel shaky about making such decisions, using only hunches. An organization can be confident it is making defensible choices, by using the rules described below.