Here's what the business wants from the application - "A minimum of 100 forms shall be validated in a 24-hour period."

The IT shop has stated that they are not sure that they can do it, but they can try. The business has stated that "this is what we require."

Question: Since IT is not sure if they can meet this requirement, should it be documented? After all, this is what the business wants. But by putting their signature to the reqs doc, IT feels as though their hands will be held to the fire. If IT doesn't know if they can meet the requirement they should sign off occur?

The business side of the org currently has a system that CURRENTLY validates 100 forms in a 24-hour period. The current system was designed by an outside vendor. The internal IT division has been charged to create a new system and the business side wants to keep this particluar capability. IT has stated that they want to comply, but they don't know if there design will be able to do it until after the fact.

What do I do? Others want sign-off on the requirements.

Thanks!

IT has stated that they won't know until it's actually in production.

I'm not sure if there is any room for negotiation.  The business side has stated that, "we have it now.  we don't want to lose it with the new system."

Question - Who signs the requirements; both IT and the business?  And if IT does, does this hold them accountable for getting it done?

Thanks!

I read this issue as one that IT believes it cannot design a solution for.

• Is there a human component to the form validation?
  
• Can IT say how many forms they believe they could validate in a 24-hour period?
  
• What is the maximum number of forms the current system has actually signed off in a 24-hour period? Just because thesystem says it does that doesn't mean that the current process hits this limit.