3 ms·
You should be aiming to release on at least a weekly cadence, preferably daily or possibly multiple times a day. Why? 1) If a bug is found in production it's mo
by twunde 8y ago
You should be aiming to release on at least a weekly cadence, preferably daily or possibly multiple times a day. Why? 1) If a bug is found in production it's more likely that the dev that built it still has context on what they did. The dev will most likely be able to fix the bug faster if told within a week about the issue. 2) For customers its amazing to be able to see a bug fixed within a day or two.
The caveats. There may be legitimate challenges to deploying often that you will have to overcome. Some industries (such as FDA-regulated industries) require documentation and some specialized testing. If you have a change management board, you will probably need to work with your compliance/security team to change the signoff process to something more light-weight that still addresses the risks/requirements. If you have manual testing, you will need to automate some of the testing. A lot of this requires work done to automate steps.