For product back-end developments, we are using an eight week long development cycle that includes two sprints that last two weeks each and generally ends with a planned release:
- Tasks are planned based on client’s order number (given by client’s project manager).
- Each client gets a percentage of development hours for each sprint (agreed on beforehand with a business manager).
- Scope is fixed three weeks before the cycle’s end at the latest.
- Tasks are done in development environment that uses a continuous integration and deployment practice, i.e. task is ready for Q&A team as soon as the developer is finished with it.
- Q&A team has different testing environments depending on where we are in a development cycle.
- After two development sprints, Q&A team will start testing in pre-live environment that lasts for one week (task based testing, regression testing and general load testing).
- After that, the client can start testing in pre-live environment, one week is for testing and the last week is for end user training.
- Pre-live environment will get bug fixes as soon as possible, but no new requirements will be implemented.
- Acceptance is needed from client’s project manager one week before the planned release at the latest.
- Cycle ends with a release.
Turnit 8-week development cycles are overlapping. When development finishes during one cycle, the next cycle starts so that the release frequency is every five weeks. It is possible for the client to skip releases, but not more than two sequential releases. This means that there will be 5-10 major annual releases depending on client’s decision on frequency.
We are developing mainly on Microsoft.Net framework using C#. The main tools and programming languages used are described on the Technology page.