We’ve all heard the horror stories of the large software development project that took longer and cost much more than was originally planned. And in many cases the finished solution still missed the mark on requirements, or even worse, got cancelled because it was no longer relevant. Although there are a variety of reasons this could happen, some of the more common reasons include the following:
- Users couldn’t fully articulate or anticipate their requirements
- The software developers misinterpreted the requirements
- The business’s requirements changed over time
There has been a lot of research and money spent by industry experts, software developers, project managers and companies to develop and implement methodologies and procedures to improve how requirements are gathered, validated, and managed over the course of a project.