How to make your
daily stand-up more
Agile Marathon (Google campus, Tel-Aviv)
Developing software since the age of 13.
Agile development fan since 2004.
Scrum.org Professional Scrum Master (PSM III).
Development Manager and Agile coach at iMDsoft.
What is your process?
Let’s first make sure we all
speak the same language?
What is Scrum?
a. An Agile software development methodology.
b. A framework for developing complex products.
c. A software project management methodology for iterative
“Scrum is a framework for developing and sustaining complex
The Scrum Guide™
What is Kanban?
a. A project management methodology that originated from
b. A Lean product development process.
c. A Lean software development methodology.
d. A method for continuous improvement.
“Kanban is a method for defining, managing and improving
services that deliver knowledge work”
Essential Kanban Condensed
“Kanban is not a software development lifecycle methodology or
an approach to project management.”
“Kanban must not be thought of as a software development
lifecycle process or a project-management process. Kanban is a
change-management technique …”
A few words about Kanban
Thanks to Andy Carmichael and David J Anderson, Essential Kanban Condensed
Scrum + Kanban
Both Scrum and Kanban come from TPS.
In Kanban we start with what we do NOW and evolve
incrementally (so we can start with Scrum).
A good way to help Scrum improve is to bring in some
Kanban practices, things that Scrum had forgotten...
What can be really helpful?
Visualizing user stories (PBIs) value stream.
Make policies explicit.
Limit your WiP
Limiting WIP is often the first step to shift the emphasis
from starting to finishing.
By limiting the work-in-progress, we allow our teams to focus,
working at a sustainable pace with quality output.
Make all policies explicit
It is hard to make improvements if every team member has a
An example can be a DoD per column before moving work forward
(checklists, ground rules).
Reduce the PBI/story size
Larger items take more time to process
More queues (extra WiP)
Slice smaller vertical user stories (PBIs)
up to 3 days to get DONE!
More opportunities to inspect and adapt on a daily basis
What did I do yesterday?
What I’m doing today?
Is there anything blocking me?
Daily Standup with Kanban
1. “Walk the board” from right to left
2. Ask the probing questions to identify issues and
decide on next steps
Daily probing questions
1. Is any of our work hidden?
2. Are the next user stories blocked in some way (not refined, have impediments)?
3. Are there user stories that we can unblock?
4. Which user stories are moving slowly?
5. Are there any bottlenecks in the queues (WiP is exceeded)?
6. Is there a demand for backlog refinement (grooming)?
7. Are we clear about what's next?
8. Are we doing everything we can to minimize waiting time?
9. Are there any queues that we can clean-up (swarm)?
10. Are we respecting our WiP limits?
11. Is anyone assigned too many tasks?
12. Should we act on user stories owned by absent team members?
Thanks to Brendan Wovchko, Huge I/O