What is the use of the status for requirements? At this point the status of a requirement is always new and does not change during the whole project. It would be nice to have statusses like: In progress - requirement is being worked on. Approved - The key stakeholder has agreed to the requirement and the developer has agreed that it is possible to create Implemented - Code has been designed and is ready for review Verified - The requirement is tested and is functioning correctly Deleted - An approved requirement is deleted. An explanation is needed of why and by whom the decision was made to delete it. Rejected - The requirement is not approved. The why and by whom it has been rejected is relevant. Deprecated - The requirement is no longer in use and has been replaced by a new requirement. It should also be possible to filter out all of the requirements based upon the status. This way you can always refer to a certain requirement that has been deleted or r
At this moment the graph interval is generated from data, it determines the interval by itself. It would be nice if the graph interval is automatically generated from the data, but could be adjusted manually. To for example: steps in 0,5, steps in 1 or steps in 10.
It would be nice to fill in different priorities for the requirements in the SF. Currently you can select this release, next release or future release. But it does not give you the opportunity to select which release you would like the requirement to be added to the application. This makes it possible to do release planning using the requirements for projectmanagement and could be very usefull creating sprints.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
