Scope
- New features might be developed and included in future Releases - these features need to be planned though
- This article describes our policy for handling this situation and its mapping with the states in the SOS Change Management System.
Life Cycle
Planned features will pass through the following states before it is decided whether they are going to be developed or not:
OPEN
- A feature has been described and assigned.
- The next step will be to decide, whether the feature is a Known Issue or it has to be Clarified.
KNOWN ISSUE
- This is not a feature, it is a known issue and will by purpose not be changed.
- Known Issue is an end status, there is no further decision taken.
CLARIFY
- The feature has to be first discussed before a further state is decided.
- The feature can be then Dismissed or Accepted.
DISMISSED or ACCEPTED
- In case the feature is NOT going to be implemented and not going to be considered for future releases, it will be set to Dismissed.
- Dismissed is an end status, there is no further decision taken.
- In case the feature inlcude valid requirements and is going to be implemented, it will be set to Accepted.
- At that point, the Development of the feature can be initiated.
DEFERRED
- The feature is going to be developed because it has been Accepted.
- Even though, the feature is not going to be developed for the next planned release. Instead, the feature is deferred for later consideration.
- Another future Release will be assigned to it in order for this feature to be developed.