Skip to main content

On So-Called "Business Requirements"

Over on the Requirements Defined blog, Dan notes that a prudent product manager reviews requirements with various stakeholders and team members early and often:

At all stages in the process, there should be time devoted to validating the requirement with the relevant team members. When a review and approval step is skipped, the requirement and the dependencies for that requirement are placed at risk.
Yet, in his entry, Dan unintentionally provides a good example of how confusion over an alleged distinction between "business" requirements and more "detailed" requirements can result in overlooking the real requirements altogether.

Let's examine all the alleged "levels" of requirements:

By requirements I mean everything from high-level business needs (e.g. stakeholder requests, business requirements, vision and problem statements) to the most granular requirements (aka shall statements, functional and supplementary requirements and the like).
The point of Dan's overall entry is well taken, and I'm sure that he had no intention of getting sucked into yet another semantic debate about the definition of "requirement". But I see substantive problems with the following statement:
Does a tester have to review a stakeholder request like “Business wants to provide upsell and cross-sell opportunities based on items browsed/purchased on the website.” Probably not, but the business does. They need to validate the functional features that will execute this requirement.
Requirements should, in principle, be testable. The stakeholder request is far too vague to be testable. Your product manager's job should be to engage the stakeholder in a dialog that brings out precisely what "upselling" and "cross-selling" are, why they are important, and how to measure them. Merely "providing the opportunities" is useless if the opportunities don't translate into measurable sales, or at least measurable clicks or page visitations.

Worrying about "validating the functional features" is relatively unimportant when the success metrics are in place. A significant cause of problems in many organizations is a tendency to go from vague stakeholder requests to features or low-level functional specifications. Neither stakeholder requests nor low-level functions are requirements. Only when organizations recognize this fact are they likely to identify the real, measurable, solution-independent requirements.

Comments

Anonymous said…
Another important thing is to actually validate the validity of requirements presented by stakeholders.

For example "customer" or "market" requirements presented by stakeholders from sales are often "marketing" requirements and could easyly be skipped, if the product is presented in another way (typical example sales thinks feature X of competitor is cool, whereas the feature is actually a well presented shortcoming).
Mon Dec 25, 09:34:00 PM 2006
Post a Comment

Popular posts from this blog

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
32 comments
Read more

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
12 comments
Read more

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
9 comments
Read more