Who's afraid of the Big Bad Wall


Published on

How do we create project level visualization in software and how to we use Gemba walks to gather information, understand what's going on and manage proactively.

Published in: Business, Sports, Technology
1 Comment
  • Good work. I think it would be good if you have a separate presentation focusing on visualization; including what data to collect, how, and some typical way of looking at it etc.
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Who's afraid of the Big Bad Wall

  1. 1. 現地現物<br />目で見る管理<br />Who’s afraid of the big bad wall<br />Visual management and gemba walks<br />Inbar Oren<br />
  2. 2. About Me<br /><ul><li>Work at AgileSparks
  3. 3. Over 15 years experience in R&D organizations ranging from product development and project management to product management.
  4. 4. Married with twins
  5. 5. MA in Buddhism and East Asian Cultures
  6. 6. Second degree black belt in Iaido and Jodo
  7. 7. Find me on:
  8. 8. inbar@agilesparks.com
  9. 9. http://www.leansamurai.com
  10. 10. @inbaro</li></li></ul><li>The story of a manager<br />3<br />How’s my Scrum Team Doing?<br />
  11. 11. What’s going on with My Scrum Team?<br />4<br />US<br />To Do<br />WIP<br />Done<br />?<br />
  12. 12. Let’s look at the burn down<br />5<br />I’ll wait for the daily<br />
  13. 13. the daily<br />6<br />Yesterday I worked on Task 1, I will finish it today no impediments<br />Since last time I worked on the production issues. I’m still on them and have no problems.<br />?<br />I’m just updating for Phil, he is at home with his child and hopes to come back tomorrow.<br />
  14. 14. the daily<br />7<br />I’m sorry but we have a joke on Chickens and Pigs in Scrum so we don’t answer questions<br />How is Phil doing on testing the subsystem?<br />
  15. 15. Joke pomodoro<br />8<br />Never mind I’ll go see the Kanabn team<br />
  16. 16. What’s going on with my Kanban Team?<br />9<br />Backlog<br />(3)<br />Dev<br />(5)<br />Test<br />(5)<br />Done<br />I’ll wait for the daily<br />
  17. 17. the daily<br />10<br />When’s the daily?<br />?<br />Dude, didn’t you see the board? We’re, Like, totally at flow. We only meet when there are bottlenecks.<br />
  18. 18. How is my project doing?<br />???<br />11<br />
  19. 19. The invisibility in the visibility<br />12<br />
  20. 20. Team Boards<br />13<br />US<br />To Do<br />WIP<br />Done<br />
  21. 21. Project Boards<br />14<br />
  22. 22. A good visual board…<br />Tells a story<br />Always visible<br />Living<br />Keeps it simple<br />Self explanatory<br />15<br />
  23. 23. Gemba<br />“the place – <br /> any place in any organization – <br /> where humans create value” Jim Womack<br />16<br />現場<br />
  24. 24. Gemba Walks<br />17<br />Go See<br />Ask Why<br />Show Respect<br />
  25. 25. Gemba walk in Software development<br />18<br />Where to Go?<br />What to See?<br />With Whom to Talk?<br />What to Ask?<br />How to Show Respect?<br />
  26. 26. Where to go?<br />19<br />The Real Gemba<br />Developers <br />Code<br />Testers <br />Test<br />Business Analysts<br />Analyze<br />Gemba Walk<br />
  27. 27. Physical and Electronic walls<br />“"Take information out of the box known as the computer and make it visible and understandable to users" Pascal Dennis – The Remedy<br />20<br />
  28. 28. What to See?<br />21<br />Potential Problems<br />Immediate Problems<br />Kaizen Opportunities<br />
  29. 29. With whom to talk?<br />22<br />The Actual Team<br />
  30. 30. What to Ask?<br />23<br />Stop and Fix<br />How are you effected <br />by upstream?<br />What are the <br />current problems?<br />What could come up <br />in the next few days?<br />Are youworking at <br />a sustainable pace?<br />How are you<br />Improving?<br />
  31. 31. How to show respect?<br />24<br />Ask Questions<br />Letting Go<br />
  32. 32. A sample tour<br />25<br />Team 1<br />Product Owner<br />Project Manager<br />Team 2<br />
  33. 33. Team 1<br />26<br />How is the sprint going?<br />Just fine<br />Will you meet your goals?<br />Yes we will!<br />Why is the burndown flat?<br />We haven’t finished tasks, but we just moved to the next item<br />
  34. 34. Team 1<br />27<br />Why so many items in progress?<br />We have some impediments<br />Why?<br />We’re waiting on Team 2<br />Why?<br />They’re just slow<br />Now wait a minute!<br />Let’s visit your board team 2<br />
  35. 35. Team 2<br />28<br />Are you behind?<br />Not at all!<br />So why does team 1, feel stuck?<br />Their tasks hasn’t started yet<br />Why not?<br />We’re just working by priority! <br />
  36. 36. Project Board<br />29<br />We’re behind on discovery?<br />I was abroad for two weeks<br />And we have misaligned expectations between Team 1 and Team 2. Our board doesn’t look good. Let’s discuss what we can do.<br />
  37. 37. Project board<br />30<br />GA<br />Kickoff<br />1/2/11<br />31/7/11<br />17/3/11<br />Discovery<br />Development<br />Y<br />R<br />G<br />Ready Stories<br />Stories<br />Epics<br />R<br />Readiness<br />Quality<br />Budget<br />Y<br />Y<br />R<br />
  38. 38. Project board<br />31<br />Impediment Board<br />Done<br />New<br />Done<br />Kaizen board<br />New<br />New<br />New<br />New<br />
  39. 39. Program board<br />32<br />Impediment Board<br />
  40. 40. VP R&D board<br />33<br />Technical Debt Level<br />Y<br />Y<br />Y<br />G<br />R<br />R<br />Y<br />G<br />R<br />G<br />G<br />G<br />R<br />Y<br />Y<br />R<br />G<br />G<br />Y<br />G<br />G<br />Y<br />R<br />G<br />R<br />R<br />R<br />R<br />G<br />Y<br />Y<br />Impediment Board<br />Kaizen board<br />
  41. 41. QA Leader Board<br />34<br />
  42. 42. Who else should have a board?<br />35<br />Everybody<br />CEO<br />Account Managers<br />Support<br />Individuals<br />
  43. 43. What to do when you leave this room?<br />36<br />Visualize<br />Get out of your seat <br />Ask Questions<br />
  44. 44. Questions?<br />37<br />Feedback<br /><ul><li>inbar@agilesparks.com
  45. 45. http://www.leansamurai.com
  46. 46. http://www.linkedin.com/in/inbaroren</li></li></ul><li>38<br />Thank<br />You<br />
  47. 47. Images<br />Front Page- http://www.flickr.com/photos/83331954@N00/2742235520<br />Joke pomodoro - http://www.flickr.com/photos/xverges/<br />Where to go - http://www.flickr.com/photos/zoovroo/3379891088/<br />What to see - http://www.flickr.com/photos/zigazou76/3702501888/<br />http://www.flickr.com/photos/andyarthur/5615755093/<br />http://www.flickr.com/photos/zivkovic/5281176320/<br />With whom to talk - http://www.flickr.com/photos/usfsregion5/4582146723/<br />How to show respect - http://www.flickr.com/photos/jurvetson/1571925233/<br />http://www.flickr.com/photos/asktheclimatequestion/4535664653<br />A sample tour - http://www.flickr.com/photos/wolfsavard/3149182570/<br />What to do when you leave - http://www.flickr.com/photos/helloturkeytoe/2706162709<br />39<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.