How To Use Scrum

4,126 views

Published on

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

No Downloads
Views
Total views
4,126
On SlideShare
0
From Embeds
0
Number of Embeds
39
Actions
Shares
0
Downloads
89
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

How To Use Scrum

  1. 1. H OW TO U SE S CRUM SUMMARY & PRACTICE
  2. 2. PEOPLE & EFFICIENCY & PRODUCTION <ul><ul><li>  People is the most important part for Scrum </li></ul></ul><ul><ul><li>  If the team does not understand efficiency,investors can not save time&money. </li></ul></ul><ul><ul><li>  Production is much more important than everything. </li></ul></ul>
  3. 3. PRIMARY NEED FOR SCRUM <ul><ul><li>Sprint </li></ul></ul><ul><ul><li>Backlog </li></ul></ul><ul><ul><li>Scrum Master </li></ul></ul><ul><ul><li>Quality Process </li></ul></ul><ul><ul><li>Production Manager </li></ul></ul><ul><ul><li>Change for Efficiency </li></ul></ul><ul><ul><li>Tracking </li></ul></ul>
  4. 4. IMPROVEMENT FOR SCRUM FRAMEWORK <ul><ul><li>  Different scopes of team </li></ul></ul><ul><ul><li>  Change sprint length </li></ul></ul><ul><ul><li>  Different practices </li></ul></ul><ul><li>  </li></ul><ul><li>  </li></ul><ul><li>Remember, scrum is a framework, the aim is efficiency. </li></ul>
  5. 5. START FROM BACKLOG <ul><ul><li>ID </li></ul></ul><ul><ul><li>NAME </li></ul></ul><ul><ul><li>IMPORTANCE </li></ul></ul><ul><ul><li>INITIAL ESTIMATE </li></ul></ul><ul><ul><li>HOW TO DEMO </li></ul></ul><ul><ul><li>NOTES </li></ul></ul>
  6. 6. EXTRA FOR BACKLOG <ul><ul><li>  CATEGORY </li></ul></ul><ul><ul><li>  COMPONENTS </li></ul></ul><ul><ul><li>  REQUESTOR </li></ul></ul><ul><li>  </li></ul><ul><li>  </li></ul><ul><li>Remember, Simple is the best! </li></ul>
  7. 7.   SPRINT PLAN <ul><li>Before: </li></ul><ul><ul><li>Development Environment Initial </li></ul></ul><ul><ul><li>Backlogs Initial </li></ul></ul><ul><ul><li>Estimate Initial </li></ul></ul><ul><ul><li>Team Initial </li></ul></ul><ul><li>Then: </li></ul><ul><ul><li>Sprint Meeting per Sprint </li></ul></ul><ul><li>  </li></ul><ul><li>Responsibility: </li></ul><ul><ul><li>Backlog : Production Manager </li></ul></ul><ul><ul><li>Sprint: Team </li></ul></ul><ul><ul><li>Culture Way: Scrum Master </li></ul></ul>
  8. 8. ARTIFACT OF SPRINT MEETING <ul><ul><li>sprint backlog </li></ul></ul><ul><ul><li>sprint time line </li></ul></ul><ul><ul><li>sprint team </li></ul></ul><ul><ul><li>demo time line </li></ul></ul>
  9. 9. S PRINT MEETING DEMO <ul><li>from 13:00 to 17:00  ten minutes break per hour. </li></ul><ul><ul><li>  13:00 – 13:30: </li></ul></ul><ul><li>production manager: sprint goal, backlog introduction </li></ul><ul><li>team:backlog estimation, split backlog </li></ul><ul><ul><li>13:30 – 15:00: </li></ul></ul><ul><li>production manager: refactor backlog, review sprint plan,show demo part. </li></ul><ul><li>team:learning backlog </li></ul><ul><ul><li>15:00 – 16:00: </li></ul></ul><ul><li>team:choose sprint backlogs </li></ul><ul><li>production manager: review sprint backlogs </li></ul><ul><ul><li>16:00 – 17:00: </li></ul></ul><ul><li>team:split backlogs into tasks. </li></ul>
  10. 10. SPRINT GOAL <ul><ul><li>The most important: tell other people the content of this sprint, then all people will understand your job. </li></ul></ul><ul><ul><li>Share your goal to all people. </li></ul></ul>
  11. 11. H OW TO SELECT YOUR BACKLOGS <ul><li>  </li></ul>
  12. 12. S PLIT B ACKLOGS INTO TASKS <ul><ul><li>Team's job </li></ul></ul><ul><ul><li>Does this need to review? </li></ul></ul><ul><ul><li>Who check out the task, who check in the source. </li></ul></ul><ul><ul><li>Who is QA? </li></ul></ul>
  13. 13. WHAT IS DONE ? <ul><ul><li>bugs have been fixed </li></ul></ul><ul><ul><li>demo should work well </li></ul></ul><ul><ul><li>give team a show time </li></ul></ul><ul><ul><li>production manager says:'fine'! </li></ul></ul>
  14. 14. D EFECT /B US ? <ul><ul><li>The serious defects/bugs need to be checked as tasks. </li></ul></ul>
  15. 15. SHARE YOUR IDEAS AND JOBS <ul><ul><li>Email </li></ul></ul><ul><ul><li>Tracking System </li></ul></ul><ul><ul><li>Sprint Meeting </li></ul></ul><ul><ul><li>Demo Show </li></ul></ul>
  16. 16. D O WE NEED DAILY MEETING ? <ul><ul><li>Internal development: Yes </li></ul></ul><ul><ul><li>Distributed development:No, but need wiki/email report and talking for exchange. </li></ul></ul>
  17. 17. S UMMARY &F EEDBACK <ul><ul><li>Feedback every sprint meeting. </li></ul></ul><ul><ul><li>Summary your experience every sprint. </li></ul></ul><ul><ul><li>It's important, scrum need to be refactor everyday. </li></ul></ul>
  18. 18. S OME TIPS : SOURCE CONTROL <ul><ul><li>Tag for every sprint  </li></ul></ul><ul><ul><li>Do not break trunk </li></ul></ul><ul><ul><li>If it is not necessary, do not use branch. </li></ul></ul><ul><ul><li>Use Hudson and testing environment everyday. </li></ul></ul>
  19. 19. T HANKS ! HTTP :// WWW . HAULYNJASON . NET /

×