Skip to main content

Simple Requirements Example

The example below is for people with an analytical bent who are interested in understanding my definition of "requirement":
"A requirement states the least stringent condition that must hold to solve or avoid a problem that a prospective customer faces."
Assume we are developing a temperature control system, and the problems that prospective customers face include:
  1. Prospective customers feel too cold or too hot in their homes.
  2. Prospective customers will feel frustrated if it takes more than one minute of their time per day to maintain a comfortable temperature.
We would likely include in our requirements a Maintain Comfortable Temperature use case and attach an ease of use constraint to it.

Here are two possible ease of use constraints:

a. The system will be a thermostat with a dial to set the desired temperature, a switch that determines cooling or heating mode, and an on/off switch.
b. For a user that fits profile 'x', it should take no longer one minute of his time per day to maintain a comfortable temperature in his home.
It is conceivable that we could solve problem 2 with a temperature control system that did not have the user interface specified in constraint 'a'. Therefore, ease of use constraint 'a' is not a requirement, as it is not the least stringent condition that must hold to solve problem 2.

Constraint 'b', on the other hand, flatly restates the prospect problem in terms of a negative condition. It is therefore a requirement.


Roger L. Cauvin said…
Well, I tried to be careful here. I'm not sure if what you call "ideation" is a good thing when it comes to requirements.

I framed one of the problems as the ease (in terms of time expended) of maintaining a comfortable temperature. Given this problem, there was no "ideation" in expressing the requirement as a limit on the amount of time it should take to maintain a comfortable temperature. The requirement did nothing more than restate the problem in terms of its inverse.

Perhaps the problem statement contains some implicit "ideation". To the extent that's the case, I think the problem statement (and thus the requirement) is flawed.

Don't get me wrong. "Ideation" sounds like a great thing. But it seems more like design than requirements to me.
Roger L. Cauvin said…
Rereading this entry and comments, I now don't think it's fair to contend that it contained any "ideation". By "maintain comfortable temperature", I did not mean setting a target temperature. Certainly, an A/C system with a thermostat might be a natural solution to the problem. But I explicitly rejected the alleged constraint containing that assumption as design. My intent was to frame the problem of feeling too hot or too cold as a requirement. That's what I meant by "temperature". Perhaps "perceived temperature" would have been clearer.

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

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

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