Practices of an Agile Team

Transcript

1. Practices of an Agile Team Eiwa System Management, Inc. Fumihiko

   Kinoshita

2. About Me ✓Name: Fumihiko Kinoshita ✓Mail: fkinos@gmail.com ✓Blog: http://fkino.net ✓Technical

   Lead ✓Practitioner of Agile Development ✓XP Japan Users Group Staff ✓I translated “Practices of an Agile Developer” into Japanese. ✓I like XP.

3. Practices of an Agile Developer

4. Japanese Edition

5. The Art of Agile Development

6. My Team’s Practices

7. Agenda ✓Agile Retrospectives ✓Agile Planning ✓Energized Work ✓Agile Team

8. Weekly Time Box

9. Iteration Planning Retrospective Development

10. Mon Tue Wed Thu Fri Sat Sun 1 Development Retro-

    spectives Deve lopm ent Off 2 Iteration Planning 3 Slack

11. Agile Retrospectives

12. Mon Tue Wed Thu Fri Sat Sun 1 Development Retro-

    spectives Deve lopm ent Off 2 Iteration Planning 3 Slack

13. Retrospectives ✓Once a week ✓KPT ✓Retrospective Driven ✓Learning team. ✓Continuous

    Kaizen.

14. Retrospectives ✓KPT (Keep/Problem/Try) Keep Problem Try

15. Retrospectives ✓First Retrospective in the project ✓“Try” area is large

    Keep Problem Try

16. Retrospectives ✓Final Retrospective at the end of the project ✓Timeline

    Nov. Dec. Jan.

17. Retrospectives ✓Graduation ceremony ✓Emotions Keep Problem Try Happy Sad

18. Estimate Retrospectives ✓The data is gathered and analyzed

19. Positive Strokes ✓Paying compliments to team member

20. Feedback

21. Iteration Planning Retrospective Development Feedback

22. Lean Software Development

23. Lean Principles ✓Eliminate waste ✓Amplify learning ✓Decide as late as

    possible ✓Deliver as fast as possible ✓Empower the team ✓Build integrity in ✓See the whole

24. Lean Principles ✓Eliminate waste ✓Amplify learning ✓Decide as late as

    possible ✓Deliver as fast as possible ✓Empower the team ✓Build integrity in ✓See the whole

25. Agile Retrospectives

26. Post-Iteration Party ✓Drinking party ✓Every 2 weeks ✓You’ll need some

    cash!

27. Sake ✓Kagetora

28. Sake ✓Hangover ✓Serious reflection Drank too much

29. Agile Planning

30. Mon Tue Wed Thu Fri Sat Sun 1 Development Retro-

    spectives Deve lopm ent Off 2 Iteration Planning 3 Slack

31. Iteration Planning

32. Iteration Planning ✓One week is 32 hours ✓The remaining 8

    hours are “Retrospective”, “Iteration Planning” and “Slack”. ✓Various Kaizen is done in remaining time.

33. Estimating

34. Extreme Programming Installed

35. Programmer Rights ✓The programmer has the right to estimate work

    and have those estimates respected by the rest of the team. ✓The programmer has the right to honestly report progress. ✓The programmer has the right to produce high- quality work at all times. ✓The programmer has the right to know what is most important to work on next. ✓The programmer has the right to ask business- oriented questions whenever they arise.

36. Programmer Rights ✓The programmer has the right to estimate work

    and have those estimates respected by the rest of the team. ✓The programmer has the right to honestly report progress. ✓The programmer has the right to produce high- quality work at all times. ✓The programmer has the right to know what is most important to work on next. ✓The programmer has the right to ask business- oriented questions whenever they arise.

37. Taboo Word

38. “We’ll Try” The saddest two words a programmer can ever

    say.

39. Lister’s Law People under time pressure don't think faster.

40. Estimate and Promise We cannot promise the precise outcome.

41. Estimate and Promise We can ✓estimate what we can do.

    ✓promise to do our best. ✓promise to tell the truth about what has happened.

42. Iteration Planning Adjust ✓the assignment of team members. ✓the scope

    of the work. ✓the limits.

43. This is my job as a leader.

44. But if we don't finish the work we've committed to...

45. Kaiouken

46. Iteration Planning ✓Sign up for the tasks that you want

    to do.

47. Iteration Planning If more than one person signs up for

    the same task ...

48. Darts

49. Task Kanban

50. Task Kanban ✓Football Pitch

51. Task Kanban ✓Time.now

52. Task Kanban ✓School Timetable

53. Toyota Kanban System ✓One-piece-At-a-Time Production ✓Waiting in one line ✓Standardization

    and multi-skill ✓Start as late as possible ✓Total amount management

54. Toyota Kanban System ✓One-piece-At-a-Time Production ✓Waiting for in line ✓Standardization

    and multi-skill ✓Start as late as possible ✓Total amount management

55. Energized Work

56. Energized Work ✓40 hours a week ✓Though I do not

    work overtime, I want overtime pay!

57. Overtime Tickets

58. Overtime Tickets ✓Assume 30 hours of overtime deemed ✓1 ticket

    = 30 minutes ✓For every 30 minutes of overtime you work, you put a ticket into the box. ✓When working overtime is unavoidable, a leader can distribute additional tickets. ✓Remaining tickets = Overtime pay

59. We changed office regulations without permission.

60. Agile Team

61. Frequent meeting with the customer ✓Every one or two weeks.

    ✓“Problem vs. us” ✓We tell the truth about what has happened.

62. Honesty pays — BUSHIDO

63. The most delightful words I have heard from a customer

    ”Because I trust you.”

64. Trust

65. Slack

66. Parent’s Rule Always give trust slightly in advance of demonstrated

    trustworthiness.

67. Trust Team Trust Trust Trust Trust Member Customer Leader

68. What It Feels Like

69. ✓You seem to take pleasure in work. ✓Your team also

    includes the customer. ✓I want to do the work once again with this team.

70. Thank you for your attention.

71. Any Questions?