Session
Get in control on release management
This session explains how Developers and the Customer collaborate on a successful implementation.
With this collaboration the next common pitfalls should not occur anymore:
o Code in production that is not tested
o Customer did not test.
o Developer released it and the customer did not know.
o Code not in the release and the customer has tested. (can this; unfortunately, it happens)
o Code Incomplete
o Code disappears.
o Not clear why code is changed.
Above scenario result in disturbing of the production and unnecessary delay for a correct release candidate. These scenarios occur because there is not a clear view on the status of all change request or the status of the change request. But it can also be addressed to the way the release candidate is created. (Not using combined builds)
Dick Wenning
Technical fellow / Solution architect
Veenendaal, The Netherlands
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top