Skip to main content

Requirements Concepts Webinar

I will be presenting a webinar on requirements concepts Wednesday, January 17th at 11 am CST. With the help of my requirements conceptual model, I will attempt to break through much of the confusion that plagues requirements terminology. You can register to receive an e-mail reminder of the webinar here.

Comments

Unknown said…
Hi Roger,

I must say that I like your conceptual model for requirements terminology. Unfortunately I missed the posting at the time. At work I recently faced the same problem: a lot of confusion about terminology. I also wrote up a formal model for the terminology which you can find here. Good luck with the webinar, unfortunately I won't be able to make it due to timezones.
rcauvin said…
I like it, Bas! I suspect if everyone had to compose a formal conceptual model of the way they use requirements terminology, it would expose a lot of confusion and contradictions. The exercise forces us to clarify the concepts to avoid the contradictions.

Popular posts from this blog

Dancer Test

Are you left-brained or right-brained? Supposedly, your brain lateralization determines how you view this animation. Some people see her rotating clockwise. Others see her rotating counter-clockwise. Some see her unpredictably changing the direction of her rotation. Supposedly, people who see clockwise rotation are right brained. People who see counter-clockwise rotation are left brained. I originally came across this animation here .

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 ...