4 ms·
> Organized on the 2x2 with these axes X: "risk/complexity" Y:"desirability" (that's business & customer desirability.) Not to sound like an idiot here or anyt
by blahblahblogger 8y ago
> Organized on the 2x2 with these axes X: "risk/complexity" Y:"desirability" (that's business & customer desirability.)
Not to sound like an idiot here or anything, but does that mean something like this:
Risk | Complexity
----------------------------------
BiZ desirability | |
----------------------------------
Cus desirability | |
Can't an item be in many of these squares?
- tinco 8y agoThe X axis would go from low risk+complexity to high risk+complexity, and the y axis from low biz+cus desirability to high biz+cus desirability. You are correct that the way you described wouldn't work.
- blahblahblogger 8y agoYes it seems like an item would be posted on an axis where theoretically the item could exist on both ends?
- jasonm23 8y agoNice to have should really be, not necessary. Problem with that is the product team will be less likely to mark things as not-necessary. So we dub these less needed features as nice to have so there's a higher chance of negotiating about their priority.
- kd5bjo 8y agoWhat's being described is an X-Y scatter plot: Necessary ^ | Simple <---+---> Complex | V Nice to have
- lioeters 8y agoThis makes the most sense to me. If I were in the OP's position, I would start discussion with the direct manager as early as possible - and begin by breaking down the remaining scope in terms of where the features are in this diagram. If the product must be "ready to ship", clearly some corners will need to be cut - especially the bottom right.
- jasonm23 8y agoExactly.