How to: 10 Sure Ways to Blow Your Requirements!
What do you achieve when you don’t know what you want? Sometimes the best way to perform is not to know what to do, but what not to do. This is best start not only to newcomers, but also to experienced Requirement Engineer who takes over a new challenge. Experience and project specificity will of course add and tailor features and work process, but you already have a solid and complete skeleton of your work product: the requirements document. So, here’s a list with some basics you can start with to fail: 1. Start working on phone/email basis: don't ask for a frozen and stable customer document, he's already told you what he needs, right? Well, not always. I mean here that the customer doesn’t always has a clear idea of what he wants, but working without a document you and your customer agreed by contract to commit to, is always a bad idea. Of course, there will be changes, maybe even a lot more features, but you need a fixed starting outcome, so you can show clear results. This...