�ݺ�ߣ

Editor's Notes

• #14: The horizontal access shows low to high number of features, the vertical access shows customer response low to high. If you have a high number of features, it maximizes initial sales…so it is natural for sales to ask for a lot of features. However repeat sales are maximized by a lower number or features. Especially in a subscription model, we often see a spike in initial sales, and then a drop off when customers are up for renewal.
• #15: Additionally, if you look at this graph, 80% of features in a typical system are only sometime, rarely, or never used. How do you know that your feature idea doesn’t fall into that 80% area. Since only 20% of Features are Always or Often used, it’s critical that we figure out what the 20% is as early as possible, so that we don’t waste money in developing Requirements that fall into the 80%. Sometimes sales will ask for something, or a user set on a platform will ask for something that is in the 80%, in that case, we had better make sure (which is a skill and an art), that how we implement that particular features doesn’t get in the way of the user’s 20%....or we risk meeting our user needs and our long term prospects for repeat sales. This workshop will help you stay focused on what is most valuable and what requirements are most likely to end up in the 20%
• #31: Incrementing means building a little bit at a time. If developers are working in this way, there won’t be anything that looks close to a finished product until the end. If you look at this as the number of features build per month, there are key features missing
• #34: It’s not enough to say that she wants to buy a handbag. We need to know WHY, or we will build the wrong thing for Lisa. She doesn’t buy on Amazon because everyone else goes there. Lisa is a Hipster, who wants to feel like she is the first person to ever get to this website and is the only person who has access to buy these handbags.
• #38: Are these user stories