Scope
- New features might be are subject to a Planning Cycle before being developed and included in future Releases - these features need to be planned thoughreleases.
- This article describes our the policy for handling this situation feature planning and its mapping with to the states respective status in the SOS Change Management System.
...
Planned features will pass through the begin-of-life cylce with the following states status before it a decision is decided taken whether they are going to will be developed or not:
...
- A feature has been described and assignedadded but might not yet be assigned to any developer or release.
- The next step will be to decide, whether the feature is a Known Issue or it has to be ClarifiedCLARIFY the feature, i.e. to collect requirements and to decide on future development.
- The feature has to be specified before any further status is assigned. This includes to check the validity of requirements and the feasibility.
- Subsequent to clarification the feature will then be ACCEPTED or DEFERRED for development, or it will be DISMISSED or classified as KNOWN ISSUE without further action.
| Status |
|---|
| colour | Green |
|---|
| title | KNOWN ISSUE |
|---|
|
- This is not a feature, it is The feature is classified as a known issue, i.e. as an inconvenience with a valid workaround available, and will by purpose not be changed.
- Known Issue Being a known issue is an end status for a feature, there is therefore no further decision action will be taken.
...
...
- The feature has to be first discussed before a further state is decided.
- The feature can be then Dismissed or Accepted.
...
- is dismissed, e.g. due to architectural constraints or invalid requirements. The feature is not considered for future development.
- Being dismissed is an end status for a feature, therefore no further action will be taken.
| Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | ACCEPTED |
|---|
|
- The feature includes valid requirements and is accepted for development with the assigned release.
- Subsequently the feature will proceed through the Development Cycle, see Release Policy - Development
...
- 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.
- The feature is going to be developed because it has been Accepted.will be considered for development in a future release.
- HoweverEven though, the feature is not going to be developed for the next planned releaseassigned to one of the planned releases. Instead, the feature is deferred for later consideration.Another future Release will be assigned to it in order for this feature to be developed.