The simplest and popular method to decide which issues should be tackled first to make the software better and safer for users.

• Relevance — Helps to understand if the bug still exist and remove it from a backlog.
• Frequency — Shows how often users can face with it and broken their workflow.
• Severity — Means how badly the bug has affected the application’s functionality.
• Front Time — Time estimates for Front-End development.
• Back Time — Time estimates for Back-End development.

‍

Really High-value New Opportunity—a sales-person with a customer deal for an unplanned feature insisting re-allocating resources to build what's required to win the deal.

Results:

• Ignored strategy and roadmap.
• Resources allocated to serve a single customer.

Two ways to handle:

1. Compare the opportunity cost and value, and argue against signing the deal if you have customer insight supporting the roadmap.
2. Adjust the roadmap if the opportunity includes features you already had planned for later in the year.

Minimizes future risks and avoids slowing down the development of your software.

• Code Knowledge. How are you familiar with the code?
• Severity. How it affects the software's functionality or performance?
• Dependency and Scale. How many components depend on that part of the code? The scale of impacted software architecture.‍
• Cost of Fixing. How many story points would it cost to fix the technical debt issue?

Total Score = (Knowledge + Severity + Dependency) – 3 * Cost

1. Set a North Star metric—consolidate the work you’re doing and the value you’re delivering across acquisition, engagement, conversion, and retention.
2. Define your user flows—define your app’s key events; draw the flows between events; use your analytics to identify the percentage of users taking each flow.
3. Build a growth model—use the information about the user flows and are guided by the North Star metric to determine the growth drivers.
4. Create a spreadsheet—transfer the model to a spreadsheet and evaluate your opportunities, to see how they impact growth.

Weighted Shortest Job First used to sequence jobs (eg., Features, Capabilities, and Epics) to produce maximum economic benefit.

WSJF = Cost of Delay / Job Size

Cost of Delay = User-business value + Time criticality + Risk reduction-opportunity enablement value

Scale each parameter with Fibonacci row (1, 2, 3, 5, 8, 13, 21).