Traditionally, software development projects have begun with a long requirements-gathering process to ensure the final deliverable would meet the needs of the intended users.
In some cases, this has meant incurring excessive costs before understanding the size of the project, as well as failure to assess return on investment. The Agile software development approach emphasizes both value and user satisfaction. Agile focuses on broadly defined features (often referred to as epics) rather than lengthy upfront definition of requirements. Instead, requirements are addressed “just in time” — at the point when implementation becomes a high priority. Learn about the value-driven user stories exercise that is used by Scrum product owners and their teams to identify required product functionality based on user needs in this white paper.
Published Article: Value-Driven User Stories Exercise