A presentation on succeeding with Scrum - Part 1. References: CSM Material from Pete Deemer Scrum presentations from Mike Cohn

1. Succeed with Scrum By Satisha K Venkataramaiah

2. What do you think? India vs Pakistan match announced. Would India Team decide on a total? Now they also know that its @ Mohali. Would India Team decide on a total?

3. What do you think? Now they are batting first? Would India Team decide on a total? They are 200/3 in 30 overs, Would they decide on a total?

4. No!!! They work as a team, look at the current situation and accordingly act, right?

5. Point is… We Inspect and Adapt @ every point in your life, then why not in projects?

6. So what did we learn? We are people with different capabilities. We perform at different levels at different times We can’t foresee future We need to inspect and adapt

7. So what’s the problem?

8. Remember, we are developing SW

9. 64%implemented features are rarelyor never used Focusing on customer needs ensures: the right features are built not wasting effort (and resources) on features that are not needed 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 9

10. Let me remind you! You want a happy customer ..and you want to be happy as well

11. Excercise!!!

12. What do we do? Lets be Agile!

13. So Scrum eh! A cross-functional and self-organizing team People are different and have different capabilities The team plans one sprint at a time You want to know your rate of delivery NOW! Product Owner decides what should be produced You want to keep your customer happy right? The team decides how much to commit to You want to have life while you work No changes accepted during sprint You have committed and you need commitment from PO Potentially shippable increment at the end of Sprint Remember you wanted to make the customer happy!

15. 5 Scrum Values Focus Commitment Respect Courage Openness

16. The Essence of Scrum SCRUM Sprint Produce Plan Inspect Transparency Adapt

17. Feature A DESIGN Feature B TEST TEST TEST TEST CODE CODE CODE CODE DESIGN DESIGN DESIGN DESIGN Feature C Feature D SPRINTWORKING SPRINT PLANNING Team has committed to features A, B, C, and D in this 2-week Sprint

18. Who are all part of Happy Family! Stakeholders Product Owner Scrum Master The Team

20. Owns the prioritized list of what needs to be produced to achieve maximum value and ROI (the Product Backlog)

22. P rocess Owner

23. Teaches Scrum to Team, PO, and stakeholders

24. Coaches the Team, PO, and stakeholders to achieve maximum value and ROI by improving practices

25. Change agent for the organization

26. P roblem Solver

27. Helps remove blocks and assists the Team and Product Owner

28. P rotector

30. 7 +/- 2 People

31. Cross-functional

34. A list of all desired work on the project

35. Ideally expressed such that each item has value to the users or customers of the product

36. Prioritized by the product owner

39. Product Owner decides what the prioritization is

40. The Team, SM, and stakeholders give input and adviceFeature Feature Feature Feature Feature Feature Feature Feature Feature Product Backlog

41. Detailed appropriately Estimated Emergent Prioritized Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature 1 2 2 3 2 3 1 1 3 2 Feature Feature Feature Feature 2 Feature Feature Feature Feature Feature Feature Feature 4 Feature Feature Feature 5 8 Feature 13 8 5 Feature 8 Feature 13 Feature 8 Feature Product Backlog

42. Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Detailed appropriately Estimated Emergent Prioritized Feature Feature Feature Feature 2 Feature Feature Feature Feature Feature Feature Feature 4 Feature Feature Feature Feature Feature Feature New Feature Feature Feature Product Backlog

43. Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Detailed appropriately Estimated Emergent Prioritized Feature Feature Feature Feature 2 Feature Feature Feature Feature Feature Feature Feature 4 Feature Feature Feature Feature Feature Feature New Feature Feature Feature Product Backlog

44. Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Detailed appropriately Estimated Emergent Prioritized Feature Feature Feature Feature 2 Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature New Feature Feature Feature Product Backlog

45. Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Detailed appropriately Estimated Emergent Prioritized Feature Feature Feature Feature 2 Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature New Feature Feature Feature Product Backlog

46. The Goal of the Sprint: Done! The team’s goal at the end of each Sprint is to be “Done” with the Product Backlog Items they committed to But what does “Done” mean? Coded? Coded, integrated, comprehensively tested, fully documented with no defects remaining? To be clear about what we mean, the Product Owner and Team must agree on a “Definition of Done” Decided before the first Sprint begins Will evolve over time as team’s practices improve

47. Code complete Code reviewed Developer tests automated Customer tests automated System Docs Updated End-User Docs Updated No P1 or P2 defects

48. Excercise!!!

49. Lets Start the Action!

50. Sprint Planning Meeting Conducted by the Team, the Product Owner, and the Scrum Master together Different Approaches to Sprint Planning Velocity-based 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 Capacity-based 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

51. Should you go for velocity based estimation directly? No!!! Know your velocity first

52. Work Time Available Sprint Planning ½ day ½ day Review and Retrospective

53. Work Time Available Buffer (5-10%) Time for Backlog Grooming (5-10%) -15 -15 180 TOTAL

54. Sprint Planning: Task Assignment Nobody assigns tasks The team members pick up the right task for them

55. What if PO pushes you get more done? Be honest about your capabilities Commit to only what you can deliver You are not saying “no” to the whole person “No” does not require an explanation. Say Its Not a Dirty Word

56. Four Steps to Saying “No” Listen to the request Say ‘No’ immediately

57. Four Steps to Saying No Offer to find an alternative Give a reason for refusal

58. Feature A DESIGN Feature B TEST TEST TEST TEST CODE CODE CODE CODE DESIGN DESIGN DESIGN DESIGN Feature C Feature D SPRINTWORKING SPRINT PLANNING Team has committed to features A, B, C, and D in this 2-week Sprint

60. Work for the sprint emerges

61. If work is unclear, define a sprint backlog item with a larger amount of time and break it down later

63. A sprint burndownchart (Run Rate) Hours

64. 4 8 12 7 10 16 11 16 8 Tasks Mon Tues Wed Thur Fri Code the user interface 8 Code the middle tier 16 Test the middle tier 8 Write online help 12 50 40 30 Hours 20 10 0 Mon Tue Wed Thu Fri

65. SCRUM ScrumMaster Input from End-Users, Customers, Team andOther Stakeholders Daily ScrumMeeting andArtifacts Update Product Backlog Grooming Sprint 4 Weeks or Less Team Product Owner Review Feature A Feature B Feature C Feature D Feature E Feature F Feature G Feature H Feature I Feature J Feature K Feature L Feature A Feature B Feature C Feature D Feature E Feature F Feature G 1 Team Selects How Much ToCommit To Do By Sprint’s End 2 3 TASKS 4 5 6 Potentially Shippable Product Increment No Changes in Duration or Goal 7 SprintBacklog 8 Sprint Planning Meeting 9 10 11 Feature M 12 13 ProductBacklog Retrospective

66. Daily Scrum Meeting Time box it to 15 minutes. Nominate a watcher and ring an OSCAR style bell when 15 minutes are up. Just answer 3 questions No details and no problem solving Identify impediments Update the artifacts

67. 3 Questions! 1 2 3 What did you do yesterday? What will you do today? Is anything in your way?

68. Why the hell have I to meet everyday? Helps you focus by creating an “anticipating culture” Promotes “Openness” as everyone shares information Helps team to respect each other for their knowledge Reinforces commitment Provides enough data that you can say No

69. This is how your first sprint will go> But don’t give up!

70. Excercise!!!