Implementation
At an agreed point there has been enough developed that you are ready for a first release, this opens up a new dynamic, working with your users in a live operating environment.
Until now everything has been in a safe testing environment, one that can be thrown away and started again at the drop of a hat. Now you need to hold data, ensure continuity of the data, the service and the customers expectation.
Release
Release plan and automation is created to allow rapid updates and ensure that new updates can be “undone” if required.
Once a release has happened there is a period of “heightened vigilance” from both the developers and support team to ensure the running environment is stable and operating as expected.
Redgum provide a Continuous Improvement budget under our Support arrangement. This is a not to be exceeded monthly allocation for adhoc improvements, adjustments and minor planned work.
Warranty
Once you have signed off on a release and rolled it out to production Redgum provide a 3 month, not to spec warranty meaning that if it doesn’t meet the agreed requirements set down in the Engineering step Redgum will fix it.
If it does meet the engineering but you would like it to do something different, we can make those adjustments but they are not warranty claims, they are addressed under the Continuous Improvement budget.
There is always some grey areas between these two definitions and we work with you to come to an agreed outcome on a case by case basis.
Redprint Adaptive Deliver Process.
Redgums adaptive framework applied to manage the varying risks of a broad range of projects.