Maybe you're a Project Manager who is ready to attack my commentary.
Maybe you're a Developer who is ready to applaud it.
Either way, you're reading it, and that's progress.
If you work in IT, you've heard the term "requirements" before. You have a basic idea of what requirements are, and what they're supposed to do for you, your customer and your team. If you're on the end user side, you may have heard the term thrown around by various IT people in their quest to get you a solution that works for you. The problem is that many people fail to understand how to avoid what I can only term "bad requirements".
