Introduction to Scrum
•Télécharger en tant que PPTX, PDF•
1 j'aime•254 vues
Scrum presentation designed to give readers basic understanding of Scrum's principles. Any copyrighted materials referenced in this document is for educational purposes only and protected under fair use.
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Introduction to Scrum
Similaire à Introduction to Scrum (20)
Dernier
Dernier (14)
Introduction to Scrum
- 1. Scrum 101 Brownbag: Introduction to Scrum Latesha Goodman August 9, 2019 This presentation is for educational purposes only. Any copyrighted material used herein this presentation is fair use.
- 2. About Me • My name is Latesha Goodman, I am certified consultant with more than six years of experience supporting IT projects. • After working on numerous government projects, I decided to pursue a certification in Agile. • In May, I earned my Certified Scrum Master (CSM) certificate--which brings us to today’s brown bag. • The following sections will give you a basic understanding of Scrum’s principles and hopefully inspire you to learn more. • Connect with me on LinkedIn: https://www.linkedin.com/in/lateshaagoodman/
- 3. Scrum's History Scrum Framework Scrum Values Scrum Team Scrum Ceremonies Scrum Artifacts Agenda
- 4. Scrum's History 1986 Hirotaka Takeuchi and Ikujiro Nonaka introduced the term Scrum in their HBR article, “New New Product Development Game”. 1993 Jeff Sutherland introduced Scrum at his job Easel Corporation using the study by Takeuchi and Nonaka. 1995 Jeff Sutherland and Ken Schwaber jointly presented Scrum as a formal process at the OOPSLA. 2001 Sutherland, Schwaber, and other scrum thinkers joined forces to create the Agile Manifesto. 2010 Sutherland and Schwaber published the Scrum Guide.
- 5. Scrum's Relationship to Agile Figure 1
- 6. Scrum Values Three Pillars of Empiricism 1. Transparency 2. Inspection 3. Adaptation 1. Courage 2. Focus 3. Commitment4. Respect 5. Openness Scrum Figure 2 Figure 3
- 8. Scrum Roles Scrum Events Scrum Artifacts and Tools Scrum Framework: Breakdown
- 9. Scrum Framework: Scrum Team Figure 5
- 10. Scrum Team: Product Owner Responsibilities include - One person, not a committee. - Creating ordered list for the Product Backlog. - Ensuring that the Product Backlog shows what the Scrum Team will work on next. - Determining Release Dates.
- 11. Scrum Team: Development Team Responsibilities include - Self-organizing into a team of 3-7 professionals. - Turning Product Backlog into Increments. - Delivering a potentially releasable Increment of "Done" product at the end of each Sprint.
- 12. Scrum Team: Scrum Master Responsibilities include - Servant leader for the Scrum Team. - Finding techniques for effective Product Backlog management. - Facilitating Scrum events as requested or needed.
- 13. Scrum Framework: Sprint Events Figure 6
- 14. Sprint Planning and Daily Scrums SprintPlanning •Scrum Team meets to discuss the work to be done in a Sprint. •Crafts a Sprint Goal to be met during the Sprint. •Time-boxed to a maximum of eight (8) hours for a one-month Sprint or 2 hours/week. DailyScrums •Development Team meets daily to inspect progress toward Sprint Goal. •Development Team plans work for the next 24 hours. •Daily Scrums are 15- minute time-boxed events.
- 16. Sprint Review and Sprint Retrospective SprintReview • Scrum Team and key stakeholders collaborate about what was done in the Sprint. • Event held at the end of the Sprint. • Maximum four (4) hour meeting for one-month Sprints. SprintRetrospective • Occurs after the Sprint Review and prior to the next Sprint Planning. • Allows team to inspect itself and make actionable commitments. • Maximum three (3) hour meeting for one-month Sprints.
- 18. Product Backlog and Sprint Backlog ProductBacklog Lists the features, functions, requirements, enhancements, and fixes to be made in future releases. It is dynamic and constantly changing as the product changes. Prioritized by the Product Owner. SprintBacklog Contains a set of Product Backlog items selected for the Sprint and a plan for delivering the product Increment and achieving the Sprint Goal. Only Development Team can change its Sprint Backlog during a Sprint.
- 19. Figure 9 Velocity in Scrum
- 20. Figure 10 Scrum Board (Post-It Notes)
- 21. Figure 11 Scrum Board (Atlassian Jira)
- 22. Figure 12 Sprint Burndown Chart
- 23. Increment Previous Sprints Increments Completed PBIs (Current Sprint) New Increment “Done” (Usable Condition)
- 25. Scrum Resources Books, Blogs, Games, and Tools • 12 Agile Manifesto Principles – Website • Agile: An Umbrella View (Blog Post) (Fig. 1) • Agile in an Hour Bernie Maloney – Presentation • Agile NOVA Meetup • Scrum.org and Scrum Co- Founder Ken Schwaber (Fig.4 and Fig.7) • Scrum Games - TastyCupcakes • Scrum PM Tools • Atlassian Jira (Fig. 11) • Asana (Free Tool) • GitScrum • Mountain Goat Tools (Fig 10 and Fig. 12) • Rally • Taiga • Art of Doing Twice the Work in Half the Time (Book) • Essential Scrum (Book) • PowerPoint History Template (Slide 4) • Planning Poker (Game) • Scrum Alliance Website • Scrum Guides – Website • Scrum Inc. – Scrum Co-Founder Jeff Sutherland (Fig.9) • The Scrum Fieldbook (Book) • Scrum Master Toolbox Podcast • Visual Paradigm (Blog Post) • Washington DC Scrum User Group Meetup Scrum Resources
Notes de l'éditeur
- LG Presenter Notes Show this slide during attendance call, so viewers can learn a little about me.
- LG Presenter Notes Show this slide during attendance call, so viewers can see what this brown bag covers up front.
- LG Presenter Notes 1 - 1986 - Scrum has been around for more than 30 years, the first appeared in Hirotaka Takeuchi and Ikujiro Nonaka’s Harvard Business Review’s article. 2 - 1993 - In his book, the “Art of Doing Twice the Work in Half the Time” Jeff Sutherland discussed using Takeuchi and Nonaka scrum principles to implement Scrum practices at his job. 3 -1995 - This led to Sutherland and Ken Schwaber collaborating to present Scrum as a formal process for software development at Object-oriented Programming, Systems, Languages, and Applications research conference. 4 - 2001 – Sutherland and Schwaber along with other Scrum practitioners developed the Agile Manifesto.
- LG Presenter Notes 1 – Scrum falls under the Agile umbrella it is not synonymous with Agile. As you can see Scrum is just one of many ways for a team be agile. Agile uses incremental, iterative work sequences that are known as sprints. Sprints allows teams to continuously align a delivered product that reflects the changing requirements needs of a client. 2 – Waterfall vs Agile Approach Requirements (Documentation Heavy)->Design (Documentation Heavy)->Implementation (Unverified Code)->Verification (Testing/Product Ready SW)->Production (Fully Deployed SW)
- LG Presenter Notes: 1a - Scrum Values - Scrum is framework that is built on the five values shown in Figure 2. 1b - Scrum Values Definitions Commitment: People personally commit to achieving the goals of the Scrum Team. Courage: Scrum Team members have the courage to do the right thing and work on tough problems. Focus: Everyone focuses on the work of the Sprint and the goals of the Scrum Team. Openness: The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work. Respect: Scrum Team members respect each other to be capable, independent people 2 – Empirical Process Scrum implements an empirical process where progress is based on unknowns and experimentation instead of upfront planning and knowns. “Learn as we grow approach” The three pillars of empiricism is shown in Figure 3.
- LG Presenter Notes 1 – Figure 4 shows the Scrum is a framework that uses cross-functional teams to address complex adaptive problems, while productively and creatively delivering products of the highest possible value. (Reference: The Scrum Guide) Bottom Line: The business / customer sees real progress and makes decisions based on working software. There are no paper reports, updated Gantt charts, or PowerPoints. And, the Development Team does not waste time building features the customer in the end does not want (anymore). 2 – Sprint Duration A Sprint is a time-box of month or less during which a potentially releasable product Increment is created. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. Excluding any of these events results in reduced transparency and is a lost formal opportunity to inspect and adapt.
- LG Presenter Notes 1 – The following sections explains Scrum’s roles, events and artifacts in more detail.
- LG Presenter Notes 1 - Scrum framework in Figure 5 consists of the following roles: Scrum Master Product Owner Development Team 2 - The following slides provide the responsibilities for each role. Reader note - Orange represents the Scrum Team in Figure 5.
- LG Presenter Notes As a Product Owner: You ensure the Product Backlog is visible, transparent, and clear to all. Represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner. Funnel all work requests intended for Dev. Team into the ordered Product Backlog by making trade-offs between various items. Explain what has been “Done” and what has not been “Done” during Sprint Review meeting. Use the Velocity and the Burndown Chart to view Team’s progress toward a successful sprint release. You can cancel the Sprint. Reader Note – Orange represents scrum team in the Scrum Framework.
- LG Presenter Notes As the Development Team You provide estimates for delivering a “Done” product. You use the Scrum Board tool to make the tasks on the Sprint Backlog visible for all team members.
- LG Presenter Notes As a Scrum Master Helping everyone understand Scrum theory, practices, rules, and values. Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value;
- LG Presenter Notes Figure 6 shows the formal events designed to enable transparency and inspection: 1 – Scrum Events (Ceremonies) Sprint Planning Daily Scrums Sprint Review Sprint Retrospective 2 – These four Scrum events create regularity and reduce the need for meetings not defined in Scrum. Reader Note - Gray represents the following Scrum Events (Ceremonies) in in Figure 6.
- LG Presenter Notes During a Sprint Planning the Scrum Team answers the following questions: What can be delivered in the Increment resulting from the upcoming Sprint? How will the work needed to deliver the Increment be achieved? When will the work be done? A Sprint Goal is an output of Sprint Planning: Dev. Team determines what can be done this Sprint. Product Owner discusses the objective the Sprint should achieve, this is called a Sprint Goal. Daily Scrums: Dev. Team uses Daily Scrums to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog. Dev. Team can use the following questions to structure the Daily Scrum: What did I do yesterday that helped the Dev. Team meet the Sprint Goal? What will I do today to help the Dev. Team meet the Sprint Goal? Do I see any impediment that prevents me or the Dev. Team from meeting the Sprint Goal?
- LG Presenter Notes Retrospective Commitments: Scrum Team talks about what it is currently doing that works well, and solicit some ideas about what it should be doing more or less of.
- LG Presenter Notes During a Sprint Review: Product Owner explains what has been “Done” and what has not been “Done” during Sprint Review meeting. Dev. Team demonstrates the work that it has been “Done” and answers stakeholders questions about the Increment. The entire group including key stakeholders discuss what to do next, so that the Sprint Review provides valuable input into subsequent Sprint Planning. The output of the Sprint Review is a revised Product Backlog. During a Sprint Retrospective: Offers Scrum Team opportunity to inspect how the last Sprint went with regards to people, relationships, process and tools.
- LG Presenter Notes – Purple represents Scrum Artifacts in Figure 7. Figure 8 provides the three Artifacts in Scrum. Product Backlog: List of sponsor’s requirements prioritized by Product Owner. Sprint Backlog: Contains what the Development Team will be completing during the Sprint. Increment (Most Viable Product): Releasable product, feature, code delivered at the end of Sprint.
- LG Presenter Notes 1 - Product Owner is responsible for refining (or grooming) the Product Backlog. Product Backlog Refinement is the act of adding detail, estimates, and order to items in the Product Backlog. 2 - Sprint Backlog contains: What the Development Team will be completing during the sprint. It includes at least one (1) high priority process improvement identified in the previous Retrospective meeting 3 – Figure 9 Illustrates how the Product Backlog and Sprint Backlog are ordered during a typical Sprint. Reader Note: Purple represents scrum artifacts in Scrum Framework.
- LG Presenter Notes 1 – What is Velocity in Scrum? Velocity is calculated at the end of the Sprint by totaling the Points for all fully completed User Stories. Points from partially-completed or incomplete stories are not counted in calculating velocity. Velocity is a measure of the amount of work a Scrum Team can tackle during a single Sprint. 2 – How does the Dev. Team know its Velocity? The Development creates estimates for every item in the Sprint Backlog. Common estimating methods include numeric sizing (1 through 10), t-shirt sizes (XS, S, M, L, XL, XXL, XXXL) or the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, 34, etc.). 2a – Why is Velocity Important? The Development Team uses velocity from previous sprints to estimate how much work it can tackle in future sprints. 2b – Velocity helps Product Owner with Ordering Product Backlog Items Higher ordered Product Backlog items are usually clearer and more detailed than lower ordered ones. More precise estimates are made based on the greater clarity and increased detail; the lower the order, the less detail.
- LG Presenter Notes 1 – What is a Scrum Board? The Sprint Board is a visual tool used to manage the Sprint Backlog and is visible to all team members at all times. The Scrum Board is what is going on in this particular sprint, with user stories broken down into smaller, technical, descriptions for the team to work on. The Development Team uses a Scrum Board to show the items that need to be completed for the current Sprint. 2 – Types of Scrum Boards As you can see from a quick Google Search, Scrum Boards come in many forms and include various categories. However, the traditional scrum include: To-Do column, Work in Progress column, and Done column.
- LG Presenter Notes 1- Jira and other Agile Tools Figure 10 illustrates a Scrum Board using Jira. 2 – I provide a list of Agile tools on Slide 24.
- LG Presenter Notes In addition to Scrum Boards, the Development Team uses a Sprint Burndown Chart to show the team’s progress in completing work during the sprint. 1 – How to use Sprint Burndown Chart? In the Daily Scrum the Development Team updates the Sprint Burndown Chart and plots the remaining work of the day. The Product Owner uses the Sprint Burndown Chart for release planning and reporting.
- LG Presenter Notes – Purple represents Scrum Artifacts in Scrum Framework. Previous Sprints Increments: Each Increment is additive to all prior Increments and thoroughly tested, ensuring that all Increments work together. Increment (Most Viable Product): The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of "Done". If the definition of "Done" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. If "Done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of "Done" appropriate for the product. If there are multiple Scrum Teams working on the system or product release, the Development Teams on all the Scrum Teams must mutually define the definition of "Done".
- LG Presenter Notes: Ask peers if they have any questions, if not then do a pop quiz to ensure they understand the material.
- LG Presenter Notes: There are various Agile tools to assist the Scrum Team with conducting Sprints including Atlassian Jira https://www.atlassian.com/agile/tutorials/sprints Dev. Teams use Planning Poker / Scrum Poker during the estimation process https://www.scrum-institute.org/Effort_Estimations_Planning_Poker.php