Timeline for How to deal with half my colleagues overriding development processes under the slightest pressure?
Current License: CC BY-SA 4.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 8, 2020 at 18:09 | comment | added | mwigdahl | If the "cursory" risk analysis also includes an accounting for opportunity cost and some reasonable estimate on how many bugs are actually caught by the elements of the process, sure. Where the company is at in its lifecycle will have a huge impact on what level of process is reasonable. | |
Jul 8, 2020 at 17:38 | comment | added | brokethebuildagain | I don't think insisting on nobody merging directly to master is really a case of the business serving the process. It's a matter of protecting yourself and your customers. I can't see a business case where you would lose opportunity or revenue by not even running a quick set of regression tests. Do you really need "hard data" when there are plenty of examples (sometimes in international news) of what happens to organizations that don't properly test/audit their software? A cursory risk assessment is all you need to prove the worth of the process IMO. | |
Jul 8, 2020 at 16:19 | comment | added | mwigdahl | The process exists to serve the business, not the other way around. Defending the process may very well be the right thing to do, but it is not a matter of dogma. Sound risk analysis and differential bug tracking can help to quantify the pain not adhering to the process is causing the business. Does that outweigh the cost of lost opportunities by missing the "urgent" deadlines? It could go either way, but whichever way, having hard data will bolster any case for change. | |
S Jul 8, 2020 at 12:48 | history | edited | JohnSomeone | CC BY-SA 4.0 |
Copy edited (e.g. ref. <https://en.wikipedia.org/wiki/GitHub> and <https://en.wikipedia.org/wiki/GitLab>). Used more standard formatting (we have italics and bold on this platform).
|
S Jul 8, 2020 at 12:48 | history | suggested | Peter Mortensen | CC BY-SA 4.0 |
Copy edited (e.g. ref. <https://en.wikipedia.org/wiki/GitHub> and <https://en.wikipedia.org/wiki/GitLab>). Used more standard formatting (we have italics and bold on this platform).
|
Jul 8, 2020 at 12:18 | review | Suggested edits | |||
S Jul 8, 2020 at 12:48 | |||||
Jul 7, 2020 at 17:48 | history | answered | brokethebuildagain | CC BY-SA 4.0 |