Planning

Planning is the process that manages incoming requirements, issues to be estimated, coordinated, implemented, and delivered.

Service Desk

Requirements (features, changes), issues are submitted via our service desk portal will be received in the form of a new task. According to their priority, they will be selected for review.

  • It's very important that tasks are only submitted through one channel. Mail, phone, chat, etc. is subject to unintentional forgetting and an inability to follow. Every task has its own beginning, process of resolution, and end (when the task is done) because of which it's important to have all in one place.

  • Bug reports, should never contain an explanation of missing function, which requires implementation.

Review

All received requirements and issues are internally reviewed by the development team, and the requirement realization time is estimated. If additional information is required, the client will receive a notification.

Planning

In this phase together with the client, task will be assigned to an appropriate type of release (as described in releases). This process is supported by the estimated implementation time of each task and also the available resources on each release, allowing us to plan the delivery time more precisely.

Changes

Actions when responding to sudden changes during Releases.

Every project lead, at some point, must face requirements changing within the on-going release. This can be a result of an impacting Bug, or urgent changes related to logical problems in the product.

  • Canceling the release and re-plan.

  • Find the balance without disturbing the flow of the release

    (accept some changes, other move to next release, or cancel tasks).

Most importantly, in any case, the Project Lead (PL) first needs to communicate with the team to know what is or isn't possible. And then present the findings to the Client for finding an agreement

Release Planning

To provide a consistent delivery of features and maintain the stability of the application, we plan simultaneous releases.

Feature Release

The release containing new functionalities, estimated and assigned together with the client, has a delivery time of > 2 weeks.

Support Release

Running parallel to the feature release, delivery every Thursday contains tasks, issues that require a quick reaction time and less effort.

HotFix Release

Dynamically create when its required to fix a critical issue on production

Last updated