Scrum

1,053 views

Published on

Slides about scrum.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,053
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • 1. 减少浪费 Delay with software development process Unnecessary functionality Unclear requirements 2. 提高学习能力 3. 慎重决策 4. 快速实现 5. 强调团队地位 find good people and let them do their own job 6. 保证软件质量 7. 了解全局 Lean thinking has to be understood well by all members of a project, before implementing in a concrete, real-life situation. “Think big, act small, fail fast; learn rapidly”
  • Product Owner: * Prepare backlogs for team, prioritize them * Review product delivered by team Scrum Master: * Keep scrum process going * Isolate external corrupts from team * Also as a scrum team member Team * 5-9 members with cross-functionality: analysis, design, implements, testing, documenting Manager * Human resource manager Stakeholders * Customers and vendors
  • Scrum

    1. 1. Practical Scrum 2011.06.17 [email_address]
    2. 2. Our Project: ByD <ul><li>Software as a Service (SaaS)
    3. 3. Distributed development
    4. 4. ~1000 staff </li></ul>
    5. 6. Problems <ul><li>Difficult to coordinate
    6. 7. Difficult to manage requirements </li></ul>
    7. 8. v2.0 DELAYED
    8. 9. Lean with Scrum <ul><li>Lean software development
    9. 10. Scrum methodology
    10. 11. XP practice </li></ul>Lean Scrum XP
    11. 12. Lean <ul><li>Adapted from the Toyota
    12. 13. Lean Software Development
    13. 14. Lean principles </li></ul>http://en.wikipedia.org/wiki/Lean_software_development
    14. 16. Lean principles <ul><li>Eliminate waste
    15. 17. Amplify learning
    16. 18. Decide as late as possible
    17. 19. Deliver as fast as possible
    18. 20. Empower the team
    19. 21. Build integrity in
    20. 22. See the whole </li></ul>
    21. 23. Scrum methodology <ul><li>1986, Japan
    22. 24. 1995, First public presentation
    23. 25. 2001, Agile Software Development with Scrum </li></ul>
    24. 27. XP Practices <ul><li>Kent Beck
    25. 28. Pair Programming
    26. 29. Unit test
    27. 30. TDD
    28. 31. Refactoring
    29. 32. Code review </li></ul>
    30. 33. 2.6, 3.0 delivered on time
    31. 34. Scrum Concepts <ul><li>Characteristics
    32. 35. Roles </li><ul><li>Pig-Role
    33. 36. Chicken-Role </li></ul><li>Meetings
    34. 37. Artifacts </li><ul><li>Backlogs
    35. 38. Burn-down chart </li></ul></ul>
    36. 39. Iterations <ul><li>Releases (10+1 sprints)
    37. 40. Sprints (10 workdays)
    38. 41. Workdays (8 hours) </li></ul>
    39. 42. Paralleled release schedule <ul><li>Solution team: 3.5
    40. 43. Dev team: 3.0
    41. 44. Testing&Operation: 2.6 </li></ul>
    42. 45. Backlogs <ul><li>Product backlogs
    43. 46. Release backlogs
    44. 47. Sprint backlogs
    45. 48. Tasks </li></ul>
    46. 50. Characters <ul><li>Pig Roles </li><ul><li>Product Owner
    47. 51. Scrum Master
    48. 52. Team </li></ul></ul><ul><li>Chicken Roles </li></ul><ul><ul><li>Manager
    49. 53. Stakeholders </li></ul></ul>
    50. 54. Product Owner
    51. 55. Scrum Master
    52. 56. Scrum Team
    53. 57. Manager
    54. 58. Stakeholders
    55. 59. Sprint <ul><li>Resource estimation
    56. 60. Meetings
    57. 61. Development </li></ul>
    58. 62. Resource Estimation <ul><li>30% development
    59. 63. 30% testing
    60. 64. 20% maintenance
    61. 65. 20% buffer </li></ul>8*10*(0.3+0.3) = 48
    62. 66. Meetings <ul><li>Planning Meeting (Thu 16:00-17:00)
    63. 67. Breakdown Meeting (Thu 17:00-18:00)
    64. 68. Refine Meeting (Wed 13:00-14:00)
    65. 69. Review Meeting (Wed 16:00-18:00)
    66. 70. Retrospective (Thu 10:15-11:00)
    67. 71. Daily Scrum (10:00-10:15) </li></ul>
    68. 72. Daily Scrum <ul><li>15-minute stand meeting
    69. 73. Update status
    70. 74. Pick new tasks
    71. 75. JIRA GreenHopper </li></ul>
    72. 76. Task Tag Sprint n Component : Task owner 5 1 2 3 4 5 1 2 8 6 2 0
    73. 77. White board TODO DOING DONE BLOCKED DECOMMIT
    74. 78. Burndown Chart
    75. 79. Implementing a Feature <ul><li>Feature backlog </li><ul><li>Feature description
    76. 80. Effort Estimation
    77. 81. Contact information
    78. 82. Done Criteria </li></ul><li>Planning </li><ul><li>Sprint n-2: feature spec
    79. 83. Sprint n-1: design
    80. 84. Sprint n: feature impl / test / doc (part 1)
    81. 85. Sprint n+1: feature impl / test / doc (part 2) </li></ul></ul>
    82. 86. Delivery usable software <ul><li>Demo
    83. 87. Test automation / Daily regression / CI
    84. 88. Document ready
    85. 89. Confirmed with stakeholders
    86. 90. Leftovers </li></ul>
    87. 91. Thank you !

    ×