Scrum Training (One Day)
Download as PPTX, PDF•22 likes•16,316 views
The document provides an overview of Scrum and Agile methodologies, discussing key roles, ceremonies, and processes that support effective software development. It emphasizes the importance of a team-oriented approach with roles such as Product Owner and Scrum Master and outlines the iterative nature of sprints in managing tasks and requirements. Furthermore, it compares traditional project management methods, like Waterfall, to Agile practices, advocating for adaptability and continuous improvement in project execution.
Scrum Training (One Day)
- 2. Chris Daily Experiences across multiple industries focused in agile transformations and software development. Led teams in start- ups to Fortune 500 companies in executive-level positions. Tana Linback Background focused on the people and organizational culture that are the foundation of business and agility. Unique combination of work in software development and human resources leadership. © 2016 beLithe LLC 2
- 3. Agenda Agile Intro Scrum Foundation Element #1: Roles 01 03 04 ScrumTheory & Framework02 © 2016 beLithe LLC 3 Scrum Foundation Element #2: Product Backlog Scrum Foundation Element #3: The Sprint Starting aSprint Working ina Sprint Ending aSprint 05 06 07 08
- 4. What will you gain from this class? Exposure to real scrum and agile experiences Process knowledge scrum roles, ceremonies, artifacts Questions leaving with more questions than before class Starting the journey welcome to the agile journey © 2016 beLithe LLC 4
- 5. 02 Professional courtesy 01 Parking lot 03 Relax, have fun 04Class should add new rules as needed 05 Instructor is the class Scrum Master Scrum Class Team Rules © 2016 beLithe LLC 5
- 6. Waterfall A traditional approach to project management.
- 7. History of Waterfall Project Management Project management processes were developed based on step-by-step manufacturing models the United States military used during World War II. Waterfall process developed from highly structured physical environments where after- the-fact changes are prohibitively costly, if not impossible. PhotoCourtesyofflintgm100.com PhotoCourtesyofthwapschoolyard.com © 2016 beLithe LLC 7
- 8. But now we’re in the age of the knowledge worker.
- 10. Waterfall Project Stats Successful Challenged Failed 14% 57% 29% The Standish Group defines project success as on time, on budget, and with all planned features. They do not report how many projects are in their database but say that the results are from projects conducted from 2002 through 2010. - Mike Cohn, Mountain Goat Software on the CHAOS Manifesto 2012 Report © 2016 beLithe LLC 10
- 11. “Insanity: doing the same thing over and over and expecting different results.” - Albert Einstein
- 12. Snowbird, UT
- 13. Agile is a Mindset.... © 2016 beLithe LLC 13 Individuals and Interactions OVER PROCESS AND TOOLS Working Software OVER COMPREHENSIVE DOCUMENTATION Customer Collaboration OVER CONTRACT NEGOTIATION Responding to Change OVER FOLLOWING A PLAN
- 14. Agile TDD Kanba n XP RUP Crystal Scrum and a few more... © 2016 beLithe LLC 14 Agile is a Mindset.... ...With lots of tools, practices, and frameworks to help put that mindset into action
- 15. Intro to Scrum
- 16. More prescriptive / more rules to follow More adaptive / fewer rules to follow KanbanXPRUP Scrum 120 13 9 3 The Sweet Spot © 2016 beLithe LLC 16
- 17. Large Companies that use Scrum …and lots of local guys, too © 2016 beLithe LLC
- 18. Scrum Example Video © 2016 beLithe LLC 18
- 19. vv Definition of Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Scrum is Scrum isScrum is lightweight.simple to understand. difficult to master.
- 20. Learn as we go Plan for change Embrace Change Use, Inspect, Adapt Command and control Planning for what you expect to happen Enforcing the plan Using change control Scrum prefers to... overoveroverover Scrum Theory: Empirical vs. Theoretical © 2016 beLithe LLC 20
- 21. Sequential vs. Overlapping Work Requirements Design Code Test 4 weeks 4 weeks 4 weeks 4 weeks Time © 2016 beLithe LLC 21
- 22. Parts of the Scrum Framework Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage Roles Ceremonies Artifacts © 2016 beLithe LLC 22
- 23. Product Owner Scrum Master The Team Roles: The People © 2016 beLithe LLC 23
- 24. Ceremonies: The Meetings Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Release Planning (optional) © 2016 beLithe LLC 24 Create regularity Minimize the need for meetings not defined in Scrum Are timeboxed Designed to enable transparency and inspection
- 25. Artifacts: The Tangibles 1 2 3 Product Backlog Sprint Backlog Potentially Shippable Product Increment
- 26. Scrum Roles © 2016 beLithe LLC 26
- 27. Scrum Master
- 28. Scrum Master Servant leader Works daily with the Scrum team Member of the Scrum team Enabling (not accountability) role Change agent The Scrum Master is responsible for ensuring Scrum is understood and enacted while supporting the Team. Scrum Masters do this by acting as a coach, ensuring that the Scrum Team adheres to Scrum theory, practices, and rules. 28
- 29. Product Owner
- 30. Product Owner Creates shared vision Works daily with the Scrum team to clarify requirements Member of the Scrum team Decides what the project/product does and does not include Bridges gaps between customer, stakeholders, and the Scrum Team The single wringable neck, the PO is responsible for the project and driving product success. Represents and speaks for the business needs of the project by creating and sharing the vision of the product. © 2016 beLithe LLC 32
- 31. Product Owner’s Responsibilities Product Backlog Work with Team Develops product vision, strategy, and direction Takes responsibility for the product’s budget and profitability Gathers, prioritizes, and manages product requirements Owns the product backlog Conveys product needs to the team Works with the team on a daily basis to answer questions and make decisions Provides or has access to product expertise Accepts or rejects completed work during the sprint Sets short- and long-term goals for the product Decides on the release date for completed functionality © 2016 beLithe LLC 33
- 32. The Team
- 33. Scrum Team Key Feature #1 Self-OrganizingTraditional Self-organizing teams choose how to best accomplish their work, rather than being directed by others outside the team Team’s tasks and work being directed by a manager The team model in Scrum is designed to optimize flexibility, creativity, and productivity © 2016 beLithe LLC 36
- 34. Scrum Team Key Feature #2 Cross FunctionalTraditional Cross functional teams have all the competencies needed to accomplish the work without depending on others not part of the team Traditional teams are formed by function The team model in Scrum is designed to optimize flexibility, creativity, and productivity © 2016 beLithe LLC 37
- 35. Product Backlog
- 36. Product Backlog Backlog lists all of the work on a project Our “to do” List The Product Owner is responsible for the product backlog, including its content, availability, and priority ordering A product backlog is never complete and evolves along with the product and the environment in which it will be usedDelete an item Add an item © 2016 beLithe LLC 41
- 37. Product Backlog Higher ordered product backlog items: • clearer and more detailed than lower ordered ones • need to be of size and clarity so the team can consume them in one sprint Priority Product Backlog Items Worked on soon Not worked on soon Small size LOTS of details Large size Few details © 2016 beLithe LLC 42
- 38. Product Backlog Items The team determines how the backlog item will be achieved The team determines the complexity of each product backlog item As a team, we estimate the t-shirt size of this item as a small. Here are the steps we will take to implement this item... Product Backlog Item Backlog Order:Estimate : Description: As a hotel guest, I want to reserve a room online. 1 Small © 2016 beLithe LLC 44
- 39. Hotel Software System Product Backlog Product Backlog Item Complexity Allow a guest to reserve a room Small Allow a guest to cancel a reservation XS Allow a guest to change the date of a reservation Medium Allow a hotel manager to run revenue reports Medium Improve exception handling Largee © 2016 beLithe LLC 45
- 40. Product Backlog Grooming Product Backlog Item Backlog Order:Estimate: Description: As a hotel guest, I want to reserve a room online. 1 S Product Backlog Item Backlog Order:Estimate: Description: As a hotel manager, I want to view my revenue for the month. 2 S Product Backlog Item Backlog Order:Estimate: Description: As a hotel guest, I want to change the date of my current reservation. 3 L Grooming is an ongoing process in which the Product Owner and the team collaborate on the details of the product backlog Items, coming to a shared understanding of what is to be accomplished. No, this item means ab and c. We think this item means xy and z. ? © 2016 beLithe LLC 46
- 41. Product Backlog Grooming Product Owner must get stories to a consumable state Product Backlog is a living thing Stories going into the next sprint need to be sufficiently refined to be understood and sized by the team. If it can’t be sized, it’s not ready. The Product Backlog is constantly reprioritized. It is dynamic – always changing to identify what the product needs to be appropriate, competitive, and useful. If you remember nothing else, remember the following two key points: © 2016 beLithe LLC 48
- 42. The Sprint
- 43. Sprint Basics At the heart of Scrum is the Sprint Consistent iteration of time (timebox) where the team completes a specific group of tasks from start to finish. Timebox duration is consistent from sprint to sprint. Timeboxes vary from team to team between 2 to 4 weeks. Each Sprint can be thought of as a project. Like projects, Sprints are used to accomplish something. Each Sprint builds incrementally on the work of prior Sprints. © 2016 beLithe LLC 50
- 44. Elements of a Sprint Sprint Planning We plan the work.01 The Work We do the work.02 Daily Scrum We coordinate the work.03 13 2 We coordinate the work. We plan the work. Sprint Review & Retrospective We review the work. 04 We review the work. 4 © 2016 beLithe LLC 52 We do the work.
- 45. Changes During the Sprint Quality goals do not decrease 02 01 03 Scope may be clarified and renegotiated as more is learned No changes are made that would endanger the sprint goal © 2016 beLithe LLC 53
- 46. Starting a Sprint © 2016 beLithe LLC 54
- 47. Scrum Process
- 48. Overview: Starting a Sprint 1 2 3 4 Establish the goals for your sprint Choose the user stories that support those goals Break user stories into specific tasks Create a Sprint Backlog 04 Steps When planning a Sprint, you will: © 2016 beLithe LLC 56
- 49. Product Backlog The Artifact: Sprint Backlog Step 03 Completed and remaining work is updated daily. Step 02 Individuals sign up for work of their own choosing. Work is never assigned. . Step 01 Sprint backlog work is pulled from the product backlog in order of business value. Sprint Backlog Item 1 Item 2 Item 3 Item 4 In Progress © 2016 beLithe LLC 57
- 50. Sprint Backlog: Tasks Tasks in agile projects should take a day or less to complete for two reasons: 24hours People are motivated to get to the finish line. If you have a task that you know you can complete quickly, you are more likely to finish on time. One-day tasks can provide early red flags that a project might be veering off course. 1 2 © 2016 beLithe LLC 58
- 51. Working in a Sprint © 2016 beLithe LLC 60
- 52. Scrum Process
- 53. Doing the Work through the Sprint Backlog Scrum Master is responsible for the resolution of impediments Once a story starts, work should continue until the story meets the sprint definition of done The team wins and loses together Additional work for the sprint can emerge from existing stories in the sprint Any team member can add, delete, or change the sprint backlog © 2016 beLithe LLC 62
- 54. Daily Scrum
- 55. Daily Scrum Meeting The answers three questions What did you do yesterday? What will you do today? Is there anything in your way? © 2016 beLithe LLC 64
- 56. Daily Scrum Meeting aka “daily standup” or “daily huddle” Meeting must last 15 minutes or less Anyone may attend but only the team & Scrum Master may talk Focus on status of current work, priorities, and impediments Daily Scrum Meetings are for coordination, not problem solving © 2016 beLithe LLC 65
- 58. Scrum Process
- 59. Sprint Review
- 60. Sprint Review Entire team participates Show off product like a demo Maximum of one hour per week per sprint duration Informal, no slides Team presents what they accomplished during the sprint to the Product Owner Invite anyone and everyone who may be interested in the product Intended to elicit feedback and foster collaboration © 2016 beLithe LLC 69
- 62. Sprint Retrospective The answers three questions What actions do we need to take moving forward to fix #2? What didn’t go well? What did we do well? © 2016 beLithe LLC 71
- 63. The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next sprint 02 All Scrum team members participate except for Product Owner (unless asked to participate) 04 Done at the end of every sprint 01 The results should be inputs (stories) into the backlog 03 Sprint Retrospective © 2016 beLithe LLC 72
- 64. Retrospective Item to Review: Team Rules Team Rules These are the guidelines the team members agree to conduct themselves under in the Sprint as defined by the Scrum team. © 2016 beLithe LLC 73
- 65. Sprint Retrospective What should we continue to do in training? What should we change or stop doing? © 2016 beLithe LLC 74
- 66. Wrap-Up
- 67. Helpful Reference Material Sites & Organizations Scrum Alliance www.scrumalliance.org Scrum.org www.scrum.org Agile Alliance www.agilealliance.org Mountain Goat Software www.mountaingoatsoftware.com Leading Agile www.leadingagile.com beLithe www.beLithe.com Text Scrum: A Breathtakingly Brief and Agile Introduction Scrum: The Art of Doing Twice the Work in Half the Time Succeeding with Agile: Software development Using Scrum © 2016 beLithe LLC 76
- 68. Wrap Up Changing Methodologies Retrospective & Survey Staying in Touch © 2016 beLithe LLC 77
Editor's Notes
- #3: **Review statements
- #7: **Review Statement
- #19: ?
- #24: Three primary roles in Scrum, PO, SM and the Team.
- #29: Scrum Masters are the evangelists of Scrum to the team. Serves as facilitator of meetings and ceremonies and removes impediments from the team. More of a peer to peer relationship, not a reporting relationships. Impediment is something that gets in the way of someone on the team getting their job done. Up to the Scrum Master to attempt to resolve it. Typically impediments are process oriented and SM helps solve that. There may be a gap in processes. In daily standups, facilitating meetings, coaches the team on Scrum. Job is make sure the team has everything it needs to get its job done. That may be sheltering from external folks making requests so that the team can focus on the current sprint’s work. Full time role – full time initially and then as you get rolling you can add another team
- #30: External interferences - No increase in scope Pulling a teammate in part time to a project Facilitate Consensus – As a moderator will help the team reach compromises Make sure all voices get heard
- #31: Most important thing is a Servant Leader – her job is to make sure that everyone else can get their job done. Make sure not one person is dominating. Make sure people are pulling their weight – if not, have a conversation as necessary. Can consult with the resource manager.
- #33: The term “owner” used in the title was chosen for a reason. The Product owner should virtually “own” the product. The product vision is critical for success. Most people don’t want to just be told what to do. They want to understand what the journey is that they are undertaking.
- #50: **Review Statement