Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Tweaking Scrum

11 views

Published on

Presentation from Agile Day Twin Cities 2017

Published in: Mobile
  • Be the first to comment

  • Be the first to like this

Tweaking Scrum

  1. 1. TWEAKING SCRUM Patrick Szalapski Senior Developer, General Mills Find me on LinkedIn, Facebook, Skype, Twitter @Szalapski
  2. 2. AGILE MEANS VALUING… 1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
  3. 3. SCRUM BASICS
  4. 4. SCRUM BASICS • A software product should be developed • by a self-organizing team • in multiple fixed-length sprints • in full collaboration with the product owner • using Agile values and principles throughout.
  5. 5. 1. DON’T BE SO STRICT ON USER STORIES
  6. 6. 1. DON’T BE SO STRICT ON USER STORIES
  7. 7. 1. DON’T BE SO STRICT ON USER STORIES
  8. 8. 1. DON’T BE SO STRICT ON USER STORIES
  9. 9. 1. DON’T BE SO STRICT ON USER STORIES
  10. 10. 1. DON’T BE SO STRICT ON USER STORIES
  11. 11. 2. BREAK UP THE SPRINT PLANNING MEETING •Do before sprint planning: •retrospective •stakeholder demo •planning poker •Do immediately after sprint planning: task breakdown
  12. 12. 3. STOP TRACKING HOURS ON TASKS
  13. 13. 4. CONSIDER SHORTER SPRINTS •Your sprint may be too long if… • Your product owner can’t wait till next sprint for important changes, OR • Any individual is working on more than one “big thing” in a sprint, OR • At the end of the sprint, there’s too many things to keep track of, OR • You can’t get sprint planning done in one day •Tackle 2/3+ of the work in 2/3 of the time
  14. 14. 5. ADD SPECIALIZED DEMOS AS NECESSARY The Sprint Demo is for the main stakeholder(s) and should be tailored for them If others need a more technical or more detailed demo, do it another time.
  15. 15. 6. REMEMBER THE POINT OF OUR RITUALS The purpose of… Is… Product backlog grooming/prioritization Ensure the team works on only the most important things all the time Sprint planning Get a sprint backlog that the team can complete Retrospective Find a few key areas to proactively improve Task breakdown Understand scope of work and plan as a team Planning poker Estimate complexity of work for prioritization Daily scrum For the team to collaborate and clear each other’s roadblocks Sprint demo Deliver to stakeholders and gather feedback
  16. 16. 7. LIGHTNING ROUND • Story points are abstract—can’t convert to hours/days • Embrace their abstract, relative, floating nature • …or just go ahead and estimate in hours/days • We are making software, not code: Find some key team members to help the Product Owner groom the backlog • Actually stand up in the daily scrum • Come up with big, strange, or helpful ideas within the team • Scrum only works if everyone on the team is trying hard
  17. 17. TWEAKING SCRUM Patrick Szalapski Senior Developer, General Mills Find me on LinkedIn, Facebook, Skype, Twitter @Szalapski

×