Feature Prioritization Toolkit

The purpose of this doc is to let you take the features or initiatives you may have the option of working on in your business, and use them to experiment with some different prioritization methods.
How to use this Doc
1. Enter the different features you need to prioritize
The features in this list will be used for each of the different prioritization methods included in this doc.
Add a Feature
Clear Feature Data
Search
Problem to Solve
1
if the CCID isn't unique to each choice, we won't be able to link the finalized item setup attributes for those styles to the correct choice rows in a MAP Buy
2
when current retail value is null in MDM, we pull original retail, which impacts our POs
3
I have more than 12 programs in my assortment
4
Would like to see a sum of the number of choices that are listed in the buy plan portion of MAP in the aggregations summary vs having to manually count and see if I have enough or have over-choiced.
5
I get an error when I try to add a choice and the vendor field is populated.
6
I use the group choices by function in every single buy plan, but it goes away when you get to the weekly receipts. Can we have it show up there + on the buy plan when you export into Excel?
7
Product attribute values don't tell me enough (dept, class, selling channel)
8
When a KP2 is not attached to a program, the calculation comparing KP2 to my buysheet is wrong
9
IMU subtotal calc is incorrect
10
Better attached KP2 indicator
11
Really annoying to have to open vary dates but scroll for days to try and manipulate the dates by cluster. Would rather open vary dates and have the column open as wide as it can.
12
As Read Only viewer, we cannot see the entire style name for the style. Hovering over doesn't show the style name and also cannot click on the style. We have to export to see what the style name is.
There are no rows in this table
2. Try Some Different Prioritization Methods
This doc currently let's you try five different prioritization methods which intend help you determine the best order to work on them. They're ordered, starting with simpler methods, going to more complicated.
This model combines two factors to give a simple score of which feature will provide the biggest bang for your buck.
This model is helps you figure out which of your must-have features really need to shine, and which ones just need to be good enough.
This model asks the question to users: How would you feel if this feature was or was not available? The answers help tell us which features are most important for customers satisfaction
SAFe "Arnold Mod" WSJF
This modified version of SAFe's Weighted Shortest Job First approach invented by Joshua Arnold puts more weight on urgency in prioritization decisions.
Cost of delay is the cost we incur by not having a feature developed and available to users. Since we can't make everything available instantly, some features will need to come later. Cost of Delay helps you make those choices correctly.
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.