One key factor that may be often overlooked or underestimated during
requirements elicitation is prioritizing requirements. If there are 25
documented itemized requirements, and 22 could be met by a software
solution, you might imagine that could be an excellent percentage to
have. But what if the three requirements that weren't/can not be met
were the three most vital of the unique 25 - What once will have given
the look of a good implementation now will become a questionable one.
Another example; let’s say there are 25 documented and itemized requirements, and only 10 of them can also be met by a software solution. Which can raise an alarm for an analyst, but upon closer examination the 10 requirements that aren't met are classified as low priority or “nice to haves”. The 25 requirements met are classified as critical priority. There's a different solution option that satisfies 15 of the necessities, but is missing 10 of the critical requirements. At the surface satisfying 15 of 25 requirements could seem just like the more sensible choice, but a deeper look under the covers will provide you with a clearer picture.
Given the time and resource pressures faced by all organizations in today’s economy, assigning a concern/weight to every requirement is a critical task that should be completed during requirements elicitation. Businesses must decide what's most necessary to them in an answer before you hit the drafting board.
Another example; let’s say there are 25 documented and itemized requirements, and only 10 of them can also be met by a software solution. Which can raise an alarm for an analyst, but upon closer examination the 10 requirements that aren't met are classified as low priority or “nice to haves”. The 25 requirements met are classified as critical priority. There's a different solution option that satisfies 15 of the necessities, but is missing 10 of the critical requirements. At the surface satisfying 15 of 25 requirements could seem just like the more sensible choice, but a deeper look under the covers will provide you with a clearer picture.
Given the time and resource pressures faced by all organizations in today’s economy, assigning a concern/weight to every requirement is a critical task that should be completed during requirements elicitation. Businesses must decide what's most necessary to them in an answer before you hit the drafting board.
No comments:
Post a Comment