Requirements for Product Upgrades

A common mistake when specifying the requirements for a product upgrade is to detail each of the incremental enhancements developers should implement. While such a specification is important, it does not constitute requirements and bypasses an essential prerequisite.

Imagine you have a mature software product that is popular in the marketplace but has a key weakness: customers have difficulty using it the first time. A competitor has included a wizard-based user interface to overcome this problem. Wikipedia defines "wizard" as follows:

A wizard is an interactive computer program which acts as an interface to lead a user through a complex task, using step-by-step dialogs.

So you have a pretty straightforward solution to the problem, and you can document this solution by simply specifying what the wizard will do. But it's not a product manager's job to do so. This activity is a design activity, not a requirements activity.

A product manager should document the problem being solved, not the solution to that problem. In this case, the problem is that it takes too long for a customer to use the product for the first time. The requirement, accordingly, should be a learnability constraint. That constraint should already be included as a requirement for the existing product; the upgrade merely tightens the constraint (specifies a smaller amount of time to use the product the first time).

Often, a product upgrade does not add new requirements. Rather, it simply tightens existing nonfunctional requirements. If you find your product manager specifying a lot of new requirements for a product upgrade, she probably is shirking her responsibilities.

Comments

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the four problems that companies face, or are trying to overcome, as they make product decisions . Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions. They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem

Cauvin

Search This Blog