7. Learning Scrum – Shu Ha Ri
Vanilla Scrum Beyond Scrum?ScrumAnd
ScrumBut
Shuhari roughly translates to "first learn, then detach, and finally transcend."
•shu (守) "protect", "obey" — traditional wisdom — learning fundamentals, techniques, heuristics, proverbs
•ha (破) "detach", "digress" — breaking with tradition — detachment from the illusions of self
•ri (離) "leave", "separate" — transcendence — there are no techniques or proverbs, all moves are natural,
becoming one with spirit alone without clinging to forms; transcending the physical
Thanks to Alistair Cockburn & Martin Fowler
Scrum doesn’t work?
15. ScrumAnd
“…When I was on my first Agile project, Ward Cunningham, one of our
project coaches, said to me “Mitch, you need to adopt the XP
engineering practices of TDD, pairing, refactoring and continuous
integration or you’ll be sorry.” I dismissed this claim as I knew what I
was doing. It was not until we were four sprints in when we all realized
that we were screwed….”
Thanks to Mitch Lacey
16. ScrumAnd – Popular Addons (1/23)
We estimate in points… or maybe #NoEstimates at all!
40. ScrumBut
(ScrumBut) (Reason) (Workaround)
Thanks to Ken Schwaber & Ron Jeffries
We use Scrum, but
having a Daily Scrum
every day is too much
overhead, so we only
have one per week.
We use Scrum, but
Retrospectives are a
waste of time, so we
don't do them.
We’re doing
Scrum, but
Retrospectives
aren’t effective, so
we only do them
monthly.
We’re doing Scrum, but
our stakeholders are
too busy to come to
Sprint Reviews, so we
stopped doing them.
We’re doing Scrum, but
we couldn’t get
everything done in two
weeks, so now we just let
our Sprints run as long as
they need to
41. ScrumBut – “Popular” modifications (1/33)
Our team members think of “my“ sprint / tasks / stories / story points
instead of “our” sprint / tasks / stories / story points
42. ScrumBut – “Popular” modifications (2/33)
We have a waterfall inside the sprint (testing only starts after all the coding
is “done”)
43. ScrumBut – “Popular” modifications (3/33)
We have QAs / Testers working outside the team / sprint
44. ScrumBut – “Popular” modifications (4/33)
QAs don’t speak to Devs whenever they find bugs (processes and tools
over individuals and interactions)
45. ScrumBut – “Popular” modifications (5/33)
The team works for the KPIs and not for the (potential) value delivered
46. ScrumBut – “Popular” modifications (6/33)
The team can't implement (technically) a story without the Dev Lead
(or Architect)
48. ScrumBut – “Popular” modifications (8/33)
The PO is a “chicken” (isn’t allowed to speak in Dailies and can’t attend
Retrospectives)
49. ScrumBut – “Popular” modifications (9/33)
We use 6 to 12 weeks sprints (instead of 1 to 4 weeks) to “avoid pain” /
“disguise problems” (e.g. releases, manual regression testing, deploys to
test environments)
50. ScrumBut – “Popular” modifications (10/33)
After a sprint we “stop” for 1 week of acceptance tests / bugfixing /
stabilization (non consecutives sprints)
51. ScrumBut – “Popular” modifications (11/33)
Team members arrive late to scrum ceremonies
52. ScrumBut – “Popular” modifications (12/33)
We have titles inside the team (Associate, Senior, etc.)
54. ScrumBut – “Popular” modifications (14/33)
Besides a Product Backlog we also have a Technical Backlog and a Bugs
Backlog (so you can guess which backlog as higher priority)
55. ScrumBut – “Popular” modifications (15/33)
We have Daily scrums away from the physical / virtual board
56. ScrumBut – “Popular” modifications (16/33)
We do Big Design Up Front (BDUF) instead of favoring emerging
architectures and the Lean & XP concepts Last Responsible Moment (LRM),
You Aren’t Gonna Need It (YAGNI) and Just in Time (JIT)
57. ScrumBut – “Popular” modifications (17/33)
We only have one person on our development team
58. ScrumBut – “Popular” modifications (18/33)
In groomings / refinements the Scrum Master assigns user stories to
developers (command and control vs self-organizing)
59. ScrumBut – “Popular” modifications (19/33)
In Sprint Planning we focus more in having everybody busy (due to
specializations) instead of focusing on the maximum value we can deliver
(output)... So we cherry pick / choose the stories that go in the sprint by
the skills / comfort zone of each developer
60. ScrumBut – “Popular” modifications (20/33)
We don’t have a Scrum Master… not even a Product Owner (they are
M.I.A.)
61. ScrumBut – “Popular” modifications (21/33)
We argue all the time about who is responsible for doing what (roles
indefinition)
62. ScrumBut – “Popular” modifications (22/33)
The Product Owner doesn’t have time to write “decent” user stories
63. ScrumBut – “Popular” modifications (23/33)
We stopped doing important things (e.g. visit customers, supporting UAT)
because “that's not scrum”
65. ScrumBut – “Popular” modifications (25/33)
We have partially allocated team members (e.g. Developers)
66. ScrumBut – “Popular” modifications (26/33)
We have horizontal and not vertical teams so we can’t deliver working
software (increments) by the end of the sprint without depending on
all teams
Thanks to Jonathan Rasmusson
67. ScrumBut – “Popular” modifications (27/33)
We have horizontal and not vertical stories so we can’t deliver working
software (increments) by the end of the sprint
68. ScrumBut – “Popular” modifications (28/33)
We split user stories between development and testing
Development Testing
69. ScrumBut – “Popular” modifications (29/33)
Each story has an estimate for backend, frontend, integration and
testing
User Story
1
5
2
3
70. ScrumBut – “Popular” modifications (30/33)
We are just worried about the How and not the Why
72. ScrumBut – “Popular” modifications (32/33)
We don’t have any predictability whatsoever
73. ScrumBut – “Popular” modifications (33/33)
We focus on idle workers and not on idle work
74. For what it matters… don’t forget that your goal is to make (awesome)
software… and not to (just) do Scrum
Final remarks
There is nothing “wrong“ in modifying the Scrum framework… you just
shouldn’t (probably) call it Scrum! And (at least) make sure that you are
doing it for the right reasons!
In the end… It is not about effectiveness (ScrumBut) but about
efficiency (ScrumAnd)
Frameworks don’t fail… people do!
75. Scrum vs ScrumAnd vs ScrumBut:
which one are you doing?
Obrigado! Thank you! Gracias!