22:25
Faizan
Failed requirements are one of the most common reasons of failed projects. Who's to blame? Who made them unclear or misunderstood, intentionally or accidentally? Nah, there is nothing interesting in figuring all that out. What's much more interesting is how to prevent receiving not what you want. Here are some helpful tips to start gathering requirements for your project with. In fact, the more of these are missed, the more problems may arise later, with everyone having to sit late at night and solve them.
Step #1. Document Everything
When you are driven by passion for what you want to do and share with the world, you seem to remember everything perfectly. But writing things down has lots of pros. One, it's a good start for the documentation, which is more useful and impressive than words - for both developers and investors. Two, you won't lose details (which do tend to be lost). Three, when you write an idea down, you develop it right there, then come up with another one, and so on. New and useful ideas always come when you pay them due attention.
Step #2. The Sooner You Set The Goals, The Better
The universal rule for any project. The goals of your project must be written down, and you'll have a basis for the upcoming decision-making. All of your requirements will help the project achieve its goals one way or another. If a requirement is of questionable importance for satisfying the objectives, most probably it can be left on the shelf until later.
Step #3. Set The Right Priorities
The main priority is user. Startups don't have yearlong time to roll products on the market - they let their development walk the agile way, offer a minimum viable product to users, and improve upon each new update. This natural scheme of things works through prioritizing features. Research of the market and professional opinion in your subject area will help you determine what is 'needed' and what 'would be nice'. Until the first user feedback, which will help you move on.
Step #4. Look For The Right People And Listen To Them
We already discussed before how and where you should look for the development team to do the job, so you may check these articles to learn more. Here we'll mention that the right people may include investors; those who are able to help your product with marketing and media coverage; and those who can help you with testing your future product - the actual users. It goes without saying that professional feedback is valued for the sake of a great product.
Step #5. Think About Requirements, Your Team Will Find The Tools
Specifications, sketches, notes, diagrams, user stories, goals of the product - this is what matters to your team. The choice of the right tools comes after the scope of work is more or less clear to them. Determine what you need, not how it will be done. Don't waste your time on what your project manager and developers will do for you and your users.
Step #1. Document Everything
When you are driven by passion for what you want to do and share with the world, you seem to remember everything perfectly. But writing things down has lots of pros. One, it's a good start for the documentation, which is more useful and impressive than words - for both developers and investors. Two, you won't lose details (which do tend to be lost). Three, when you write an idea down, you develop it right there, then come up with another one, and so on. New and useful ideas always come when you pay them due attention.
Step #2. The Sooner You Set The Goals, The Better
The universal rule for any project. The goals of your project must be written down, and you'll have a basis for the upcoming decision-making. All of your requirements will help the project achieve its goals one way or another. If a requirement is of questionable importance for satisfying the objectives, most probably it can be left on the shelf until later.
Step #3. Set The Right Priorities
The main priority is user. Startups don't have yearlong time to roll products on the market - they let their development walk the agile way, offer a minimum viable product to users, and improve upon each new update. This natural scheme of things works through prioritizing features. Research of the market and professional opinion in your subject area will help you determine what is 'needed' and what 'would be nice'. Until the first user feedback, which will help you move on.
Step #4. Look For The Right People And Listen To Them
We already discussed before how and where you should look for the development team to do the job, so you may check these articles to learn more. Here we'll mention that the right people may include investors; those who are able to help your product with marketing and media coverage; and those who can help you with testing your future product - the actual users. It goes without saying that professional feedback is valued for the sake of a great product.
Step #5. Think About Requirements, Your Team Will Find The Tools
Specifications, sketches, notes, diagrams, user stories, goals of the product - this is what matters to your team. The choice of the right tools comes after the scope of work is more or less clear to them. Determine what you need, not how it will be done. Don't waste your time on what your project manager and developers will do for you and your users.
Posted in: business
