One of the biggest questions today is “Where do Non-Functional Requirements fit into Agile”? The answer is that they should influence the acceptance criteria of user stories as well as the definition of one. The problem is that they are often left out of both artifacts.

This white paper explores:

  • The importance of non-functional requirements
  • The big payoff of improving non-functional requirements
  • 4 concepts that will improve your non-functional requirements

Please fill in the form to access your copy of the white paper.

Read the Whitepaper