Do you know of any agile process that has been created for code release? One of the main topics of Tough continues continues and each company / customer has its own exam / approval process, which controls the code release. Most of the time it slows down the speed of "continuous release"
We currently have a proprietary tool-based workflow which encourages promotion of any one of the final UAT servers, which requires code enforcement Need to create. Once this is done, and once the test is done, some customers, technical / non-technical managers need to be approved, then this product goes into the deployment phase. Meanwhile there is no sprint appointment meeting or anything about that thing.
What is the process of code release (which is fickle) that has worked for you?
Why does not any kind of sprinter planning meet if there is workflow income? Tag your repository and go immediately with the next release. If you need a bug fix on the candidate's release, then branch from the tag and fix them. The approval workflow and the final UAT test should not be involved or delayed either by the development team. (If you are actually on things like guit or mercurial, forgive the non-distributed SCM terminology.)
If you take a playful process like Scaram, the release output is not "Reliable Software" Is "released software". If you have an overhead on the material released for production, then it can be in parallel. I should add that most tests occur as part of the sprint - maybe you have to re-examine what test is done in your cycle?
Comments
Post a Comment