Maxxton is having multiple teams working on our software sprint-in, sprint-out. A sprint is a given time frame of two weeks in which all functionlity requests or reported issues are scheduled to be fixed by a developer. Those sprints are lasting two weeks and starting on mondays. There is a specific way of how this software gets 1) developed 2) tested and afterwards 3) deployed to production. Methods are described below:
During the sprint, developers are releasing code changes to the development environment. The first swimlane is representing this. As you can see in the diagram below, that takes 2 weeks which is equal to the sprint duration.
A sprint ends on the second Thursday of a sprint. At that specific Thursday, all code changes from the last two weeks will be released to the acceptance environment. This is done so that our QA department can start testing functionalities and possible errors can still be fixed before the code is released to production next Wednesday. This acceptance software will remain there until the next acceptance release.0,
In the week after a sprint ends (for instance sprint B), a new sprint is started (sprint C). However, on the first Thursday of sprint C all the changes of the previous sprint B are updated to the production environment.
Please note:
The staging environments are only available on request and additional costs will be charged for hosting and maintenance.
MXTS users can subscribe to the Release notes - Maxxton Software