Zen of Scrum

download Zen of Scrum

of 57

  • date post

  • Category


  • view

  • download


Embed Size (px)


Introduction to Scrum: a product development framework based on agile principles.

Transcript of Zen of Scrum

  • 1. Zen of Scrum

2. Agile Manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a planThat is, while there is value in the items on the right, we value the itemson the left more. 3. Scrum Goals Deliver working (potentially Workshippable) software frequently bydeveloping functioning software ineach iteration Transparency Favor customer collaboration byencouraging customer involvement Inspectthroughout the project Respond to changingrequirements, even late inAdaptdevelopment, by not planningahead in too much detail Avoid procrastination, or studentsScrum employs ansyndrome, by working in smalliterative, incremental approach toincrementsoptimize predictability and controlrisk. - Scrum Guide 4. Scrum Values Courage Commitment Respect Openness Focus 5. Scrum Distilledscrum team iterationseventsDaily Scrum Daily Scrum24 hoursStand-Up MasterSprintSprintPlanning2-4 weeks Team Sprint backlogSprintReview Product ReleaseSprint Owner 2-6 months RetrospectiveProduct backlogIncrement 6. Scrum TeamProductScrumTeamOwnerMaster (Developers) Responsible for Product Ensure Scrum is Deliver potentially Backlog (PBL) understood and enacted releasable increment of Ensure developers Scrum coachDone product at the understand PBL items Removing impediments end of each Sprint Maximize ROI Facilitate meetings Self-organizing Cross-functional Scrum Teams deliver productsdesigned to optimize iteratively andflexibility, creativity, and productivity.incrementally, maximizing- Scrum Guideopportunities for feedback. - Scrum Guide 7. Definition of DoneIt is crucial to have the same definition of done in the Scrumteam, between teams, across the organization, and whentalking to other stakeholders and customers. Everybody must understand what done means Helps during estimation Ensures transparency Helps to avoid technical debt As Scrum Teams mature, it isexpected that their Definitionof Done will expand toinclude more stringent criteriafor higher quality.- Scrum Guide 8. http://www.flickr.com/photos/calypso/2767592937/Planning and Estimation 9. Product Backlog Ordered list of everything that might be needed in theproduct Single source of requirements DynamicThe Product Backlog is often ordered byvalue, risk, priority, and necessity. Top-ordered Product Backlog items driveimmediate development activities. The higherthe order, the more a Product Backlog itemhas been considered, and the more consensusexists regarding it and its value. - Scrum Guide 10. User StoriesStory XYZ123As a ...I want to ...So that I can ... 5 points 11. User StoriesINVEST in the user stories Independent avoid dependencies on other stories Negotiable stories are not a contract Valuable show the value to customers/stakeholders Estimable sufficient detail needs to be present Sized right small enough to complete in one sprint Testable Acceptance criteria should be apparent in story 12. Estimation Key Points Its easier to estimate relatively than absolutely Its difficult impossible to accurately estimate calendar time Firmly establish estimates by team commitment Separate the task of estimating size and duration Only re-estimate relative changes 13. Cone of Uncertainty4xestimation accuracy2x 1x 0.5x0.25x Project evolvement 14. Story Points vs Ideal Days Ideal days are easily confused with calendar time, especiallywhen communicating outside the team My ideal day is not your ideal day Ideal days always have a relationship to calendar days. If theproject takes twice the ideal days in calendar time tofinish, it does not mean the team is 50% efficient If everything takes longer (or shorter, even though longer ismuch more common :-P) you do not have to re-estimate;this is more intuitive using story points 15. Estimating with Story Points 16. Estimating with Story Points2 3521 17. Story PointsStoriesEpics0 1 2 3 5 8 13 20 40 100 18. Story Points0x80 19. Story PointsXS S ML XL 20. Poker Planning 21. Story Splitting Sometimes stories are too big for one sprint Story Splitting Patterns Boundaries: Operational, data, interfaces Remove cross-cutting concerns: Logging, Exception handling, ... Functional and non-functional aspects Business value Anti-Patterns When in doubt,do a spike solution 22. http://www.flickr.com/photos/john_scone/493915787/The Sprint 23. Sprint PlanningAgendaParticipants Select user stories Product Owner Identify and estimate Scrum Mastertechnical tasks Developers Come up with sprint goalTwo parts: (a) Selecting stories and (b) identifying tasks. ThePO and stakeholders only need to participate in the firsthalf, but must still be available during the second half. 24. Sprint Planning 1 hrs 2 hrsStory 1 123 4 hrs 4 hrs5 points 1 hrs 8 hrs 25. Product Backlog GroomingAgendaParticipants Update the product Product Ownerbacklog Scrum Master Refine and split top stories Developers Estimate stories 26. Sprint Rules No changes affecting the Sprint goal No changes to team Scope may be discussed, re-negotiated and clarifiedas knowledge is gained 27. Sprint Emergency ProcedureThree questions to ask before canceling a sprint: 1. Can anything be changed inthe way work is done? 2. Can anyone outside the teamhelp? 3. Can something be droppedfrom the sprint backlog? 28. Sprint LengthSize matters. Shorter is better! Feedback more often Stable velocity quicker React to changes faster Learn processes faster If it wasnt for the last minute, nothing would ever getdone. - a lot more last minutes 29. Daily Stand-Up MeetingAgendaParticipants What has been accomplished Scrum Mastersince the last meeting? Developers What will be done before the Passive: Other interestednext meeting?parties - only listen! What obstacles are in theway?Same time and place every day. Only answer the threequestions, keep any discussions outside the meeting.Instead, meet immediately after the Daily Scrum for re-planning and further discussions. 30. Sprint BacklogSTORY TO DO IN PROGRESSDONE SPRINT GOAL Implement aStory 1 123 working API 5 points BURNDOWN CHARTStory 2 127 1 points UNPLANNEDStory 3 213 8 pointsNEXTStory 4129 5 points 5 points 3 points 31. Sprint BacklogSTORY TO DOIN PROGRESSDONE SPRINT GOALImplement aStory 1 123 MNworking API 5 pointsBURNDOWN CHARTSAStory 2 127 1 pointsUNPLANNEDStory 3 213 PL 8 points NEXT Story 41295 points5 points3 points 32. Sprint BacklogSTORY TO DOIN PROGRESSDONE SPRINT GOALImplement aStory 1 123 MN SAworking API 5 pointsBURNDOWN CHARTSAStory 2 127 1 pointsUNPLANNEDStory 3 213PL 8 points NEXTPL Story 41295 points5 points3 points 33. Sprint BacklogSTORY TO DOIN PROGRESSDONE SPRINT GOALImplement aStory 1 123 MN SAworking API 5 pointsBURNDOWN CHARTSA MNStory 2 127PL 1 pointsUNPLANNEDStory 3 213PLSA 8 points NEXTMN PL Story 41295 points5 points3 points 34. Sprint BacklogSTORY TO DO TESTS COMPLETEIN PROGRESSDONE HOURS(2)Story 1 123 SA 32 5 pointsMN SAStory 2 127 1 points8Story 3 213 PL 8 points 48 PL 35. Sprint Burndown ChartHoursDays 36. Sprint ReviewAgendaParticipants What has been Product Ownerdone, what has not been Scrum Masterdone Developers What went well, anyproblems Stakeholders Product backlog What to do next 37. Sprint RetrospectiveAgenda Participants Inspect last sprint Scrum Master People and relationships Developers Process and tools Identify potentialimprovements Plan for implementingimprovements 38. http://www.flickr.com/photos/acediscovery/3030548744/ Release Planning 39. Release PlanningAgenda Participants Goal for the release Product Owner Identify features Stakeholders Rough estimates Scrum Master Create a release plan Developers 40. Release PlanningFixed Date Fixed Scope Can Have X weeks Might Have Wont Have 41. Release Burndown ChartStory PointsSprints 42. Release Burndown Bar Chart Team Progress Completed stories Re-estimationsStory pointsSprints Workload changes Added features Removed features 43. Parking Lot DiagramTheme, subsystem, product Theme, epic, fe Theme, epic, fe Theme, epic, feature set ature set ature set (8) (8) (8) 50% 50% 0%Sprint 8Sprint 3 Sprint 10Theme, subsystem, productTheme, subsystem, product Theme, epic, fe Theme, epic, fe Theme, epic, fe Theme, epic, feature set ature set ature set ature set (8) (4) (8) (4)50% 25%0%0% Sprint 8Sprint 3 Sprint 12Sprint 12 44. http://www.flickr.com/photos/28481088@N00/2957770391/Scaling Scrum 45. Scrum of Scrums 46. Scaling Scrum Synchronize sprints between teams Do integration at sprint boundaries Coordinate work Lookahead planning Complexity increases 47. http://www.flickr.com/photos/darkroses/2357927668/Distributed Scrum 48. Distributed ScrumTo be successful... Shared vision and goal Tools for distributed Personal relationshipscollaboration Virtual Scrum boards Kick-off meeting Video conferencing Workshops Screen sharing Same standards andvalues Estimation Definition of Done 49. Distributed Daily Stand-Up Meetings Working Hours ATeamWorking Hours BTime 50. http://www.flickr.com/photos/droetker0912/5542920908/Additional Stuff 51. Scrum MisconceptionsScrum says documentationisnt important. Documentation is important, but working software is valued more. !People need to be cross-Teams need to be cross-functional. That soundsboth inefficient andunrealistic. functional, not people. Nonetheless, it is always a good idea not to rely on one person. Spread the knowledge. ! 52. Scrum MisconceptionsWe cant estimate in size, Ineed to know when we can Using story points you can stilldeliver. estimate when the project will be completed. The important differenceis that duration is derived from size. !Its not possible to mix Maybe you will not reach ScrumsScrum and our traditionalproject model (read:waterfall) full potential, but you can benefit from agile methods nontheless.! 53.