How to Write Your First Requirement

People always complain about the poor quality of requirements, but usually that all they do say: requirements are a mess. What would really be useful is they say what’s wrong with them, why they don’t like then, what to improve, what cannot be implemented or tested; generally, where they need to be able to do their work. There are of course some recommendations and rules to writing requirements. Good practice and a complete document nevertheless come following an optimal combination between experience, product knowledge, industry know-how and a solid and clear systematic...

read more

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 new comers, 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 pretty solid and complete skeleton of your work product: the requirements document. So, here’s a list with some basics you can start with in order to fail: 1. Start working on phone/email basis: don't ask for a...

read more
Page 2 of 212