Scope
- Feature Life Cycle Management includes features being subject to a Planning Cycle:
- new features are planned and specified before being
New Features might be - developed and included in
next Releases - these Features need to be planned though- future releases.
- having passed the Planning Cycle new features are subjec to a Development Cycle.
- This article describes our handling this situation and its mapping with the states in the SOS
- Further resources for life cycle management
Life Cycle
Planned features will pass through the following statesbegin-of-life cylce with the following status before a decision is taken whether they will be developed or not:
...
- A feature or bug has been described and assignedadded but might not yet be assigned to any developer or release.
- Open issues are assigned a release and are worked on in the course of this release.
- The next step will be to decide, whether the feature is a Known Issue or it has to be Clarifiedto CLARIFY the feature, i.e. to collect requirements and to decide on future development.
- The feature or bug has to be specified before any further status is assigned. This includes to check the validity of requirements and the feasibility.
- Issues for clarification are assigned a release and are worked on in the course of this release.
- Users are invited to vote for the feature and to comment by adding use cases and requirements that help to specify the feature.
- 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 or bug is classified as a known issue, i.e. as an inconvenience with a valid workaround available, and will by purpose not be changed.
- Known issues are not assigned a release.
- Being a known issue Issue is an end status for a feature, there is therefore no further decision action will be taken.
- The issue is assigned one of the resolutions
- the feature works as designed (resolution:
works as designed
). - the issue not being fixed (resolution:
won't fix
).
...
...
- The feature has to be first discussed before a further state is decided
- The feature can be then dismissed or accepted.
...
- or bug is dismissed, e.g. due to architectural constraints or invalid requirements. The feature is not considered for future development.
- Dismissed Issues are assigned a release and are worked on in the course of this release.
- Being dismissed is an end status for a feature, therefore no further action will be taken.
- The issue is assigned one of the resolutions:
- the feature works as designed (resolution:
works as designed
). - the issue is caused by misconfiguration or misapprehension of the underlying functionality (resolution:
bogus
). - the issue not being fixed (resolution:
won't fix
). - the issue duplicating an issue and being resolved with that issue (resolution:
duplicate
) - the feature requirements being incomplete (resolution:
incomplete
). - the bug cannot be reproduced (resolution:
cannot reproduce
).
...
Status |
---|
| |
---|
colour | Yellow |
---|
title | ACCEPTED |
---|
|
- The feature or bug 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 Cycle
- In case the feature is NOT going to be implemented, it will be set to Dismissed.
- Dismissed is an end status, there is no further decision taken.
- In case the feature 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 Acceptedwill be considered for development in a future release.
- HoweverEven though, the feature is not going to be developed for the Planned Release.Another future Release will be assigned to it in order for this feature to be developed.assigned to a release. Instead, the feature is deferred for later consideration.
- The issue has no resolution assigned (resolution:
Unresolved
). Therefore the issue can be voted by the users in order for the company to prioritize these issues for future releases.