Scrum for high performance teams
0 likes354 views
This document outlines the principles and practices of Scrum, an agile model designed for high-performance teams, emphasizing transparency, inspection, and adaptation. It discusses essential roles within a Scrum team, key events such as sprint planning and daily scrums, and the importance of artifacts like the product backlog. The document also encourages teams to embrace agility, continually learn about Scrum, and adapt practices to suit their unique environments.
Scrum for high performance teams
- 1. SCRUM FOR HIGH PERFORMANCE TEAMS Laurynas Antanavičius Product Manager @ Data Dog 2014.12.02
- 2. ABOUT US • Custom web development and support • Cloud-based application and software development • B2B, B2C eCommerce solutions • Specialised in PHP • Over 35 developers • Wide base of clients: UK, US, UAE, Canada, Luxembourgh, France…
- 4. OUR TEAM • Crypto-Currency exchange / Forex market • 6 members in the development team • Agile - Scrum, TDD, CI, CD • PHP & GO
- 5. HOW WE WORK • Prioritise features with the PO • Work in short iterations - 2 weeks • Development team chooses the features • Write tests before each line of code (TDD & CI) • Ship the feature as soon as it is ready (CD) • Focus on performance & quality
- 6. SCRUM Born from a team game
- 8. WHAT IS IT? • Popular agile model • Lightweight • Easy to understand • Difficult to master
- 9. Individuals and interactions over Processes and tools Working software over Comprehensive documentation Customer collaboration over Contract negotiation Responding to change over Following a plan
- 10. SCRUM DEFINES • Practices • Roles • Events • Artifacts • Rules
- 12. THE THREE PILLARS • Transparency - giving and getting feedback • Inspection - checking how well a project is progressing • Adaptation - adjusting the process to minimise further issues
- 13. It takes courage to be fully transparent and to be fully responsible for the results you deliver. AND Scrum brings a binary understanding of what is “Done”.
- 16. THE SCRUM MASTER
- 17. THE SCRUM TEAM
- 18. EVENTS the game
- 19. SPRINT PLANNING • Sprint - time-boxed iteration of one month or less • Used to determine what will be delivered in that sprint
- 20. DAILY SCRUM • 15-minute timeboxed daily meeting • What has been achieved since last meeting? • What will be done before next meeting? • What obstacles are in the way?
- 21. SPRINT REVIEW • PO and Dev Team discuss the product increment and determine what to do next
- 22. SPRINT RETROSPECTIVE • Reflecting on the process and look for opportunities for improvement
- 23. ARTIFACTS can’t play a game without the ball, can you?
- 24. PRODUCT BACKLOG • Ordered list of everything that might be needed for the product that is elaborated progressively
- 25. SPRINT BACKLOG • A set of items from the Product Backlog that were selected for a specific sprint
- 26. DEFINITION OF DONE • A common definition as agreed with the team members
- 27. BE READY for a rough game
- 28. SHOCK THERAPY • Move from Waterfall to Agile • A Bootstrap to High Performance
- 29. HOW TO • Be reachable! • Follow the Rules defined in Scrum guide • Then deviate from the Rules • Find your own way
- 30. WHAT ARE THE RULES? • Recognise the roles • Follow the events and time-boxing • Perfect the artifacts • Find what motivates you as a team member
- 32. WHAT’S NEXT?
- 33. Read about it, understand it, memorise it, sleep with it… Until you are 100% confident with using Agile methods
- 34. XP “Extreme Programming” by Ron Jeffries, Ann Anderson, Chet Hendrickson http://xprogramming.com/
- 36. SCRUM “Scrum Guide” by Jeff Sutherland, Ken Schwaber http://www.scrumguides.org/
- 37. TEAMWORK “The Clean Coder” by Robert C. Martin
- 38. TDD, BDD… “Engineering Long-Lasting Software” by Armando Fox David Patterson
- 39. TRUST YOURSELF BEFORE TRUSTING ANYONE