Scrum Review

248 views
161 views

Published on

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

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

No notes for slide

Scrum Review

  1. 1. Lennon Manchester @leManchester lennon.manchester@staunchrobots.com
  2. 2. Scrum
  3. 3. Agile Methodology
  4. 4. Agile Manifesto
  5. 5. Individuals and interactions over processes and tools Agile Manifesto
  6. 6. Individuals and interactions over processes and tools Working software over comprehensive documentation Agile Manifesto
  7. 7. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Agile Manifesto
  8. 8. Individuals and interactions over processes and tools Responding to change over following a plan Working software over comprehensive documentation Customer collaboration over contract negotiation Agile Manifesto
  9. 9. 2001 A Space Odyssey
  10. 10. Principles
  11. 11. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  12. 12. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
  13. 13. The best architectures, requirements and designs emerge from self-organizing teams.
  14. 14. multidisciplinary self-organizing trust team work Agile value continues team collaboration commitment frequently communication sustainable effective
  15. 15. Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowler James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick Robert C. Martin Steve Mellor Ken Schwaber Jeff Sutherland Dave Thomas
  16. 16. Time boxes Planning Review Retrospective Daily Sprint
  17. 17. Sprint - Defined cycle of work 2 - 4 weeks?
  18. 18. Review
  19. 19. Review - review meeting 2.5% of the total sprint
  20. 20. Review(2 hr) - review meeting 2.5% of the total sprint
  21. 21. Review(2 hr) - review meeting 2.5% of the total sprint - scrum team + client
  22. 22. Review(2 hr) - review meeting 2.5% of the total sprint - scrum team + client - review what is delivered
  23. 23. Daily
  24. 24. Daily15 min
  25. 25. Daily15 min - What I did from the last daily until now
  26. 26. Daily15 min - What I did from the last daily until now - What I'm going to do until the next
  27. 27. Daily15 min - What I did from the last daily until now - What I'm going to do until the next - Blockers
  28. 28. Daily - Same time always 15 min - What I did from the last daily until now - What I'm going to do until the next - Blockers
  29. 29. Retrospective
  30. 30. Retrospective 3.75% - 3hr
  31. 31. Retrospective - Positive items to keep 3.75% - 3hr
  32. 32. Retrospective - Positive items to keep - Negative items to improve 3.75% - 3hr
  33. 33. Retrospective - Do not take it personal  - Positive items to keep - Negative items to improve 3.75% - 3hr
  34. 34. Retrospective - Do not take it personal  - Positive items to keep - Negative items to improve 3.75% - 3hr
  35. 35. Planning
  36. 36. Planning 5% of the Sprint
  37. 37. Planning 5% of the Sprint 4 hr
  38. 38. Planning I
  39. 39. Planning I - What is going to be done?
  40. 40. Planning I - What is going to be done? - PO what is explain the priority story
  41. 41. Planning I - What is going to be done? - PO what is explain the priority story - Explain the business
  42. 42. Planning I - Dev’s estimate that story - What is going to be done? - PO what is explain the priority story - Explain the business
  43. 43. Planning I - Dev’s estimate that story - What is going to be done? - PO what is explain the priority story - Explain the business
  44. 44. Planning II
  45. 45. Planning II - How is it going to be done?
  46. 46. Planning II - How is it going to be done? - Break stories to tasks of 8 hrs
  47. 47. Planning II - How is it going to be done? - Break stories to tasks of 8 hrs (max)
  48. 48. Planning II - How is it going to be done? - Break stories to tasks of 8 hrs (max) - That’s stories goes to the Kanban board
  49. 49. Planning II - Define the meta - How is it going to be done? - Break stories to tasks of 8 hrs (max) - That’s stories goes to the Kanban board
  50. 50. To be, or not to be, that is the question: Whether ler in the mind to The S end them: to die, to nd sleep, to say we end rows of outr Or a Sea to say we endThe No Tis a consummationActors drea ui
  51. 51. Scrum Team
  52. 52. Scrum Team - auto organization - flexibility  - focus - quality  - be on time on the meetings
  53. 53. - keep the backlog updated
  54. 54. - keep the backlog updated - breath the product
  55. 55. - keep the backlog updated - breath the product - control expectations
  56. 56. - keep the backlog updated - breath the product - control expectations - defend the interest of the product
  57. 57. - keep the backlog updated - breath the product - control expectations - defend the interest of the product - define sprint meta
  58. 58. - answer the business questions - keep the backlog updated - breath the product - control expectations - defend the interest of the product - define sprint meta
  59. 59. Scrum Master
  60. 60. Scrum Master - solve blocks
  61. 61. Scrum Master - solve blocks - motivation
  62. 62. Scrum Master - solve blocks - motivation - education of the team
  63. 63. Scrum Master - solve blocks - motivation - education of the team - give the right focus
  64. 64. Scrum Master - solve blocks - motivation - education of the team - give the right focus - identify weirdness
  65. 65. Scrum Master - keep the continues flow  - solve blocks - motivation - education of the team - give the right focus - identify weirdness
  66. 66. Dev Team
  67. 67. Dev Team - estimate
  68. 68. Dev Team - estimate - help each other
  69. 69. Dev Team - estimate - help each other - share the knowledge 
  70. 70. Dev Team - estimate - help each other - share the knowledge  - update kanban board
  71. 71. Dev Team - have the technical knowledge - estimate - help each other - share the knowledge  - update kanban board
  72. 72. Kanban
  73. 73. Kanban Boards
  74. 74. References http://agilemanifesto.org/ http://scrum.org/Scrum-Guides http://www.caelum.com.br/curso-agile-scrum/ http://images.google.com/ https://www.pivotaltracker.com/ http://scrumtool.me/ http://leankit.com/
  75. 75. Questions? Thanks Lennon Manchester @leManchester lennon.manchester@staunchrobots.com

×