Ognjen Pejovic - Scrum Framework

Osnove Scrum frejmvorka

Transcript

1. Scrum Framework “Easy to Learn it hard to master it” Ognjen Pejovic
2. Agenda 1. What do you think when you say SCRUM? 2. Is it SCRUM solution for every problem and project? 3. How I as software developer can benefit from it? 4. SCRUM framework in action 5. How to fu*k up your SCRUM? 6. Wrap up
3. 1. What do you think when you say SCRUM?
4. Where are difference between traditional and SCRUM • Meetings, meetings, meetings • “Management stuff” • 10x faster development – overtime? • How to differentiate from traditional management?
5. History • Waterfall thinking • Losing millions of dollars to deliver software in one or more years • Slow and hard adaptation to change • Agile manifesto – February 2001 • Agile principles • Scrum - founded in 1995 – Sutherland and Schwaber • 2001 first Scrum book • Beside software development until now SCRUM is adopted in marketing, operations and education…
6. Manifesto • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan
7. 2. Is it SCRUM Solution for every project?
8. There are approach how to choose it • How to discover is it Scrum or even Agile for you? Stacey matrix
9. 3. How I as software developer can benefit from it?
10. Do you know this situation?
11. There are a lot of benefits • High visibility of progress. • Regular feedback from customer. • Predictable rhythm. • Measurable productivity (via burndown, velocity, etc.). • Cross-functional, self-organising teams. • Inspect and adapt. • Low bureaucratic overhead (meetings, documentation, etc.). • Emphasis on face-to-face communication. • And these features lead to the following benefits: • Project can respond easily to change. • Problems are identified early. • Customer gets most beneficial work first. • Work done will better meet the customers needs. • Improved productivity. • Ability to maintain a predictable schedule for delivery
12. SCRUM values
13. 4. SCRUM framework in action
14. SCRUM in nutshells Ø We are running it in Sprint’s • An iteration with fixed duration Ø We have 5 meetings as part of each iteration • Sprint Planning • Daily Scrum • Product Backlog Refinement • Sprint Review • Sprint Retrospective Ø Delivery and outcome of each Sprint • Working product increment Ø 5 Documents • Product Vision • Product Backlog • Sprint Backlog • Sprint Burn down • Release Burn down Ø 3 roles • Development Team • Scrum Master • Product Owner
15. SCRUM process looks like this
16. There are new cool roles Ø Roles Overview • Ownership • Share Vision and tell story • Collaboration • Value • Features/UX • ROI • Knows Market • Servant Leader • Methodology Knowledge • Coach and facilitator • Remove impediments • Motivator • Develops Team • Help team with self organization • Self organized, empowered and autonomous • Cross functional • Team Size 7(+-)2 • Ideally full time allocated • Tells how product should be developed • Committed to Sprint Goals
17. Every Vision and Product starts with Great Idea
18. Product Backlog is formed from User Stories Ø Product Backlog is wish list for features that product will contain
19. What to do when Backlog is not ready Ø Product Backlog pitfall No 1.
20. Prerequisite for Sprint planning is Sprint goals Ø Sprint Planning is preparation session for User Stories that we will develop first. Outcome is Sprint Backlog which is fixed for iteration. Team: Tells How PO: Tells What SM: Facilitate process
21. How Scrum Team is functioning during Sprint Ø During Sprint key is to keep transparency on impediments and progress. 1. What we did yesterday to achieve Sprint Goals? 2. What we will do today to achieve Sprint Goals? 3. Do we have impediments that are stopping us to achieve Sprint Goals?
22. Sprint Review helps us to validate that team achieved goals Ø Sprint Review meetings helps team to validate their solution for product increment and to get feedback on product
23. Team should stop for moment and reflect on previous sprint Ø Retrospective helps us to reflect on last Sprint and to see how we can improve
24. 5. How to fu*k up your SCRUM?
25. There are least 10 ways to destroy it 1. Bad Scrum Master 2. Definition of Done in not defined 3. Velocity is important more then delivery 4. Retrospective 5. Team Commitment 6. Technical debt 7. Working alone not in the team 8. Not defined product backlog and not empowered product owner 9. Sprint Backlog and Sprint Goals are not defined 10.Mergophobia Source: https://www.crisp.se/file-uploads/10-ways-to-screw-up-with-Scrum-and-XP.pdf
26. 6. Wrap up
27. Who am I? Ognjen Pejovic - https://www.agilizing.us/author/ognjen/ Currently in role of SCRUM master Helping and coaching 4 international team in Scrum Framework Facebook: https://www.facebook.com/peja890 Linkedin: https://de.linkedin.com/in/ognjenpejovic Twitter: https://twitter.com/Pejinac