Succeed with Scrum<br />By Satisha K Venkataramaiah<br />
What do you think?<br />India vs Pakistan match announced. Would India Team decide on a total?<br />Now they also know tha...
What do you think?<br />Now they are batting first? Would India Team decide on a total?<br />They are 200/3 in 30 overs, W...
No!!!<br />They work as a team, look at the current situation and accordingly act, right?<br />
Point is…<br />We Inspect and Adapt @ every point in your life, then why not in projects?<br />
So what did we learn?<br />We are people with different capabilities.<br />We perform at different levels at different tim...
So what’s the problem?<br />
Remember, we are developing SW<br />
64%implemented features are rarelyor never used<br />Focusing on customer needs ensures:<br />the right features are built...
Let me remind you!<br />You want a happy customer<br />..and you want to be happy as well<br />
Excercise!!!<br />
What do we do? Lets be Agile!<br />
So Scrum eh!<br />A cross-functional and self-organizing team<br />People are different and have different capabilities<br...
5 Scrum Values<br />Focus<br />Commitment<br />Respect<br />Courage<br />Openness<br />
The Essence of Scrum<br />SCRUM<br />Sprint<br />Produce<br />Plan<br />Inspect<br />Transparency<br />Adapt<br />
Feature A<br />DESIGN <br />Feature B<br />TEST<br />TEST<br />TEST<br />TEST<br />CODE<br />CODE<br />CODE<br />CODE<br /...
Who are all part of Happy Family!<br />Stakeholders<br />Product Owner<br />Scrum Master<br />The Team<br />
Product Owner<br />Responsible for maximizing the value of the work that the Team does<br /><ul><li>Owns the vision and ov...
Owns the prioritized list of what needs to be produced to achieve maximum value and ROI (the Product Backlog)
Decides when product is ready to ship</li></li></ul><li>Scrum Master<br />Responsible ensuring the Scrum process is unders...
P rocess Owner
Teaches Scrum to Team, PO, and stakeholders
Coaches the Team, PO, and stakeholders to achieve maximum value and ROI by improving practices
Change agent for the organization
P roblem Solver
Helps remove blocks and assists the Team and Product Owner
P rotector
Protects the Team from disruption</li></li></ul><li>The Team<br /><ul><li>Responsible for doing the work
7 +/- 2 People
Cross-functional
Self-organizing</li></li></ul><li>Let’s Play a Game<br />
Product Backlog<br /><ul><li>The requirements
A list of all desired work on the project
Ideally expressed such that each item has value to the users or customers of the product
Prioritized by the product owner
Reprioritized at the start of each sprint</li></li></ul><li>A Sample Product Backlog<br />
The Product Owner<br />owns the Product Backlog<br /><ul><li>PO Decides what is on the  Product Backlog
 Product Owner decides what  the prioritization is
 The Team, SM, and  stakeholders give input and  advice</li></ul>Feature<br />Feature<br />Feature<br />Feature<br />Featu...
Detailed appropriately<br />Estimated<br />Emergent<br />Prioritized<br />Feature<br />Feature<br />Feature<br />Feature<b...
Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Featu...
Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Featu...
Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Featu...
Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Featu...
The Goal of the Sprint: Done!<br />The team’s goal at the end of each Sprint is to be “Done” with the Product Backlog Item...
Code complete<br />Code reviewed<br />Developer tests automated<br />Customer tests automated<br />System Docs Updated<br ...
Excercise!!!<br />
Lets Start the Action!<br />
Sprint Planning Meeting<br />Conducted by the Team, the Product Owner, and the Scrum Master together<br />Different Approa...
Should you go for velocity based estimation directly?<br />No!!! Know your velocity first<br />
Work Time Available<br />Sprint Planning<br />½ day<br />½ day<br />Review and Retrospective<br />
Work Time Available<br />Buffer (5-10%)<br />Time for Backlog Grooming (5-10%)<br />-15<br />-15<br />180<br />TOTAL <br />
Upcoming SlideShare
Loading in...5
×

Succeed with Scrum - Part 1

1,094

Published on

A presentation on succeeding with Scrum - Part 1.

References:
CSM Material from Pete Deemer
Scrum presentations from Mike Cohn

