Scrum is not #perfect

1. Scrum is not #perfect
For software development
Mateusz Żeromski

2. Time
Value
In theory, the Scrum allows having a huge
impact of value in a very short time in the
beginning. It’s related to the first version,
MVP - etc. But later on - adding value it’s
more complicated.
Software development is a good example
- it’s easy to start, and hard to extend. So
this is a case to show that scrum rules are
not always perfect.

3. Time
Value
At the begin, the Scrum ceremony can be a
blocker. You need to plan the Sprint, do a Review,
Retro. In startups it’s too complicated, you have to
fight with time, create and extend MVP every day,
inspect and adapt every hour.
Daily can be not so effective, communication
should be faster.
So in this stage - scrum is not perfect, please
check “Lean Startup”.

4. Time
Value
When the product contains a lot of features -
extend it is very complicated. The value grows not
so fast, and it needs more effort. So daily Scrum
ceremony can be to often, sometimes some
technical job required a few days to develop it.
Review - it’s boring, almost nothing added. Retro
does not bring any improvement.
It’s time to switch to Kanban board. The Scrum
ceremony is wasting time.

5. Time
Value
IMO this is a good time for Scrum rules. Let’s start from anarchy, then
switch to Scrum to fix problems, improve the team flow. Then switch to the
kanban rules without timeboxed Sprint, and do ScrumBut.

6. What is a key? When use the Scrum?
Knowledge Teach team about the Scrum Rules. Show benefits and costs. Ask
for the team experience
Ask Ask team members about their opinion, work closely. Allow
making anarchy, support to bring the biggest possible value.
Introduce When first problem will occur - introduce some scrum
rules to daily work. Step by step - make transformation
Go away Sometimes - you have to go away, and let team work
on their rules.