Three years of Scrum at The Netcircle
•
3 likes•1,050 views
This document summarizes the experiences of four scrum masters with using scrum over three years. It discusses improvements in communication, planning, requirements, delivery, agile practices, and teamwork since adopting scrum. Benefits included increased collaboration, clearer specifications, early delivery, and flexibility. Drawbacks included the potential for too many meetings or changes disrupting the team. The conclusion is that scrum is not perfect but has helped the organization by highlighting problems and being flexible.
More Related Content
What's hot
What's hot (20)
Similar to Three years of Scrum at The Netcircle
Similar to Three years of Scrum at The Netcircle (20)
Recently uploaded
Recently uploaded (20)
Three years of Scrum at The Netcircle
- 1. THREE YEARS OF SCRUM AT
- 2. SCRUM MASTERS Name: Jacky Hung Name: Aime Blaise Iranyumviye Doing Scrum: 3 years Doing Scrum: 3 years Been SM: 12 months Been SM: 12 months Name: Joshua Chi Name: Mik Pathikirikorale Doing Scrum: 1 year Doing Scrum: 3 years Been SM: 6 months Been SM: 3 months
- 3. AGENDA I.COMMUNICATION II.PLANNING III.REQUIREMENTS & CHANGES IV.DELIVERY V.SCRUM & AGILE VI.WORKING AS A TEAM
- 5. Before Scrum • one meeting a week • little client interaction • projects were independent
- 6. With Scrum • scrum meetings • demo every sprint, on-site PO • projects share code and people
- 7. What did we learn ? • Benefits: - left hand knows what the right hand is doing - product delivery every sprint - increases team collaboration • Drawbacks: - PO can disrupt the team - could lead to too many meetings
- 8. II.PLANNING
- 9. Before Scrum • no estimation • clients assigned tasks to people directly • clients not always available
- 10. With Scrum • planning meeting • PO must have a backlog • clients represented by onsite PO
- 11. What did we learn ? • Benefits: - realistic estimates - clients are more focused on what they want - P.O. available all the time • Drawbacks: - teams have more control of decisions - short term releases can be challenging
- 13. Before Scrum • no requirements standards • large chunks of work • no progress reports till finished • requirements likely to change during development
- 14. With Scrum • project/sprint backlog • user stories • demo of progress every sprint • sprint has set requirements
- 15. What did we learn ? • Benefits: - specification is much clearer to the team - user stories make life easier - updates on product progress - scrum embraces change • Drawbacks: - too many changes can be a bad thing - controlled creativity
- 16. IV.DELIVERY
- 17. Before Scrum • output not very often • client feedback slow • client feedback not always realistic
- 18. With Scrum • incremental delivery • sprint review • definition of DONE
- 19. What did we learn ? • Benefits: - early delivery - product reacts to market changes quickly - review and improve working process • Drawbacks: - iterative delivery may cause stress to developers
- 20. V.SCRUM & AGILE
- 21. Before Scrum • no real pair work • specific areas of expertise per person • new developers need teaching time
- 22. With Scrum • XP/PP - pair programming • scrum encourages flexibility • new developers taught through PP
- 23. What did we learn ? • Benefits: - code quality greatly improved - more people know about each area of the project - faster integration of new team members • Drawbacks: - not all agile processes work well with scrum
- 24. VI.WORKING AS A TEAM
- 25. Before Scrum • very specific roles • tasks assigned to individuals directly • lack of management/direction
- 26. With Scrum • cross-functional and flexible teams • team members choose tasks • self managed/organized teams
- 27. What did we learn ? • Benefits: - increase developer flexibility - developers hold more responsibility - more committed and pro-active team members • Drawbacks: - needs developers active and willing to change
- 28. CONCLUSION • Scrum is not a silver bullet • Scrum highlights problems • Scrum is flexible • Scrum’s helped us
- 29. Q &A