Pecha kucha Scrum at a Glance agile tour Lebanon 2014
•Télécharger en tant que PPTX, PDF•
1 j'aime•741 vues
This is a Pecha Kucha presentation (20 slides 20 seconds each slide) I made in Agile Tour Lebanon 2014 about Scrum: How it started, the framework, the roles, the artifacts and the events
Recommandé
Contenu connexe
En vedette
En vedette (19)
Dernier
Dernier (20)
Pecha kucha Scrum at a Glance agile tour Lebanon 2014
- 1. SCRUM AT A GLANCE Joanna Khoury
- 2. Prepared by Joanna Khoury Joanna@scrumarabia.com all rights reserved (c)
- 3. Prepared by Joanna Khoury Joanna@scrumarabia.com all rights reserved (c)
- 4. What They Observed Requirements Design Code Test Rather than doing one thing at a time... Project Timeline Project Timeline ...Scrum teams do a little of everything all the time.
- 5. Waterfall and Scrum Plan Review Execute Manage Change Traditional planning steps Plan Execute Learn Plan Execute Learn Expect and Embrace Change Scrum planning steps
- 6. 1996: a software version of Scrum was introduced Ken Schwaber Jeff Sutherland Prepared by Joanna Khoury Joanna@scrumarabia.com all rights reserved (c)
- 7. The Scrum Framework Roles Artifacts Events Prepared by Joanna Khoury Joanna@scrumarabia.com all rights reserved (c)
- 8. Prepared by Joanna Khoury Joanna@scrumarabia.com all rights reserved (c) Coach = PO Referee = SM The Players = The team
- 9. Roles •Product Owner Client Proxy Prepared by Joanna Khoury Joanna@scrumarabia.com all rights reserved (c)
- 10. Roles •SrumMaster Servant Leader Prepared by Joanna Khoury Joanna@scrumarabia.com all rights reserved (c)
- 11. Roles Problem Solver • The Team Prepared by Joanna Khoury Joanna@scrumarabia.com all rights reserved (c)
- 12. Artifacts • The Backlog High-priority Items Release 1 Release 2 Release 3 Low-priority Items Prepared by Joanna Khoury Joanna@scrumarabia.com all rights reserved (c)
- 13. Artifacts •Scrum Board. Stories Tasks In Progress Completed Prepared by Joanna Khoury Joanna@scrumarabia.com all rights reserved (c)
- 15. Artifacts • Burn Down Chart
- 16. Events • The Sprint Daily Stand up SPRINT Prepared by Joanna Khoury Joanna@scrumarabia.com all rights reserved (c)
- 17. Events • Sprint Planning Prepared by Joanna Khoury Joanna@scrumarabia.com all rights reserved (c)
- 18. Events • The Review Prepared by Joanna Khoury Joanna@scrumarabia.com all rights reserved (c)
- 19. Events • The Retrospective Prepared by JoannKhoury Joanna@scrumarabia.com all rights reserved (c)
- 20. So….The Scrum Framework is…
Notes de l'éditeur
- My name is Joanna from Scrum Arabia, I am a management consultant, a scrum coach and a customer service improver. In the next 6 minutes I am going to Introduce Scrum to you
- You all know Rugby or American football/ Scrum is the moment of the game where all the team members come together to get the ball. Well… it is not this Scrum that we are going to discuss.
- It all started in Japan/ in 1986 / when 2 university teachers /Tkeuchi and Nonaka / Did a research /on why some companies /are doing better than others /when it comes to responding to market demand.
- While in some companies/ people gather the requirements first / when all the requirements are ready they start the design / when the full design document is ready they start coding/ and when all the code is written they start testing// scrum teams do a little bit of everything in the same time.
- In Traditional planning steps / change is only welcomed at the end. Change at the end is very expensive and difficult to implement. In Scrum / All the team is working together instead of passing on tasks / Work is divided into iterations/ we pose and learn at the end of each iteration (inspection and adapt) Most importantly change is welcomed throughout the project / Which makes change much less expensive and easy to integrate.
- In 1996, a software project version of SCRUM was introduced by Ken Schwaber and Jeff Sutherland. In 2001 Scrum start to be widely used in the IT and software industry after Ken Schwaber wrote a book called “Agile software development with Scrum” Now a lot of companies across the world use Scrum, I can name Microsoft, Oracle, Google, IBM, amazone, and lot
- The Scrum framework is very simple it has roles artifacts and events
- We have 3 roles, Product Owner, Team and Scrummaster If we are in a rugby or soccer game, the coach set the strategy (this is our Product Owner), the Referee makes sure the game is played according to the rules (this is the scrummaster) and the team do the actual work and plays the game (this is the scrum team)
- Represent the Client Decide what to build Prepare the backlog Create Value!!!
- Make sure Scrum process runs properly Keep the team focus Resolve impediments THE Actual project manager role is divided between the PO and the SM
- Most important entity Do the work Typically 5-9 people, have all the skills to build the product. Have all the skills to create the product in one team. Programmers, designers, testers, user experience designers, etc. Teams are self-organizing and problem solving. Commits to tasks and build the work within a sprint.
- The first artifact is the Product backlog This is a list of all the work needed to be done for a given product or sometimes multiple products. It contains stories, features, buts, requirements… It is ordered by the product owner based on the business value. It is sized by the team Stories at the top should be already broken down and sized by the team to be ready for the next sprint planning . In the planning meeting the team commits to from the top of the list.
- In the second part of the planning the team prepare their task board. They divide stories into tasks needed to complete each story. This is what we call the Scrum board or the sprint backlog. During all the sprint the team will complete the stories on the task board to reach the sprint goal Task boards are updated daily by all the team members in the daily stand up meeting.
- Scrum boards are colorful fun and motivating.
- The last artifact is the Burn Down Chart. It is a powerful tool to discover if all items team committed to, will finish on time or not. We can see the vertical axis the the team commitment and on the horizontal axis the number of days in the sprint. A straight line is optimal Daily the team will decrease the work already accomplished, iif there is any delay, the actual line will be far from the optimal line and it will be clear if finishing all the committed work in a sprint is at risk.
- The main time boxed event in Scum is the Sprint itself it can go from 3 days to 1 month. During which the team will convert the backlog into a potentially shippable increment 0f features During this sprint there is a daily meeting called daily scrum or stand up meeting, it is time boxed to up to 15 minutes no matter what is the sprint length. During the standup meeting the team plan for the day and inspect and adapt to daily impediments.
- Scrum has not only specific roles, but also specific events, and all scrum events are time boxed. All start with a planning or what we call Sprint planning Where the team understand the vision from the PO discuss the product backlog, size and commit to stories to be done in the next sprint and set a sprint goal. Sprint planning can go up to 8 hours for a 1 month sprint
- The team will review the increment of work done during the sprint with the Product Owner, the Scrummaster the Client, the managers all stakeholders can be present. The client or product owner tries the product, it is a hands on meeting not a demo and accept or reject the the work done. It is an opportunity to meet the client and get their direct feedback on the product.
- After the Review, the team and the scrummaster will do a retrospective to see what went well in the sprint, What could be improved And what actions to take for the next sprint. The retrospective mainly focus on improving the process to get a DONE increment. Like the other scrum events, the retrospective is time boxed, by example for a 2 weeks sprint your retrospective should take up to 1 hour and a half.