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