Overemphasis on Functional Requirements

I've mentioned before that there are two kinds of requirements, functional and nonfunctional. What I didn't mention is that most organizations place too much emphasis on functional requirements.

How can you tell if your organization overemphasizes functional requirements?

If your organization bothers to document requirements (whether in an MRD or other document), examine them. If you find any of the following statements apply, then your organization probably is overemphasizing functional requirements:

Is there a laundry list of product features?
Are there more use cases than constraints on the use cases?
Is there a multi-page section labeled "functional requirements"?

If any of these statements apply in your case, then your organization likely fails to understand the difference between functional and nonfunctional requirements. In a future entry, I will explain why the overemphasis on functional requirements has a negative impact on product development.

UPDATE: See the follow-up entry and this clarification. The problem is that so-called functional requirements are sometimes functional design specifications masquerading as requirements.

Comments

leathej1 said…

I see where you are going with this. However, let me turn this upside down and suggest we concentrate on Using Functional Requirements More Effectively. I think you will find that NF requirements will fall right off the page if we follow some simple steps to drive detail and context in our Functional Requirements.

Thu May 25, 10:17:00 AM 2006

Roger L. Cauvin said…

But isn't "detail and context" precisely what nonfunctional requirements are?

Thu May 25, 03:52:00 PM 2006

leathej1 said…

Right. So why let your BAs procrastinate with statements like this:

Non-functional requirements:
Non-functional requirements will be dealt with in another document.

IOW - why the hell do we deal with them separately?

Wed May 30, 03:28:00 PM 2007

Roger L. Cauvin said…

I agree. Since nonfunctional requirements modify (or constrain) functions, it doesn't make sense to deal with them separately.

Thu May 31, 09:10:00 AM 2007

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