Prioritisation
Prioritisation is the discipline of ordering initiatives, features, or tasks to maximise business value and engineering velocity. For technology leaders, prioritisation is not simply about choosing what to build; it is the strategic act of deciding what not to build, protecting engineering bandwidth, and ensuring that the team's output matches the company's highest-leverage goals.
Without a structured approach, engineering teams risk succumbing to the loudest voice in the room, chasing low-value feature requests, or falling into Analysis Paralysis.
The Prioritisation Spectrum
Prioritisation frameworks generally fall along a spectrum from qualitative, stakeholder-driven models to quantitative, economically-driven models. Choosing the right framework depends on the complexity of your roadmap, the availability of data, and the type of delivery model you employ.
Why Technology Leaders Must Care
- Protecting Engineering Flow
Constant context switching kills productivity. Clear prioritisation sets boundaries, allowing engineering teams to focus on finishing work rather than starting new things. - Managing Opportunity Cost
Every feature built comes at the expense of another. Frameworks force cross-functional teams to explicitly acknowledge these trade-offs rather than assuming "we can build everything." - Establishing a Shared Language
A transparent prioritisation model removes emotion from roadmapping. It shifts the discussion from "Why isn't my feature done?" to "How does this feature score against our agreed framework?"
Core Methodologies
Within this section, we cover two primary methodologies that suit different organisational needs:
1. MoSCoW Method
A qualitative classification technique that groups requirements into Must have, Should have, Could have, and Won't have (for now). It is highly effective for managing scope in fixed-deadline projects and aligning stakeholder expectations around MVP (Minimum Viable Product) definitions.
2. Weighted Shortest Job First (WSJF)
A quantitative, economic framework popularized by the Scaled Agile Framework (SAFe). It calculates priority by dividing the Cost of Delay by the Job Size (Duration). This model is ideal for continuous flow systems where the goal is to maximise value delivery while minimising lead times.
Strategic Recommendations
- Use MoSCoW for tactical releases and MVPs where time and budget are fixed, and you need quick stakeholder agreement on what constitutes the baseline product.
- Use WSJF for strategic roadmapping and backlog grooming in mature agile organisations where you want to maximise ROI and sequence large-scale features based on economics rather than intuition.
- Avoid framework dogmatism. The goal is alignment and velocity, not bureaucratic compliance. Choose the simplest model that achieves consensus and keeps the team building.