Want to complete a project successfully?
Then you’d better have success at the start. That means getting requirements right, and there are as many ways to do that as there are business analysts charged with getting it done.
But impatience, miscommunication, misunderstandings and overlooked users can produce requirements that aren’t clear or complete. ‘You want to have as little ambiguity as possible, because ambiguity creates defects,’ says Andrew Ari Clibanoff, a senior business analyst at GSI Commerce Inc., a King of Prussia, Pa.-based provider of e-commerce services.
Those defects can be costly. Ellen Gottesdiener, principal consultant at EBG Consulting in Carmel, Ind., and author of ‘The Software Requirements Memory Jogger’ (Goal QPC Inc., 2005), says that roughly one-third of the budget for a typical project goes to fixing defects that originated in faulty requirements.
The following tips will help you avoid becoming part of that depressing statistic…
Start understanding your users at: http://www.journyx.com/rss/redir/cworld-userswant.html