From faf0bd92829746889f7449164bf272c453aebe19 Mon Sep 17 00:00:00 2001 From: Trueblueaddie <102972456+Trueblueaddie@users.noreply.github.com> Date: Sun, 4 Dec 2022 17:29:33 -0600 Subject: [PATCH 1/9] Create fixing-issues-step-by-step.md --- .../fixing-issues-step-by-step.md | 43 +++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 patterns/2-structured/fixing-issues-step-by-step.md diff --git a/patterns/2-structured/fixing-issues-step-by-step.md b/patterns/2-structured/fixing-issues-step-by-step.md new file mode 100644 index 000000000..14f058614 --- /dev/null +++ b/patterns/2-structured/fixing-issues-step-by-step.md @@ -0,0 +1,43 @@ +## Title + +Fixing Issues Step by Step + +## Patlet + +Solving an issue by deadline without consideration of the current scope of change to process causes developer frustration and decreased efficiencies. Utilize a continuous improvement approach which right-sizes the work and provides realistic expectations. + +## Problem + +Results are expected to take place within a few days/weeks after a process has started. Adding a process or a toolchain by itself will not provide any result by itself beyond developer frustration. Stating that something has to work by a certain deadline will not make it possible, this will just force the situation and workarounds will be done by developers. + +## Forces + +Understanding step changes in a process requires adequate time and clarity of impact +Clarity of impact to the process and delivery pressure are deterrents to change + +## Solutions + +When planning new steps, set the way that step is successful if compared to others. Follow a continuous improvement approach and measure the delta between steps. + +## Resulting Context + +Expectations are aligned and realistic in terms of the improvement path of the organization. A continuous improvement is required and understood. + +## 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 From 50f48933b62b06e25a2a3781ccc1ef49e56814ea Mon Sep 17 00:00:00 2001 From: Trueblueaddie <102972456+Trueblueaddie@users.noreply.github.com> Date: Wed, 7 Dec 2022 05:53:49 -0600 Subject: [PATCH 2/9] Update fixing-issues-step-by-step.md --- patterns/2-structured/fixing-issues-step-by-step.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/patterns/2-structured/fixing-issues-step-by-step.md b/patterns/2-structured/fixing-issues-step-by-step.md index 14f058614..34536bee9 100644 --- a/patterns/2-structured/fixing-issues-step-by-step.md +++ b/patterns/2-structured/fixing-issues-step-by-step.md @@ -23,11 +23,11 @@ When planning new steps, set the way that step is successful if compared to othe Expectations are aligned and realistic in terms of the improvement path of the organization. A continuous improvement is required and understood. -## Known Instances +## Known Instances Santander Bank -## Status +## Status Structured Published internally in Santander Bank; drafted via pull-request in December of 2022 @@ -38,6 +38,6 @@ Alberto Pérez García-Plaza Daniel Izquierdo Cortázar Addie Girouard -## Acknowledgements +## Acknowledgements Igor Zubiaurre From 9a9e8336a7ce6e153bc29d895e502b5d3c666b7f Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 11 Mar 2023 15:25:34 +0100 Subject: [PATCH 3/9] Rewording Co-authored-by: Igor Zubiaurre --- patterns/2-structured/fixing-issues-step-by-step.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patterns/2-structured/fixing-issues-step-by-step.md b/patterns/2-structured/fixing-issues-step-by-step.md index 34536bee9..971a22aa4 100644 --- a/patterns/2-structured/fixing-issues-step-by-step.md +++ b/patterns/2-structured/fixing-issues-step-by-step.md @@ -8,7 +8,7 @@ Solving an issue by deadline without consideration of the current scope of chang ## Problem -Results are expected to take place within a few days/weeks after a process has started. Adding a process or a toolchain by itself will not provide any result by itself beyond developer frustration. Stating that something has to work by a certain deadline will not make it possible, this will just force the situation and workarounds will be done by developers. +Results are expected to take place within a few days/weeks after a process has started. Adding a process or a toolchain will not provide any result by itself beyond developer frustration. Stating that something has to work by a certain deadline will not make it possible. This will just force the situation, and workarounds will be done by developers. ## Forces From 4771d5ea981ebe8bdff2f7cbd5a8647cc68bf3de Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 11 Mar 2023 15:26:29 +0100 Subject: [PATCH 4/9] Adding initial Context section Co-authored-by: Igor Zubiaurre --- patterns/2-structured/fixing-issues-step-by-step.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/patterns/2-structured/fixing-issues-step-by-step.md b/patterns/2-structured/fixing-issues-step-by-step.md index 971a22aa4..c070685ee 100644 --- a/patterns/2-structured/fixing-issues-step-by-step.md +++ b/patterns/2-structured/fixing-issues-step-by-step.md @@ -10,6 +10,11 @@ Solving an issue by deadline without consideration of the current scope of chang Results are expected to take place within a few days/weeks after a process has started. Adding a process or a toolchain will not provide any result by itself beyond developer frustration. Stating that something has to work by a certain deadline will not make it possible. This will just force the situation, and workarounds will be done by developers. +## Context + +* Developer frustration is spread and at high levels. Complaints about pressure and stress. +* Clumpsy workarounds, undocumented and/or prone to be broken/voided are frequent. +* Voluntary contributions are scant. ## Forces Understanding step changes in a process requires adequate time and clarity of impact From 13d06c35f2d62d200b8ad46ac2ad454961f6f079 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 11 Mar 2023 15:26:53 +0100 Subject: [PATCH 5/9] Fix spacing --- patterns/2-structured/fixing-issues-step-by-step.md | 1 + 1 file changed, 1 insertion(+) diff --git a/patterns/2-structured/fixing-issues-step-by-step.md b/patterns/2-structured/fixing-issues-step-by-step.md index c070685ee..dd0516a36 100644 --- a/patterns/2-structured/fixing-issues-step-by-step.md +++ b/patterns/2-structured/fixing-issues-step-by-step.md @@ -15,6 +15,7 @@ Results are expected to take place within a few days/weeks after a process has s * Developer frustration is spread and at high levels. Complaints about pressure and stress. * Clumpsy workarounds, undocumented and/or prone to be broken/voided are frequent. * Voluntary contributions are scant. + ## Forces Understanding step changes in a process requires adequate time and clarity of impact From 155dfa97a38d24041e4845ae5312aa925cd4d53a Mon Sep 17 00:00:00 2001 From: Trueblueaddie <102972456+Trueblueaddie@users.noreply.github.com> Date: Thu, 23 Mar 2023 18:20:57 -0500 Subject: [PATCH 6/9] Apply suggestions Co-authored-by: Igor Zubiaurre --- patterns/2-structured/fixing-issues-step-by-step.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/patterns/2-structured/fixing-issues-step-by-step.md b/patterns/2-structured/fixing-issues-step-by-step.md index dd0516a36..b0b978f10 100644 --- a/patterns/2-structured/fixing-issues-step-by-step.md +++ b/patterns/2-structured/fixing-issues-step-by-step.md @@ -5,7 +5,7 @@ Fixing Issues Step by Step ## Patlet Solving an issue by deadline without consideration of the current scope of change to process causes developer frustration and decreased efficiencies. Utilize a continuous improvement approach which right-sizes the work and provides realistic expectations. - +A baby-step development culture fosters external contributions (more opportunities for engaging, less to learn, less to comply with, less to document, less to review). This culture reflects in the open source mantra _["Release early, release often"](https://en.wikipedia.org/wiki/Release_early,_release_often)_. ## Problem Results are expected to take place within a few days/weeks after a process has started. Adding a process or a toolchain will not provide any result by itself beyond developer frustration. Stating that something has to work by a certain deadline will not make it possible. This will just force the situation, and workarounds will be done by developers. @@ -18,16 +18,23 @@ Results are expected to take place within a few days/weeks after a process has s ## Forces -Understanding step changes in a process requires adequate time and clarity of impact -Clarity of impact to the process and delivery pressure are deterrents to change +Understanding step changes in a process requires adequate time and clarity of impact. +Lack of clarity of impact on the process and delivery pressure are deterrents to change. ## Solutions When planning new steps, set the way that step is successful if compared to others. Follow a continuous improvement approach and measure the delta between steps. +Splitting targets into smaller bits multiplies the opportunities for engagement. And they are more attractive too, because they require less to learn, less to comply with, less to document, and less to review (reviews are contributions too). + +When reviewing contributions, don't strive for perfection and approve them as soon as there's a tangible improvement (regressions must be avoided, of course). +Lurkers will feel that the (small) achievement is within their reach and will convince them to contribute. This bootstraps a virtuous cycle, as more frequent and diverse contributions also seduce other lurkers to join the party. ## Resulting Context Expectations are aligned and realistic in terms of the improvement path of the organization. A continuous improvement is required and understood. +Contributors feel like they can contribute partial improvements without the need to solve all problems at once. +Contributions are small and can be reviewed swiftly. +Trusted Committers accept contributions or partial or imperfect solutions if they provide enough value to improve the previous status. Pointers on how to perfect the contribution become comments instead of mandates. ## Known Instances From 16c422a8caa282d48c3939750ac85346e26a1ccd Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Fri, 24 Mar 2023 13:22:18 +0100 Subject: [PATCH 7/9] Add spacing before header Co-authored-by: Igor Zubiaurre --- patterns/2-structured/fixing-issues-step-by-step.md | 1 + 1 file changed, 1 insertion(+) diff --git a/patterns/2-structured/fixing-issues-step-by-step.md b/patterns/2-structured/fixing-issues-step-by-step.md index b0b978f10..83554e20c 100644 --- a/patterns/2-structured/fixing-issues-step-by-step.md +++ b/patterns/2-structured/fixing-issues-step-by-step.md @@ -6,6 +6,7 @@ Fixing Issues Step by Step Solving an issue by deadline without consideration of the current scope of change to process causes developer frustration and decreased efficiencies. Utilize a continuous improvement approach which right-sizes the work and provides realistic expectations. A baby-step development culture fosters external contributions (more opportunities for engaging, less to learn, less to comply with, less to document, less to review). This culture reflects in the open source mantra _["Release early, release often"](https://en.wikipedia.org/wiki/Release_early,_release_often)_. + ## Problem Results are expected to take place within a few days/weeks after a process has started. Adding a process or a toolchain will not provide any result by itself beyond developer frustration. Stating that something has to work by a certain deadline will not make it possible. This will just force the situation, and workarounds will be done by developers. From 23ae945d720c6e4552c4eae3339d61dd64ca45ae Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Fri, 24 Mar 2023 13:22:26 +0100 Subject: [PATCH 8/9] Add spacing before header Co-authored-by: Igor Zubiaurre --- patterns/2-structured/fixing-issues-step-by-step.md | 1 + 1 file changed, 1 insertion(+) diff --git a/patterns/2-structured/fixing-issues-step-by-step.md b/patterns/2-structured/fixing-issues-step-by-step.md index 83554e20c..7e38ddc44 100644 --- a/patterns/2-structured/fixing-issues-step-by-step.md +++ b/patterns/2-structured/fixing-issues-step-by-step.md @@ -30,6 +30,7 @@ Splitting targets into smaller bits multiplies the opportunities for engagement. When reviewing contributions, don't strive for perfection and approve them as soon as there's a tangible improvement (regressions must be avoided, of course). Lurkers will feel that the (small) achievement is within their reach and will convince them to contribute. This bootstraps a virtuous cycle, as more frequent and diverse contributions also seduce other lurkers to join the party. + ## Resulting Context Expectations are aligned and realistic in terms of the improvement path of the organization. A continuous improvement is required and understood. From bb0fd615992d3620cfb6364d59ea139412ccfe14 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Fri, 24 Mar 2023 13:30:49 +0100 Subject: [PATCH 9/9] Removing trailing space --- patterns/2-structured/fixing-issues-step-by-step.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patterns/2-structured/fixing-issues-step-by-step.md b/patterns/2-structured/fixing-issues-step-by-step.md index 7e38ddc44..639e5ca27 100644 --- a/patterns/2-structured/fixing-issues-step-by-step.md +++ b/patterns/2-structured/fixing-issues-step-by-step.md @@ -29,7 +29,7 @@ Splitting targets into smaller bits multiplies the opportunities for engagement. When reviewing contributions, don't strive for perfection and approve them as soon as there's a tangible improvement (regressions must be avoided, of course). -Lurkers will feel that the (small) achievement is within their reach and will convince them to contribute. This bootstraps a virtuous cycle, as more frequent and diverse contributions also seduce other lurkers to join the party. +Lurkers will feel that the (small) achievement is within their reach and will convince them to contribute. This bootstraps a virtuous cycle, as more frequent and diverse contributions also seduce other lurkers to join the party. ## Resulting Context