How to make your daily stand-up more engaging

Download How to make your daily stand-up more engaging

Post on 21-Apr-2017

121 views

Category:

Engineering

2 download

Embed Size (px)

TRANSCRIPT

<p>What is Scrum?</p> <p>How to make your daily stand-up more engaging?Boris KazarezMarch 2017Agile Marathon (Google campus, Tel-Aviv)</p> <p>About meBoris KazarezDeveloping 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.Married +2</p> <p>What is your process?ScrumKanbanXPMixWaterfall</p> <p>Daily Scrum vs Daily Standup</p> <p>How not to turn your Daily Standup into Zombie Daily Standup?</p> <p>Gamification?</p> <p>What is the purpose of your Daily Standup?</p> <p>Daily StandupIt is a planning meeting for the next 24 hours!</p> <p>What is the right question?</p> <p>How can you make the planning more effective?</p> <p>Focus on your (Sprint) Goal!</p> <p>How can we do that exactly?</p> <p>Lets first make sure we all speak the same language?</p> <p>What is Scrum?An Agile software development methodology.A framework for developing complex products.A software project management methodology for iterative software development.</p> <p>Scrum is a framework for developing and sustaining complex products.The Scrum Guide</p> <p>What is Kanban?A project management methodology that originated from Toyota.A Lean product development process.A Lean software development methodology.A method for continuous improvement.</p> <p>Kanban is a method for defining, managing and improving services that deliver knowledge workEssential Kanban Condensed</p> <p>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 -David Anderson</p> <p>A few words about Kanban</p> <p>Thanks to Andy Carmichael and David J Anderson, Essential Kanban Condensed</p> <p>Scrum + KanbanBoth 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...</p> <p>What can be really helpful?Limiting WiP.Visualizing user stories (PBIs) value stream.Make policies explicit.Manage flow.</p> <p>Visualize work (not tasks)</p> <p>Limit your WiPLimiting WIP is often the first step to shift the emphasis from starting to finishing. </p> <p>By limiting the work-in-progress, we allow our teams to focus,working at a sustainable pace with quality output.</p> <p>Limit your WiP</p> <p>(2)(3)(2)(2)(2)(5)</p> <p>Make all policies explicitIt is hard to make improvements if every team member has a different standard. </p> <p>An example can be a DoD per column before moving work forward (checklists, ground rules). </p> <p>Reduce the PBI/story sizeLarger items take more time to processMore queues (extra WiP)More variability</p> <p>Slice smaller vertical user stories (PBIs)up to 3 days to get DONE!</p> <p>More opportunities to inspect and adapt on a daily basis</p> <p>Lets mix all the ingredients</p> <p>Daily StandupWhat did I do yesterday?What Im doing today?Is there anything blocking me?</p> <p>Daily Standup with KanbanWalk the board from right to leftAsk the probing questions to identify issues and decide on next steps</p> <p>Daily probing questionsIs any of our work hidden?Are the next user stories blocked in some way (not refined, have impediments)?Are there user stories that we can unblock?Which user stories are moving slowly?Are there any bottlenecks in the queues (WiP is exceeded)?Is there a demand for backlog refinement (grooming)?Are we clear about what's next?Are we doing everything we can to minimize waiting time?Are there any queues that we can clean-up (swarm)?Are we respecting our WiP limits?Is anyone assigned too many tasks?Should we act on user stories owned by absent team members?</p> <p>Thanks to Brendan Wovchko, Huge I/O</p> <p>29</p> <p>1. Is any of our work hidden?</p> <p>2. Are the next user stories blocked in some way (not refined, have impediments)?</p> <p>3. Are there user stories that we can unblock?</p> <p>4. Which user stories are moving slowly?</p> <p>5. Are there any bottlenecks in the queues (WiP is exceeded)?</p> <p>6. Is there a demand for backlog refinement (grooming)?</p> <p>7. Are we clear about what's next?</p> <p>8. Are we doing everything we can to minimize waiting time?</p> <p>9. Are there any queues that we can clean-up (swarm)?</p> <p>10. Are we respecting our WiP limits?</p> <p>11. Is anyone assigned too many tasks?</p> <p>12. Should we act on user stories owned by absent team members?</p> <p>The gameOne team member observes the daily stand-up from a side.If s/he is able to identify a problem that others didnt notice s/he wins!</p> <p>Thanks to Brendan Wovchko, Huge I/O</p> <p>Wrapping upFocus on how the team can move the work forward by using probing questionsDiscuss daily how to achieve the Sprint goalTurn it into an effective planning meeting</p> <p>And use a physical board </p> <p>Questions?</p> <p>https://www.linkedin.com/in/boriskazarez/</p>