A prioritization technique is a structured approach to evaluate and order requirements, features, or tasks using explicit criteria. It helps focus scarce resources and makes decision trade-offs transparent. Common methods include MoSCoW, Kano, and Weighted Shortest Job First. Context and stakeholder preferences guide method selection.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
A prioritization technique shows which requirements or tasks receive attention and resources first by making value, effort, and risk comparable.
Prioritization is a recurring management practice rather than a single invention. Agile ways of working formalized it through backlog and product-management practices; the Scrum Guide describes responsibility for ordering the Product Backlog.
Define the goal and decision unit first. Rate each option with a few understandable criteria, expose uncertainty, and then order the options. Review the ranking with stakeholders and update it when learning, cost, or urgency changes.
Explicit criteria show how options are compared.
Priority turns assessment into a sequence for work and decisions.
Assumptions and missing data indicate how reliable the ranking is.
Prioritization techniques help teams direct scarce capacity toward the most valuable or risky options. They support decisions rather than provide objective truth; criteria and weights remain context-dependent.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.