Please upgrade your browser!

Bookmark and Share

Requirements Feasibility

Ensuring Requirements Feasibility through Better Use User Acceptance Testing


Development teams can face challenges with requirements feasibility from budget, scheduling, and even technology limitations. Thus it’s important for development teams and their stakeholders to run user acceptance testing (UAT) cycles. UAT has traditionally been an area of contention between IT and the business. IT teams get critical systems readied through development and testing, while Business teams verify that these systems meet their requirements. Testing requirements feasibility entails:

  • Project manager collects the requirements that will be verified. Otherwise, consult your Acceptance Criteria for the necessary information
  • Customer confirms requirements have been met
  • The lead reviews the requirements list for known issues and adds any new ones as bugs
  • The team captures requirement changes and fit into a project as warranted while keeping an eye on project slippage and delivery schedules.

Any requirements/stories under test become part of the UAT test report. Download our FREE The Science of Running Effective User Acceptance Testing Cycles whitepaper by clicking the image to the right to learn more about how to test requirements feasibility through UAT.