Product Hierarchy
Agile Estimation
Bugs, Defects & Technical Debt
100

This is the highest level in the MWoW Product Hierarchy, representing strategic investments that support enterprise goals.

What is an Initiative?

100

Agile teams use this sequence to estimate story points, focusing on relative complexity rather than absolute time.

What is the Fibonacci sequence?

100

This issue type is identified during development and testing in a sprint and should be addressed as part of the Definition of Done.

What is a Bug?

200

This level breaks down into Epics and represents significant capabilities that span multiple quarters.

What is a Feature?

200

According to MWoW standards, stories larger than this point value should be broken down for clarity and deliverability.

What is 8 (story points)?

200

This issue type is found in the production environment and results from a coding error missed during testing.

What is a Production Defect?

300

This unit of work is completed in a single sprint and describes value from the end user’s perspective.

What is a User Story?

300

This is one of the several distinct flavors of estimation used in Agile teams, and consists of estimating tasks or user stories, not separately and in absolute units of time, but by comparison or by grouping of items of equivalent difficulty.

What is Relative estimation?

300

This term describes the cost of future rework caused by choosing a quick solution over a robust one.

What is Technical Debt?