Handle Requirement

How do you handle a requirement that is not feasible?

Questions by scarnes67

Showing Answers 1 - 6 of 6 Answers

saurabh243

  • Feb 25th, 2010
 

Approach towards handling handling requirements that are not feasible is to first categorise either as possible with some workaround subject to client agreeing on extending timelines to meet that requirement and the extra cost incurred or is superficial and is not at all possible.

For the second categorisation, advisable practice is to say very politily that this is not at all possible and would impact the proposed system in any way.

For the first categorisation, just work for workaround and give client about options either to pay for extra cost and delayed timelines or keep aside the requirement.

cdnewlin

  • Mar 31st, 2010
 

Depending on the situation and the level of the person requesting, I wouldn't be necessarily negative on it, but perhaps would see if some other requirement might suffice that is already in the list.  If this does not work, then I would add it in the wishlist and perhaps make it either lower priority or bump it back to the next version to come out after this one is completed. 

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions