Tangible Bug Tracking Using LEGO Bricks in Agile2008, Toronto

Slide 1: Tangible Bug Tracking Using LEGO Bricks Change Vision, Inc. Takeshi Kakeda AgileConference2008 8/5 Sheraton A, LC takeshi.kakeda@change-vision.com Seeing is understanding.

Slide 2: About Me ● My name is Takeshi Kakeda ● Certified Scrum Master Agile Community ● ● Participation in Japan since 2001. Book ● ● One of the translators ● “Agile Software Development with SCRUM” ● One of the reviewers ● “Agile Estimating and Planning” ● Japanese original Books ● Unit Testing, Eclipse, FreeBSD, Linux, etc Seeing is understanding.

Slide 3: About Me  Change Vision, Inc.  I'm developing “TRICHORD”. – Agile Team Kanban Board http://trichord.change-vision.com Seeing is understanding.

Slide 4: I'm from... Tokyo, Japan Here we are in Toronto 4 Seeing is understanding.

Slide 5: Agile Communities in Japan  It'll be talked about Agile context in Japan – 14:00 – 15:30 – Kenora, 2 – Presenter is Tsutom Yasui.  Please check it out! Seeing is understanding.

Slide 6: Japanese Open Space  Session calender about Japanese Presenter  We're going to have a party tomorrow. Please visit our space today. Seeing is understanding.

Slide 7: Table of Contents  What's BUG-LEGO?  History of BUG-LEGO  Three Keywords  BUG-LEGO on software  Conclusion Seeing is understanding.

Slide 8: What's BUG-LEGO Seeing is understanding.

Slide 9: LEGO Bricks? LEGO Bricks was made in Denmark in 1949. LEGO Duplo A baby may LEGO eat a small piece of LEGO! Seeing is understanding.

Slide 10: LEGO duplo with my children Seeing is understanding.

Slide 11: What's BUG-LEGO？ The structure built such as a bug... Seeing is understanding.

Slide 12: What's BUG-LEGO？ The tangible bug-tracking system with using tiny structure built of lego bricks Seeing is understanding.

Slide 13: History of BUG-LEGO Seeing is understanding.

Slide 14: Before BUG-LEGO Workflow Create a ticket Check BTS and Catch a bug Create task Close the ticket Fix it! Seeing is understanding.

Slide 15: Motivator Let's think about how we can see a stock of bugs. We got an idea of BUG-LEGO in week “FURIKAERI”. “ That's LEGO Bricks!” Seeing is understanding.

Slide 16: “FURIKAERI” Stop and Turn around to go forward Same meaning to retrospective, reflection meeting http://www.tnm.jp/gallery/search/images/max/C0032483.jpg Seeing is understanding.

Slide 17: Initial version There were no ticket id. Seeing is understanding.

Slide 18: First improvement Tiny structure built by lego Ticket id on a sticky note Summary on a sticky note Seeing is understanding.

Slide 19: After BUG-LEGO Workflow Build Create a bug-lego ticket Catch a bug Check Close the ticket and Create task Destroy it! Fix it! Seeing is understanding.

Slide 20: Second improvements Dependency Priority Difficulty Severity Seeing is understanding.

Slide 21: Priority Low Middle High Seeing is understanding.

Slide 22: Difficulty or Severity Representation of complexity of structure as difficulty or severity of software bug Simple Complex Easy/Trivial Difficult/Critical Seeing is understanding.

Slide 23: Dependency #138 #132 Seeing is understanding.

Slide 24: Final version Seeing is understanding.

Slide 25: Three Keywords of BUG-LEGO Consciousness Change of Mindset Constraint Seeing is understanding.

Slide 26: Consciousness  Everyone is conscious of the amount of software bug whoever come in the room  By the sounds Seeing is understanding.

Slide 27: Change of Mindset  Changing mindset against bug – Negative -> Positive  Pleasure in – Construction – Destruction Seeing is understanding.

Slide 28: Constraint  Physical constraint became a driver of reducing bugs 15inch x 15inch No constraint on BTS Seeing is understanding.

Slide 29: Comparison of before and after Before After Attitude to bugs Negative Positive The stock of bug Increase Decrease The number of people Developer who knows about bugs Developer Sales staff Manager Seeing is understanding.

Slide 30: Suitable for  Early stages  Collocated  With stakeholders  Lean Seeing is understanding.

Slide 31: Unsuitable for  There are already many bugs  Distributed  Only developer Seeing is understanding.

Slide 32: Next Idea Using LEGO Bricks Building lego as a tangible Building lego goal for delivered story Progress Indicator by giant lego Seeing is understanding.

Slide 33: BUG-LEGO on Software Let me show you This is developed by Akiya Mizukoshi (Change Vision, Inc) Seeing is understanding.

Slide 34: Conclusion  LEGO bricks make software bugs tangible, noticeable,and fun. – We tried BUG-LEGO  “FURIKAERI” is great activity. Seeing is understanding.

Slide 35: Question (1)  Q: What is merit on comparison with kanban on a wall?  A: It looks like kanban functionally. I'd like to use LEGO bricks as kanban :) Seeing is understanding.

Slide 36: Question(2)  Q:Did developers stop working because they enjoyed building LEGO bricks?  A: No, they don't ;) Seeing is understanding.

Slide 37: Thank you so much! Seeing is understanding.