Introduction to agile and Scrum
5 likes1,183 views
The document provides an introduction to Agile and Scrum, outlining key concepts such as Agile principles, Scrum roles, and planning stages like user stories and backlogs. It explains the structure and functions of Scrum teams, including the roles of the Product Owner, Scrum Master, and Development Team, as well as essential practices like daily stand-ups and retrospectives. The document emphasizes iterative development, team collaboration, and measuring progress using metrics like velocity to achieve continuous improvement.
Introduction to agile and Scrum
- 1. INTRODUCTION TO AGILE & SCRUM
- 2. What will we cover? • What is agile? • What is Scrum? • Roles • User Stories • Product Backlog and Sprint Backlog • Sizing • Planning • Sprints • Meetings • Calculating velocity
- 3. Agile • What is agile? • Agile promotes certain concepts and principles; it does not give a prescriptive set of processes • It is based on iterative and incremental development (‘iterations’ or ‘sprints’)
- 4. The Agile Manifesto “While there is value in the items on the right, we value the items on the left more.” The agile manifesto
- 5. Scrum • What is Scrum? • ‘Scrum’ is one approach that applies agile principles • A framework; not a full methodology • Relies on a self-organising team (because the team knows best how to solve the problems they face) ! • Other agile approaches include Extreme Programming (XP)
- 7. The Game Simulates how teams use Scrum
- 8. Scrum Roles Scrum uses a number of specific (and odd sounding) roles. They are: ! 1. Product Owner 2. The Development Team 3. Scrum Master
- 9. Product Owner • The Product Owner is one person • Owns the Product Backlog • Decides on the priority of the backlog based on knowledge of business value • Provides support to the Team and answers any questions relating to requirements ! We will play this role
- 10. The Team • Typically 5-9 people • Agree, as a team, to the work taken on for each Sprint • Satisfy requirements as a team; not as individuals • Everyone is responsible for quality ! You will play this role Everyone involved in creating the product (e.g. developers, testers, UX)
- 11. Scrum Master • Servant leader; not decision-maker • Removes impediments for the team • Acts as a process coach & helps the team improve use of agile/ Scrum • Facilitates the meetings • Leads and coaches the organisation in the adoption of Scrum We will play this role
- 12. Planning stage: “user stories” • PO produces requirements for the project • Requirements written by PO (often with help of analyst) • A short, simple description of a feature using everyday language • Told from the perspective of the person who desires the new capability • Supported by ‘Conditions of Satisfaction’ Popular format: As a <who> I want <what> So that <why>
- 13. Planning stage: “product backlog” • The PO prioritises the user stories in order of value to the business • This is the ‘Product Backlog’ ! • Read through the requirements • Your PO will answer any questions relating to requirements
- 14. Planning stage: “sizing” • Teams plan each Sprint by taking the highest priority items from the Product Backlog • We estimate the ‘size’ of each story and agree how much can be undertaken in the allocated time of the Sprint • However, we are not good at estimating in time; we are better at relative comparison ! … which is why we use story points
- 15. • Discuss the story • Size effort relative to other stories • Must include all coding and testing to consider it ‘Done’ • Use points to describe size: 1, 2, 3, 5, 8, 13, 20, 40 • Each person chooses a size, but everyone declares together • Discuss until consensus reached Planning stage: “sizing”
- 16. Planning stage: “sizing” As a team: • Choose a small story • Assign the small story 2 points • Then assign a number to each story relative to this small story ( and relative to all other stories you subsequently size) ! 1, 2, 3, 5, 8, 13, 20, 40
- 17. Planning stage: “sizing” • The PO then reviews your estimates • This gives the PO more information to allow him/her to: – Leave it as it was – De-prioritise the story – De-scope the story • Does your PO want to change the order? • As a team, decide how many of the stories you can complete in a single Sprint of 3 minutes • You now have your “Sprint Backlog”
- 18. Sprint 1 • Let's get ready to complete some of these tasks • You know which stories you are doing • And you know the order you are doing them in But hang on! How do you track progress? How do you know which stories have been completed?
- 19. Agile boards • Method of managing progress during an Sprint • Team members move cards from left to right as each stage is completed • Columns vary by team • Basic columns are: • Not started / To do • In progress • Done
- 20. Sprint 1 • Create a board with 3 columns: – To Do – In progress – Done • Put the stories from your Sprint Backlog in the ‘To Do’ column • Then you are ready to go! • You have 3 minutes to complete as many of the stories as possible … we will stop half way through to evaluate progress
- 21. Daily Stand-Up (aka the Daily Scrum) • Approx. 15 mins each day • Each person confirms: What I did yesterday What I will do today Any impediments that I have ! • Don’t talk too much! • Meeting is not for solving issues; discuss specific details afterwards Team, Scrum Master (& sometimes PO)
- 22. Velocity • How many stories did you complete in full? • How can this information help you plan future work? Velocity • Estimated you could do X points • Actually, you implemented Y points • Use past performance as a guide to decide how many stories to bring into future Sprints Velocity = average points previously completed
- 23. Showcase • Allows team to show what they have produced to the PO, stakeholders, and any other interested parties • A chance to see new functionality, ask questions and give feedback • Demonstration; not training session Team, PO, Scrum Master, stakeholders + anyone else
- 24. Retrospective • How well did the team work in the last Sprint? • Basic retrospective asks: • What did we do well? • What could we have done better? • How can we improve? • Not for discussing work done during the sprint or individual performances • Everyone has a voice Team, PO, Scrum Master
- 25. Sprint 2: planning • Read through the next set of user stories • Order them by effort (with any remaining stories) • Size each story (based on previous estimates) • Based on your ‘velocity’ what can you complete as a team? • Does the PO want to alter priorities? • Put your stories in ‘To Do’ on your board ! • GO!
- 26. Daily Stand-Up (aka the Daily Scrum) • Approx. 15 mins each day • Each person confirms: What I did yesterday What I will do today Any impediments that I have ! • Don’t talk too much! • Meeting is not for solving issues; discuss specific details afterwards Team, Scrum Master (& sometimes PO)
- 27. Velocity • How many stories did you complete in full? • How can this information help you plan future work? Velocity • Estimated you could do X points • Actually, you implemented Y points • Use past performance as a guide to decide how many stories to bring into future Sprints Velocity = average points previously completed
- 28. Showcase • Allows team to show what they have produced to the PO, stakeholders, and any other interested parties • A chance to see new functionality, ask questions and give feedback • Demonstration; not training session Team, PO, Scrum Master, stakeholders + anyone else
- 29. Retrospective • How well did the team work in the last Sprint? • Basic retrospective asks: • What did we do well? • What could we have done better? • How can we improve? • Not for discussing work done during the sprint or individual performances • Everyone has a voice Team, PO, Scrum Master
- 30. Sprint 3: planning • Read through the next set of user stories • Order them by effort (with any remaining stories) • Size each story (based on previous estimates) • Based on your ‘velocity’ what can you complete as a team? • Does the PO want to alter priorities? • Put your stories in ‘To Do’ on your board ! • GO!
- 31. Daily Stand-Up (aka the Daily Scrum) • Approx. 15 mins each day • Each person confirms: What I did yesterday What I will do today Any impediments that I have ! • Don’t talk too much! • Meeting is not for solving issues; discuss specific details afterwards Team, Scrum Master (& sometimes PO)
- 32. Velocity • How many stories did you complete in full? • How can this information help you plan future work? Velocity • Estimated you could do X points • Actually, you implemented Y points • Use past performance as a guide to decide how many stories to bring into future Sprints Velocity = average points previously completed
- 33. Showcase • Allows team to show what they have produced to the PO, stakeholders, and any other interested parties • A chance to see new functionality, ask questions and give feedback • Demonstration; not training session Team, PO, Scrum Master, stakeholders + anyone else
- 34. Retrospective • How well did the team work in the last Sprint? • Basic retrospective asks: What did we do well? What could we have done better? How can we improve? • Not for discussing work done during the sprint or individual performances • Everyone has a voice Team, PO, Scrum Master
- 35. So what have we learned? • Agile and the Agile Manifesto • The benefits of agile • Scrum is a framework that uses agile principles • Scrum roles (Product Owner, Scrum Master) • How to build & organise a Product Backlog • User stories • Sizing, Planning Poker & calculating velocity • How to build a Sprint Backlog • Agile boards • How to work in Sprints • Meetings (Stand-up,Sprint Review, Retrospective)
- 36. AOB and Questions What I wish I had time to mention: • Definition of Done • Sprint Goal • Burndown chart ! For further information: scrumandkanban.co.uk Meetups (e.g. London Agile Discussion Group)