1 Comment
1 Like
Statistics
Notes
  • Hi,
    I really like the way, you have presented the Agile concept.
    Wanted to have a copy of this to use it internally.
    Please send me the same if that is ok for you.
    Regards,
    RIcha
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
1,094
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
1
Likes
1
Embeds 0
No embeds

No notes for slide
  • Video of “never to fart” from the movie license to wedVideo of Scope creep
  • We work together as team and solve the problems together… The team includes the customer as well.So we are people and we have our own needs. We fulfill everybody’s needs.
  • Succeed with Scrum - Part 1

    1. 1. Succeed with Scrum<br />By Satisha K Venkataramaiah<br />
    2. 2. What do you think?<br />India vs Pakistan match announced. Would India Team decide on a total?<br />Now they also know that its @ Mohali. Would India Team decide on a total?<br />
    3. 3. What do you think?<br />Now they are batting first? Would India Team decide on a total?<br />They are 200/3 in 30 overs, Would they decide on a total?<br />
    4. 4. No!!!<br />They work as a team, look at the current situation and accordingly act, right?<br />
    5. 5. Point is…<br />We Inspect and Adapt @ every point in your life, then why not in projects?<br />
    6. 6. So what did we learn?<br />We are people with different capabilities.<br />We perform at different levels at different times<br />We can’t foresee future<br />We need to inspect and adapt<br />
    7. 7. So what’s the problem?<br />
    8. 8. Remember, we are developing SW<br />
    9. 9. 64%implemented features are rarelyor never used<br />Focusing on customer needs ensures:<br />the right features are built<br />not wasting effort (and resources) on features that are not needed<br />Ref: Jim Johnson, Chairman of Standish Group, quoted in 2006 in: http://www.infoq.com/articles/Interview-Johnson-Standish-CHAOSSample: government and commercial organizations, no vendors, suppliers or consultants<br />9<br />
    10. 10. Let me remind you!<br />You want a happy customer<br />..and you want to be happy as well<br />
    11. 11. Excercise!!!<br />
    12. 12. What do we do? Lets be Agile!<br />
    13. 13. So Scrum eh!<br />A cross-functional and self-organizing team<br />People are different and have different capabilities<br />The team plans one sprint at a time<br />You want to know your rate of delivery NOW!<br />Product Owner decides what should be produced<br />You want to keep your customer happy right?<br />The team decides how much to commit to<br />You want to have life while you work<br />No changes accepted during sprint<br />You have committed and you need commitment from PO<br />Potentially shippable increment at the end of Sprint<br />Remember you wanted to make the customer happy!<br />
    14. 14.
    15. 15. 5 Scrum Values<br />Focus<br />Commitment<br />Respect<br />Courage<br />Openness<br />
    16. 16. The Essence of Scrum<br />SCRUM<br />Sprint<br />Produce<br />Plan<br />Inspect<br />Transparency<br />Adapt<br />
    17. 17. Feature A<br />DESIGN <br />Feature B<br />TEST<br />TEST<br />TEST<br />TEST<br />CODE<br />CODE<br />CODE<br />CODE<br />DESIGN<br />DESIGN<br />DESIGN<br />DESIGN<br />Feature C<br />Feature D<br />SPRINTWORKING<br />SPRINT PLANNING<br />Team has committed to features<br />A, B, C, and D in this 2-week Sprint<br />
    18. 18. Who are all part of Happy Family!<br />Stakeholders<br />Product Owner<br />Scrum Master<br />The Team<br />
    19. 19. Product Owner<br />Responsible for maximizing the value of the work that the Team does<br /><ul><li>Owns the vision and overall goals
    20. 20. Owns the prioritized list of what needs to be produced to achieve maximum value and ROI (the Product Backlog)
    21. 21. Decides when product is ready to ship</li></li></ul><li>Scrum Master<br />Responsible ensuring the Scrum process is understood and followed<br /><ul><li>3 P’s:
    22. 22. P rocess Owner
    23. 23. Teaches Scrum to Team, PO, and stakeholders
    24. 24. Coaches the Team, PO, and stakeholders to achieve maximum value and ROI by improving practices
    25. 25. Change agent for the organization
    26. 26. P roblem Solver
    27. 27. Helps remove blocks and assists the Team and Product Owner
    28. 28. P rotector
    29. 29. Protects the Team from disruption</li></li></ul><li>The Team<br /><ul><li>Responsible for doing the work
    30. 30. 7 +/- 2 People
    31. 31. Cross-functional
    32. 32. Self-organizing</li></li></ul><li>Let’s Play a Game<br />
    33. 33. Product Backlog<br /><ul><li>The requirements
    34. 34. A list of all desired work on the project
    35. 35. Ideally expressed such that each item has value to the users or customers of the product
    36. 36. Prioritized by the product owner
    37. 37. Reprioritized at the start of each sprint</li></li></ul><li>A Sample Product Backlog<br />
    38. 38. The Product Owner<br />owns the Product Backlog<br /><ul><li>PO Decides what is on the Product Backlog
    39. 39. Product Owner decides what the prioritization is
    40. 40. The Team, SM, and stakeholders give input and advice</li></ul>Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Product Backlog<br />
    41. 41. Detailed appropriately<br />Estimated<br />Emergent<br />Prioritized<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />1<br />2<br />2<br />3<br />2<br />3<br />1<br />1<br />3<br />2<br />Feature<br />Feature<br />Feature<br />Feature<br />2<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />4<br />Feature<br />Feature<br />Feature<br />5<br />8<br />Feature<br />13<br />8<br />5<br />Feature<br />8<br />Feature<br />13<br />Feature<br />8<br />Feature<br />Product Backlog<br />
    42. 42. Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Detailed appropriately<br />Estimated<br />Emergent<br />Prioritized<br />Feature<br />Feature<br />Feature<br />Feature<br />2<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />4<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />New Feature<br />Feature<br />Feature<br />Product Backlog<br />
    43. 43. Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Detailed appropriately<br />Estimated<br />Emergent<br />Prioritized<br />Feature<br />Feature<br />Feature<br />Feature<br />2<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />4<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />New Feature<br />Feature<br />Feature<br />Product Backlog<br />
    44. 44. Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Detailed appropriately<br />Estimated<br />Emergent<br />Prioritized<br />Feature<br />Feature<br />Feature<br />Feature<br />2<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />New Feature<br />Feature<br />Feature<br />Product Backlog<br />
    45. 45. Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Detailed appropriately<br />Estimated<br />Emergent<br />Prioritized<br />Feature<br />Feature<br />Feature<br />Feature<br />2<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />Feature<br />New Feature<br />Feature<br />Feature<br />Product Backlog<br />
    46. 46. The Goal of the Sprint: Done!<br />The team’s goal at the end of each Sprint is to be “Done” with the Product Backlog Items they committed to<br />But what does “Done” mean?<br />Coded?<br />Coded, integrated, comprehensively tested, fully documented with no defects remaining?<br />To be clear about what we mean, the Product Owner and Team must agree on a “Definition of Done”<br />Decided before the first Sprint begins<br />Will evolve over time as team’s practices improve<br />
    47. 47. Code complete<br />Code reviewed<br />Developer tests automated<br />Customer tests automated<br />System Docs Updated<br />End-User Docs Updated<br />No P1 or P2 defects<br />
    48. 48. Excercise!!!<br />
    49. 49. Lets Start the Action!<br />
    50. 50. Sprint Planning Meeting<br />Conducted by the Team, the Product Owner, and the Scrum Master together<br />Different Approaches to Sprint Planning<br />Velocity-based<br />Once a Team has a stable history of how much Product Backlog they can complete in a Sprint, they commit based on this recent historical average<br />Capacity-based<br />Team estimates its capacity for work during the Sprint (in hours or days, for example), then commits to only as many Product Backlog items as they have capacity for<br />
    51. 51. Should you go for velocity based estimation directly?<br />No!!! Know your velocity first<br />
    52. 52. Work Time Available<br />Sprint Planning<br />½ day<br />½ day<br />Review and Retrospective<br />
    53. 53. Work Time Available<br />Buffer (5-10%)<br />Time for Backlog Grooming (5-10%)<br />-15<br />-15<br />180<br />TOTAL <br />
    54. 54. Sprint Planning: Task Assignment<br />Nobody assigns tasks<br />The team members pick up the right task for them<br />
    55. 55. What if PO pushes you get more done?<br />Be honest about your capabilities<br />Commit to only what you can deliver<br />You are not saying “no” to the whole person<br />“No” does not require an explanation.<br />Say<br />Its Not a Dirty Word<br />
    56. 56. Four Steps to Saying “No”<br />Listen to the request<br />Say ‘No’ immediately <br />
    57. 57. Four Steps to Saying No<br />Offer to find an alternative<br />Give a reason for refusal<br />
    58. 58. Feature A<br />DESIGN <br />Feature B<br />TEST<br />TEST<br />TEST<br />TEST<br />CODE<br />CODE<br />CODE<br />CODE<br />DESIGN<br />DESIGN<br />DESIGN<br />DESIGN<br />Feature C<br />Feature D<br />SPRINTWORKING<br />SPRINT PLANNING<br />Team has committed to features<br />A, B, C, and D in this 2-week Sprint<br />
    59. 59. Managing the sprint backlog<br /><ul><li>Any team member can add, delete or change the sprint backlog
    60. 60. Work for the sprint emerges
    61. 61. If work is unclear, define a sprint backlog item with a larger amount of time and break it down later
    62. 62. Update work remaining as more becomes known</li></li></ul><li>A sprint backlog<br />8<br />4<br />8<br />16<br />12<br />4<br />10<br />8<br />16<br />11<br />8<br />16<br />12<br />8<br />8<br />8<br />8<br />8<br />4<br />Add error logging<br />8<br />Tasks<br />Mon<br />Tues<br />Wed<br />Thur<br />Fri<br />Code the user interface<br />Code the middle tier<br />Test the middle tier<br />Write online help<br />Write the foo class<br />
    63. 63. A sprint burndownchart (Run Rate)<br />Hours<br />
    64. 64. 4<br />8<br />12<br />7<br />10<br />16<br />11<br />16<br />8<br />Tasks<br />Mon<br />Tues<br />Wed<br />Thur<br />Fri<br />Code the user interface<br />8<br />Code the middle tier<br />16<br />Test the middle tier<br />8<br />Write online help<br />12<br />50<br />40<br />30<br />Hours<br />20<br />10<br />0<br />Mon<br />Tue<br />Wed<br />Thu<br />Fri<br />
    65. 65. SCRUM<br /> ScrumMaster<br />Input from End-Users,<br />Customers, Team andOther Stakeholders<br />Daily ScrumMeeting andArtifacts Update<br />Product<br />Backlog<br />Grooming<br />Sprint<br />4 Weeks or Less<br />Team<br />Product Owner<br />Review<br />Feature A<br />Feature B<br />Feature C<br />Feature D<br />Feature E<br />Feature F<br />Feature G<br />Feature H<br />Feature I<br />Feature J<br />Feature K<br />Feature L<br />Feature A<br />Feature B<br />Feature C<br />Feature D<br />Feature E<br />Feature F<br />Feature G<br />1<br />Team Selects <br />How Much ToCommit To Do By Sprint’s End<br />2<br />3<br />TASKS<br />4<br />5<br />6<br />Potentially Shippable Product Increment<br />No Changes<br />in Duration or Goal<br />7<br />SprintBacklog<br />8<br />Sprint Planning<br />Meeting<br />9<br />10<br />11<br />Feature M<br />12<br />13<br />ProductBacklog<br />Retrospective<br />
    66. 66. Daily Scrum Meeting<br />Time box it to 15 minutes. <br />Nominate a watcher and ring an OSCAR style bell when 15 minutes are up.<br />Just answer 3 questions<br />No details and no problem solving<br />Identify impediments<br />Update the artifacts<br />
    67. 67. 3 Questions!<br />1<br />2<br />3<br />What did you do yesterday?<br />What will you do today?<br />Is anything in your way?<br />
    68. 68. Why the hell have I to meet everyday?<br />Helps you focus by creating an “anticipating culture”<br />Promotes “Openness” as everyone shares information<br />Helps team to respect each other for their knowledge<br />Reinforces commitment<br />Provides enough data that you can say No<br />
    69. 69. This is how your first sprint will go><br />But don’t give up!<br />
    70. 70. Excercise!!!<br />

    ×