Your SlideShare is downloading. ×
0
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Scrum
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Scrum

886

Published on

Slides about scrum.

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
886
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
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
  • Transcript

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

    ×