From e043ea90c641363ddf5075d9ade3a2b05734de13 Mon Sep 17 00:00:00 2001 From: Trueblueaddie <102972456+Trueblueaddie@users.noreply.github.com> Date: Sun, 4 Dec 2022 16:03:04 -0600 Subject: [PATCH 1/2] Create business-time-pressures.md --- .../2-structured/business-time-pressures.md | 53 +++++++++++++++++++ 1 file changed, 53 insertions(+) create mode 100644 patterns/2-structured/business-time-pressures.md diff --git a/patterns/2-structured/business-time-pressures.md b/patterns/2-structured/business-time-pressures.md new file mode 100644 index 000000000..4ac44c4cc --- /dev/null +++ b/patterns/2-structured/business-time-pressures.md @@ -0,0 +1,53 @@ +## Title +Business Time Pressures + +## Patlet + +Development releases can become pressurized by business causing needed steps to be dropped in favor of delivery. Continuous release cycle is upheld to ensure code quality and new requests are moved into next development phases. + +## Problem + +Time drives development in most cases. It is not a problem per se, difficulties appear when some unfinished features need to be hidden to release or new unplanned features suddenly appear to be included in the next release. As a result, delivered artifacts usually contain too many changes and that makes their testing, deployment and maintenance difficult. One example is delaying complete testing to later stages, creating a lag in deployment originated from the difficulties for performing local tests of big amounts of code. +No proper code review in place. -> Middle Managers & Dev InnerSource Learning Path, Undocumented or Non-existent Code Revie Process +No proper testing in place. Testing is done during delivery to PRE in some cases. Delivery is delayed because errors are detected late. -> Late Delivery pattern +No time scheduled to tackle the previous two points. -> PO, Middle Managers & Dev InnerSource Learning Path +PO jumps over scheduled things to add new features. -> PO InnerSource Learning Path. + +## Forces + +Against: +Deadlines do not change. +Good testing provides stability. Stability is needed for faster delivery. + +## Solutions + +Known anti-pattern: surreptitious temporary fork, no communication. +Split contributions in small changes that can be easily reviewed and tested. +Allocate time for a proper code review process, based on a commonly established set of guidelines and automated tests. + +## Resulting Context + +New requirements are naturally moved into next development phases. Development teams are not forced to add late functionalities as there is a continuous release cycle. + +## Known Instances + +Santander Bank + +## Status + +Structured +Published internally in Santander Bank; drafted via pull-request in December of 2022 + +## Authors + +Alberto Pérez García-Plaza +Daniel Izquierdo Cortázar +Addie Girouard + +## Acknowledgements + +Igor Zubiaurre + +## Related + +Time Constraints Hamper Inner Source Progress pattern that can be found in the Appendix document. From add6b1168406ad3b6b0e9a89f37c1e45e024b558 Mon Sep 17 00:00:00 2001 From: Sebastian Spier <github@spier.hu> Date: Tue, 6 Dec 2022 14:10:19 +0100 Subject: [PATCH 2/2] Fix warnings from GHA checks --- patterns/2-structured/business-time-pressures.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/patterns/2-structured/business-time-pressures.md b/patterns/2-structured/business-time-pressures.md index 4ac44c4cc..c563727e7 100644 --- a/patterns/2-structured/business-time-pressures.md +++ b/patterns/2-structured/business-time-pressures.md @@ -1,9 +1,10 @@ ## Title + Business Time Pressures ## Patlet -Development releases can become pressurized by business causing needed steps to be dropped in favor of delivery. Continuous release cycle is upheld to ensure code quality and new requests are moved into next development phases. +Development releases can become pressurized by business causing needed steps to be dropped in favor of delivery. Continuous release cycle is upheld to ensure code quality and new requests are moved into next development phases. ## Problem @@ -13,6 +14,10 @@ No proper testing in place. Testing is done during delivery to PRE in some cases No time scheduled to tackle the previous two points. -> PO, Middle Managers & Dev InnerSource Learning Path PO jumps over scheduled things to add new features. -> PO InnerSource Learning Path. +## Context + +* ??? + ## Forces Against: @@ -29,11 +34,11 @@ Allocate time for a proper code review process, based on a commonly established New requirements are naturally moved into next development phases. Development teams are not forced to add late functionalities as there is a continuous release cycle. -## Known Instances +## Known Instances Santander Bank -## Status +## Status Structured Published internally in Santander Bank; drafted via pull-request in December of 2022 @@ -44,7 +49,7 @@ Alberto Pérez García-Plaza Daniel Izquierdo Cortázar Addie Girouard -## Acknowledgements +## Acknowledgements Igor Zubiaurre