Question

1. Name three reasons that stakeholder needs cannot simply be recorded as software product requirements.

please type it

Answer 1

1- Features -   Your next step is to determine the feature requirements for the release. Every feature should support the overall purpose of your product.

Some examples of a theme might be:

• API
• Performance
• Mobile

This might be changes as the new technoligies or new features need to implement to improve the application to meet the future requiremement and needs .

2-  Timeline -

Every product release needs a goal release date — even if it’s a rough estimate.

This should give you flexibility to adapt to a change in priorities. But it should restrict scope creep by limiting how many features stakeholders can add.

The timeline also changes as there is new features need to implement or some modification needed .

3- Release Criteria -  

Functionality

You’ll need to define the minimum functionality you need in order to release the product. An example is defining requirements that are critical to the release. It keeps changes .

Usability

You’ll need to ensure the product is easy to use. An example is determining the scope of user testing — and what you’ll do with those results.