Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create fixing-issues-step-by-step.md #503

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open
Changes from 6 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
56 changes: 56 additions & 0 deletions patterns/2-structured/fixing-issues-step-by-step.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
## 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.
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
spier marked this conversation as resolved.
Show resolved Hide resolved

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.
spier marked this conversation as resolved.
Show resolved Hide resolved

spier marked this conversation as resolved.
Show resolved Hide resolved
## Forces

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).

Trueblueaddie marked this conversation as resolved.
Show resolved Hide resolved
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.
spier marked this conversation as resolved.
Show resolved Hide resolved
## Resulting Context
spier marked this conversation as resolved.
Show resolved Hide resolved

Expectations are aligned and realistic in terms of the improvement path of the organization. A continuous improvement is required and understood.
Trueblueaddie marked this conversation as resolved.
Show resolved Hide resolved
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

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