Your SlideShare is downloading. ×

Shayke's SCRUM @alphageeks 6

1,045

Published on

At the recent alphageeks 6 meetup, Shay Cohen is talking about his group's experience with implementing SCRUM. …

At the recent alphageeks 6 meetup, Shay Cohen is talking about his group's experience with implementing SCRUM.

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

  • Be the first to like this

No Downloads
Views
Total Views
1,045
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
17
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
  • Add animation and a “can’t commit”… Move a smaller up…
  • Transcript

    • 1. Scrum In Action
      Shay Cohen
      11/5/2010
    • 2. Agenda
      The Pain Points
      What is SCRUM ?
      Scrum Flow
      Roles
      Planning a Sprint
      Pillars & Principals
      The Results
      From hell to Heaven
      Recommendation
    • 3. Worked very similar way to waterfall
      Try define all at the beginning
      Break the plan
      Fix and delay as we go along
      Months ahead
      Every feature is P0
      Low productivity due to missing / changing requirements
      Low visibility during planning stage
      Long release cycles – TTM
      We establishing our RoB as we progress
      A lot of noise during the development – DCRs, Integrations, Bugs
      Poor WLB
      The Pain Points
      Areas for improvement:
      Communication
      Simplicity
      Feedback
      Courage
    • 4. SCRUM in 100 words
      Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time.
      It allows us to rapidly and repeatedly inspect actual working software.
      The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features.
      Every 5w anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.
    • 5. Scrum Flow
    • 6. Roles
      Product Owner
      PM
      SCRUM Masters
      Team Leaders
      • Represent the stakeholders
      • 7. Owner the Product backlog
      • 8. Owner the Sprint backlog
      • 9. Responsible for the prioritization process
      • 10. Approve removal of items during running sprint
      • 11. Protect the Team and keep them focused on the tasks in hand
      • 12. Manage the daily SCRUM meetings
      • 13. Update the dev task progress
      Teams
      Has the responsibility to deliver the product
    • 14. Planning a Sprint
      Product Backlog
      Iteration Backlog
      User Stories
      User Stories
      Tasks (hours)
      Commit!
      1
      1
      1
      Commit!
      Can’t Commit!
    • 15. Planning a Sprint
      Product Backlog
      Iteration Backlog
      User Stories
      User Stories
      Tasks (hours)
      Commit!
      1
      1
      1
      Commit!
      ?
      1
      Commit!
    • 16. Sprint Vs. Release
      Sprint
      Fixed duration
      Potentially deployable
      Release
      Fixed content
      Content of one or more Sprints
      Deployable
      Requires stabilization period and ZBB
    • 17. Pillars & Principals
      Planning take place before the sprint begin
      We only plan what we know (well defined)
      Each user story get unique priority
      High priority items should be scheduled to the beginning of the sprint
      We strive for HLD & STP before planning
      All tests are automated (Unit, Component, E2E)
      No test – no feature (E2E)
      Sprint N-1
      Planning N
      Sprint N
      Dev/Test
      Dev/Test
      Dev/Test
      Dev/Test
      Quality
      Sprint N+1
      Dev/Test
      Planning N+1
      Planning N+1
    • 18. Pillars & Principals
      Last week is for quality and planning – no “new” code
      No buffers – Every developer has a long tail of low priority user story
      New backlog items shall not be added to a running sprint
      Integrations are planned for beginning* of Sprint
      Deployments ? Integrations ? Live system support ?
      Sprint N-1
      Planning N
      Sprint N
      Dev/Test
      Dev/Test
      Dev/Test
      Dev/Test
      Quality
      Sprint N+1
      Dev/Test
      Planning N+1
      Planning N+1
    • 19. Addressing Pain Points
    • 20. The Results I
    • 21. The Results II
    • 22. From hell to Heaven
      The outcome
      The “right” feature are in, Nice-to-have / future are out
      Better TTM
      Better Quality
      Better transparency
      Less status reports/emails
      Less meetings
      Well known & establish ROB
      Developers have clear and quiet work plan and environment
      Better WLB
    • 23. Recommendations
      Organization
      Management buy-in / sponsorship
      All or nothing - PM/Test/Dev
      Daily scrum, Scrum of Scrums, Daily war-room on quality week
      Quality & Automation
      Test automation
      Smoke Tests on submit
      Nightly builds with BVT
      Weekly / bi-weekly FRS & Manual tests
      Quality week
      Quality gates
      State of mind
      Transparency & communication is the key
      Constantly give/take feedback
      Courage

    ×