Software Requirements

Requirements Pulse - How many conditions apply to your project

• The project's business objectives, vision, and scope were never clearly defined.
• Customers were too busy to spend time working with analysts or developers on the requirements.
• Your team could not interact directly with representative users to understand their needs.
• Customers claimed that all requirements were critical, so they didn't prioritize them.
• Developers encountered ambiguities and missing information when coding, so they had to guess.
• Communications between developers and stakeholders focused on user interface displays or features, not on what users needed to accomplish with the software.
• Your customers never approved the requirements.
• Your customers approved the requirements for a release or iteration and then changed them continually.
• The project scope increased as requirements changes were accepted. but the schedule slipped because no additional resources were provided and no functionality was removed.
• Requested requirements changes got lost; no one knew the status of a particular change request.
• Customers requested certain functionality and developers built it, but no one ever uses it.
• At the end of the project, the specification was satisfied but the customer or the business objectives were not.