As an agile software company, we unfortunately cannot make any reliable promises beyond a planning horizon of 14 days. There are plans, some of which go well beyond two weeks, but these are not always reliable. The further in the future a planned release date is, the more uncertain it is that it will actually be met at that exact time.
The following table lists the status we use to make planning for a feature request as transparent as possible. Each status can contain multiple topics at the same time. For example, a topic in the After state is not immediately processed once another topic in the Next state has been delivered. First, all or most topics in the Next state must be completed – this can take anywhere from a few weeks to a few months.
Status | Declaration |
Next | This is up to come within one of the next versions. |
After | Currently scheduled to be done after Next. |
No Scope | Currently not scheduled but reasonable to be done. |
Non Strategic | Currently not included in our strategy –means unlikely to be implemented in the near future. |