Conventional Requirements Model Flaw Misses REAL Business Requirements
by Robin F. Goldsmith, JD
A fundamental flaw in the widely-held conventional model of requirements creates much of creep and other requirements difficulties. This flaw involves misunderstanding of the nature and role of REAL business requirements. The term “REAL” relates to requirements in two ways. The first way is widely recognizable and is represented in lower-case. People think they know what the requirements are and then learn differently and must revise their requirements definition. Thus, the “real” requirements are what one ends up with, as opposed to what one may have thought initially.
The second use of “REAL” warrants distinguishing with upper case because it represents breakthrough awareness that REAL requirements are business requirements, which are in business terms and are what must be delivered to provide value.
| Attachment | Size |
|---|---|
| Conventional Requirements Model Flaw Misses REAL Business Requirements.pdf | 158.75 KB |
You just don't understand us!
Your assessment of the user’s inability to articulate their requirements is SO TRUE! I'm currently suffering through a project initiation where the users have stated we (the project manager and business analyst) just don't understand their business and what they need. We have redefined the scope of the project in the project charter 4 times and two of the times have gone back to the original idea. It is clear the users do not agree nor do they understand their own needs for this project.
I will take to heart your advice to help them develop their problem statement and be very patient.
Peggy Foreman