Skip to content

Instantly share code, notes, and snippets.

@igabesz
Last active June 9, 2023 05:50
Show Gist options
  • Save igabesz/3892a6ceaf80d52046cc6cde260e7b1b to your computer and use it in GitHub Desktop.
Save igabesz/3892a6ceaf80d52046cc6cde260e7b1b to your computer and use it in GitHub Desktop.
[Blog] BaU-vs-Systematic
Business as Usual Systematic Improvements
== Impact ==
Immediate impact Usual Usually none
Changes in code quality Slow Can be fast
Risk of results Usual High (usually uncertain)
Leverage None-to-low Potentially high
Available Always During calm times
== Nature ==
Typical Tasks Features, bugs, maintenance Research, devenv, architecture, various
Uncertainty / risk of estimations Usual (low for established teams) High
Scope Mostly well-knows areas New, unknown areas
== Methodology ==
Estimation Story points Time-boxing
Divide the problems Well defined tasks Create subtasks on the go
Acceptance Clear acceptance criteria Step-by-step
Tickets Various tickets Tasks, sub-tasks, Spikes
== Skill-sets ==
Required tech skill level Usually medior-level Higher; often senior-level
Required tech areas Usual ones New areas are often involved
Required other skills None Discovery, making connections, communicating results
== Communication ==
PO & Stakeholder level Usual Educated POs and stakeholders
Ease of communication Easy Difficult
Visibility of results Immediately (feature/fix) Over time (shipping speed)
Measurable Sprint velocity (based on history) Sprint velocity after months/quarters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment