Requirements are essential for any project, no matter what software lifecycle you choose. Have you ever experienced that sinking feeling in your gut, when time to get things working is over, and the question is asked, “Are we ready to go live.”
In a traditional lifecycle it is common to have a traceability matrix. This is simply a document with a list of all the things your software should do. When you check them all off, or have agreement thatthey are not essential for a software release, then you’re done. You know clearly what is bing left out, and the associated risks.
In an agile implementation you often have unit tests or integration tests for everything that would have been included in the traceability matrix. This makes it a lot easier to know when you’re done because you can execute it over and over when needed,
If you don’t have a traceability matrix, automated testing, or agile tests, the question about the readiness of your software is answered with little more than a good estimate. That results in failed deployments and reduced customer confidence when you do finally release the software.
Cheers,
Ben