Tuesday Lunch: 10 Cosmic Truths About Software Requirements

Reading Group: 10 Cosmic Truths About Software Requirements
Moderator: Lawrence Ludlow
Location: Ottawa Room
Time: 12:30pm Tuesday, March 25th

The reading this week is based on an chapter from More About Software Requirements: Thorny Issues and Practical Advice by Karl E. Wiegers. The full text is located online here.

  • If you don’t get the requirements right, it doesn’t matter how well you execute the rest of the project.
  • Requirements development is a discovery and invention process, not just a collection process.
  • Change happens.
  • The interests of all the project stakeholders intersect in the requirements process.
  • Customer involvement is the most critical contributor to software quality.
  • The customer is not always right, but the customer always has a point.
  • The first question an analyst should ask about a proposed new requirement is, “It this requirement in scope?”
  • Even the best requirements document cannot—and should not—replace human dialogue.
  • The requirements might be vague, but the product will be specific.
  • You’re never going to have perfect requirements.

It's only fair to share...
Share on FacebookGoogle+Tweet about this on TwitterShare on LinkedIn

Leave a Reply