0
Agile Methodology(SCRUM) Khushbu Desai(07030244003)
Agile Manifesto (2001) <ul><li>We are uncovering better ways of developing </li></ul><ul><li>software by doing it and help...
Principal #1:  Individuals and interaction  over  processes and tools
Principal #2: Working Software  over  Comprehensive Documentation Requirements Gathering Use Cases / Scenarios Functional ...
Principal #3: Customer collaboration  over  contract negotiation
Principal #4: Responding to change  over  following a plan
Total Transparency  At any time the status of the project is visible for everybody
Scrum Basics Pete Deemer CPO, Yahoo! India R&D
The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product...
The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product...
Product Owner <ul><li>Responsible for the overall project vision and goals </li></ul><ul><li>Responsible for managing proj...
The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product...
Team <ul><li>7 people, + or – 2 </li></ul><ul><ul><li>Has worked with as high as 15, as few as 3 </li></ul></ul><ul><ul><l...
The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product...
The Role of the ScrumMaster <ul><li>The ScrumMaster does everything in their power to help the team achieve success </li><...
What the ScrumMaster Does <ul><li>Serves the team </li></ul><ul><ul><li>The ScrumMaster takes action to help remove impedi...
The Basics of Scrum No Changes (in Duration or Deliverable) Commitment Product Backlog 4-Week Sprint Potentially Shippable...
Product Backlog Product Owner lists items in descending order of priority (highest priority item is listed first, next-hig...
Product Backlog <ul><li>List of everything that could ever be of value to the business for the team to produce </li></ul><...
The Basics of Scrum No Changes (in Duration or Deliverable) Commitment Product Backlog 4-Week Sprint Potentially Shippable...
Sprint Planning Meeting <ul><li>Takes place before the start of every Sprint </li></ul><ul><li>Team decides  how much Prod...
Sprint Pre-Planning Meeting <ul><li>Not textbook Scrum, but many teams find it useful </li></ul><ul><li>Takes place severa...
The Sprint Backlog Day of Sprint Backlog Item Task Owner Initial Est. 1 2 3 4 5 6 Enable all users to place book in shoppi...
Daily Scrum Meeting <ul><li>Every weekday </li></ul><ul><li>Whole team attends </li></ul><ul><li>Everyone stands </li></ul...
Table Exercise: Daily Scrum Meeting <ul><li>Do a Daily Scrum Meeting for your table </li></ul><ul><ul><li>One person plays...
Updating the Sprint Backlog <ul><li>Before or after the Daily Scrum, team members update the hours remaining on the Sprint...
Updating the Sprint Backlog Day of Sprint Backlog Item Task Owner Initial Est. 1 2 3 4 5 6 Enable all users to place book ...
The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product...
Sprint Review <ul><li>Purpose of the Sprint Review is </li></ul><ul><ul><li>Demo what the team has built </li></ul></ul><u...
The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product...
Sprint Retrospective <ul><li>What is it? </li></ul><ul><ul><li>1-2 hour meeting following each Sprint Demo </li></ul></ul>...
Velocity – Based on Historical Data Team’s Recent Sprints 90 points 120 points 100 points ~105 size points per Sprint
Thank You
Upcoming SlideShare
Loading in...5
×

Agile Methodology(SCRUM)

11,887

Published on

Published in: Technology, Business
2 Comments
12 Likes
Statistics
Notes
No Downloads
Views
Total Views
11,887
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
938
Comments
2
Likes
12
Embeds 0
No embeds

No notes for slide
  • Transcript of "Agile Methodology(SCRUM)"

    1. 1. Agile Methodology(SCRUM) Khushbu Desai(07030244003)
    2. 2. Agile Manifesto (2001) <ul><li>We are uncovering better ways of developing </li></ul><ul><li>software by doing it and helping others do it. </li></ul><ul><li>Through this work we have come to value: </li></ul><ul><li>Individuals and interaction over processes and tools </li></ul><ul><li>Working Software over Comprehensive Documentation </li></ul><ul><li>Customer collaboration over contract negotiation </li></ul><ul><li>Responding to change over following a plan </li></ul><ul><li>That is, while there is value in the items on </li></ul><ul><li>the right, we value the items on the left more . </li></ul>
    3. 3. Principal #1: Individuals and interaction over processes and tools
    4. 4. Principal #2: Working Software over Comprehensive Documentation Requirements Gathering Use Cases / Scenarios Functional Specs Design Specs Code Integrate Test Fix User Stories / Project Plan Iteration 1 Iteration 2 Iteration 3 Iteration 4 Design / Code / Test Stories for Next Iteration
    5. 5. Principal #3: Customer collaboration over contract negotiation
    6. 6. Principal #4: Responding to change over following a plan
    7. 7. Total Transparency At any time the status of the project is visible for everybody
    8. 8. Scrum Basics Pete Deemer CPO, Yahoo! India R&D
    9. 9. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective 7 8 9 10 11 12 1 2 3 4 5 6 13
    10. 10. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective
    11. 11. Product Owner <ul><li>Responsible for the overall project vision and goals </li></ul><ul><li>Responsible for managing project ROI vs. risk </li></ul><ul><li>Responsible for taking all inputs into what the team should produce, and turning it into a prioritized list (the Product Backlog) </li></ul><ul><li>Participates actively in Sprint Planning and Sprint Review meetings, and is available to team throughout the Sprint </li></ul><ul><li>Determines release plan and communicates it to upper management and the customer </li></ul>
    12. 12. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective
    13. 13. Team <ul><li>7 people, + or – 2 </li></ul><ul><ul><li>Has worked with as high as 15, as few as 3 </li></ul></ul><ul><ul><li>Can be shared with other teams (but better when not) </li></ul></ul><ul><ul><li>Can change between Sprints (but better when they don’t) </li></ul></ul><ul><ul><li>Can be distributed (but better when colocated) </li></ul></ul><ul><li>Cross-functional </li></ul><ul><ul><li>Possesses all the skills necessary to produce an increment of potentially shippable product </li></ul></ul><ul><ul><li>Team takes on tasks based on skills, not just official “role” </li></ul></ul><ul><li>Self-managing </li></ul><ul><ul><li>Team manages itself to achieve the Sprint commitment </li></ul></ul>
    14. 14. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective
    15. 15. The Role of the ScrumMaster <ul><li>The ScrumMaster does everything in their power to help the team achieve success </li></ul><ul><li>This includes: </li></ul><ul><ul><li>Serving the team </li></ul></ul><ul><ul><li>Protecting the team </li></ul></ul><ul><ul><li>Guiding the team’s use of Scrum </li></ul></ul>
    16. 16. What the ScrumMaster Does <ul><li>Serves the team </li></ul><ul><ul><li>The ScrumMaster takes action to help remove impediments to the team’s effectiveness </li></ul></ul><ul><ul><li>The ScrumMaster facilitates the team’s group interactions, to help the team achieve its full potential </li></ul></ul><ul><li>Protects the team </li></ul><ul><ul><li>The ScrumMaster protects the team from anything that threatens its effectiveness, such as outside interference or disruption </li></ul></ul><ul><ul><li>The ScrumMaster will need to confront uncomfortable issues, both inside and outside the team </li></ul></ul><ul><li>Guiding the team’s use of Scrum </li></ul><ul><ul><li>The ScrumMaster teaches Scrum to the team and organization </li></ul></ul><ul><ul><li>The ScrumMaster ensures that all standard Scrum rules and practices are followed </li></ul></ul><ul><ul><li>The ScrumMaster organizes all Scrum-related practices </li></ul></ul>
    17. 17. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment Product Backlog 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective
    18. 18. Product Backlog Product Owner lists items in descending order of priority (highest priority item is listed first, next-highest is second, etc.) Size estimates are rough estimates (can either be arbitrary “points”, or “ideal days”)
    19. 19. Product Backlog <ul><li>List of everything that could ever be of value to the business for the team to produce </li></ul><ul><li>Ranked in order of priority </li></ul><ul><ul><li>Priority is a function of business value versus risk </li></ul></ul><ul><li>Product Owner can make any changes they want before the start of a Sprint Planning Meeting </li></ul><ul><ul><li>Items added, changed, removed, reordered </li></ul></ul><ul><li>How much documentation is up to the team and Product Owner to decide </li></ul><ul><li>The farther down the list, the bigger and less defined the items become </li></ul><ul><ul><li>~2 Sprints worth are defined in detail </li></ul></ul>
    20. 20. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment Product Backlog 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective
    21. 21. Sprint Planning Meeting <ul><li>Takes place before the start of every Sprint </li></ul><ul><li>Team decides how much Product Backlog it will commit to complete by the end of the Sprint, and comes up with a plan and list of tasks for how to achieve it </li></ul><ul><li>What’s a good commitment? </li></ul><ul><ul><li>Clearly understood by all </li></ul></ul><ul><ul><li>Shared among the team </li></ul></ul><ul><ul><li>Achievable without sacrificing quality </li></ul></ul><ul><ul><li>Achievable without sacrificing sustainable pace </li></ul></ul><ul><li>Attended by Team, Product Owner, ScrumMaster, Stakeholders </li></ul><ul><li>May require 1-2 hours for each week of Sprint duration </li></ul><ul><ul><li>2 week Sprint = 2-4 hours, 4 week Sprint = 4-8 hours </li></ul></ul>
    22. 22. Sprint Pre-Planning Meeting <ul><li>Not textbook Scrum, but many teams find it useful </li></ul><ul><li>Takes place several days before the end of a Sprint (and start of the next Sprint </li></ul><ul><li>Product Owner spends an hour walking the team through the items at the top of the Product Backlog for the next Sprint </li></ul><ul><li>Team asks questions, requests clarification, recommend items to be broken down further </li></ul>Weds Thurs Fri Mon Tues Pre-Meeting for Sprint 4 Review & Retrospective for Sprint 3 (afternoon) Sprint Planning Meeting for Sprint 4 (morning) Sprint 4 Begins
    23. 23. The Sprint Backlog Day of Sprint Backlog Item Task Owner Initial Est. 1 2 3 4 5 6 Enable all users to place book in shopping cart Design business logic Sanjay 4 Design user interface Jing 2 Implement back-end code Tracy 2 Implement front-end code Tracy 6 Complete documentation Joe 8 Unit testing Philip 4 Regression testing Philip 2 Upgrade transaction processing module Implement back-end code Tracy 5 Complete documentation Joe 6 Unit testing Philip 3 Regression testing Philip 3 Total 214
    24. 24. Daily Scrum Meeting <ul><li>Every weekday </li></ul><ul><li>Whole team attends </li></ul><ul><li>Everyone stands </li></ul><ul><li>Lasts 15 minutes or less </li></ul><ul><li>Everyone reports 3 things only to each other </li></ul><ul><ul><li>What was I able to accomplish since last meeting </li></ul></ul><ul><ul><li>What will I try to accomplish by next meeting </li></ul></ul><ul><ul><li>What is blocking me </li></ul></ul><ul><li>No discussion, conversation until meeting ends </li></ul><ul><li>Product Owner can attend and report </li></ul><ul><li>Update of artifacts after standup </li></ul>
    25. 25. Table Exercise: Daily Scrum Meeting <ul><li>Do a Daily Scrum Meeting for your table </li></ul><ul><ul><li>One person plays the role of ScrumMaster </li></ul></ul><ul><ul><li>The rest of the table are team-members </li></ul></ul><ul><li>Each team-member reports to the group: </li></ul><ul><ul><li>What I was able to get done since last Daily Standup Meeting </li></ul></ul><ul><ul><li>What I will try to get done by the next Daily Standup Meeting </li></ul></ul><ul><ul><li>What is blocking me? (If nothing, say “No Blocks”) </li></ul></ul><ul><li>But there is a twist… </li></ul>
    26. 26. Updating the Sprint Backlog <ul><li>Before or after the Daily Scrum, team members update the hours remaining on the Sprint Backlog </li></ul>
    27. 27. Updating the Sprint Backlog Day of Sprint Backlog Item Task Owner Initial Est. 1 2 3 4 5 6 Enable all users to place book in shopping cart Design business logic Sanjay 4 2 0 Design user interface Jing 2 2 2 Implement back-end code Tracy 2 4 2 Implement front-end code Tracy 6 6 6 Complete documentation Joe 8 6 6 Unit testing Philip 4 3 3 Regression testing Philip 2 2 2 Upgrade transaction processing module Implement back-end code Tracy 5 10 8 Complete documentation Joe 6 6 6 Unit testing Philip 3 3 3 Regression testing Philip 3 2 2 Total 214 220 205
    28. 28. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective
    29. 29. Sprint Review <ul><li>Purpose of the Sprint Review is </li></ul><ul><ul><li>Demo what the team has built </li></ul></ul><ul><ul><li>Generate feedback, which the Product Owner can incorporate in the Product Backlog </li></ul></ul><ul><li>Attended by Team, Product Owner, ScrumMaster, functional managers, and any other stakeholders </li></ul><ul><li>A demo of what’s been built, not a presentation about what’s been built </li></ul><ul><ul><li>no Powerpoints allowed! </li></ul></ul><ul><li>Usually lasts 1-2 hours </li></ul><ul><li>Followed by Sprint Retrospective </li></ul>
    30. 30. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective
    31. 31. Sprint Retrospective <ul><li>What is it? </li></ul><ul><ul><li>1-2 hour meeting following each Sprint Demo </li></ul></ul><ul><ul><li>Attended by Product Owner, Team, ScrumMaster </li></ul></ul><ul><ul><li>Usually a neutral person will be invited in to facilitate </li></ul></ul><ul><ul><li>What’s working and what could work better </li></ul></ul><ul><li>Why does the Retrospective matter? </li></ul><ul><ul><li>Accelerates visibility </li></ul></ul><ul><ul><li>Accelerates action to improve </li></ul></ul>
    32. 32. Velocity – Based on Historical Data Team’s Recent Sprints 90 points 120 points 100 points ~105 size points per Sprint
    33. 33. Thank You
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×