This article is the second in a series on requirements modeling with the emphasis on why PMs should care about modeling requirements. Last month we spoke generally about models, the benefits of modeling requirements, and introduced the relationship between the iterative nature of eliciting requirements and modeling them. This article discusses the concept of concurrent requirements modeling, a structure that helps us elicit the detail needed for a complete set of requirements.
For managers, time is a scarce commodity. Actually, it’s equally scarce for everyone, but I start off this way to show that I know how tough it is to be a manager. When I meet managers of various kinds - CEOs, division managers, middle managers, indeed all sorts of managers - I take their lack of time into account and let them know that there’s only one thing they need to do to develop a culture of continuous improvement. This is what I tell them:
Technological complexities often pose significant challenges to project staff. That’s especially true when a number of companies are involved and the technologies run the gamut from hardware subsystems, system and application software and communications infrastructure. In these cases, the difference between success and failure is often a function of detailed minutiae. Correctly addressed and everybody’s happy. One small item overlooked and there’s hell to pay.