The document provides an overview of Scrum basics and components. It introduces Scrum as an Agile framework and discusses its core elements - events like sprints, planning and reviews; roles like product owner and scrum master; and artifacts like product backlog and sprint backlog. It also covers related concepts like capacity, velocity and how Scrum compares to Agile approaches. The document concludes by suggesting resources to learn more about Scrum and offers coaching for teams to understand how to apply Scrum.

1. www.luxoft.com
Scrum Basics
Agile Practice

2. www.luxoft.com
Introduction
Svetlana Mukhina
ICAgile ICP, ICP-ATF, ICP-BVA, PSM I
Agile and Career Coach at Luxoft Agile Practice
Experience: 12+ years in IT, Project and department management,
Computer Linguistics, Technical Writing, Quality Assurance
Interests: Project management, Agile transformation, Career and
performance coaching, Psychology
Hobbies: Horse riding, music, poker, travelling
Linkedin: https://www.linkedin.com/in/svetlanamukhina

3. www.luxoft.com
Session Plan
 How Scrum relates to Agile?
 Can the team be Agile, but don’t practice Scrum?
 Scrum Structure
 Scrum Components
 Events: Sprint, PBR, Planning, Standup, Review, Retrospective;
 Roles: PO, SM, Development Team;
 Artifacts: Product backlog, Sprint backlog, Shippable increment;
 Metrics: Capacity and Velocity
 Top 3 questions about Scrum
 Way forward

4. www.luxoft.com
What is Agile?

5. www.luxoft.com
That is, while there is value in the items on the right, we value the items on the left more.
from ICAgile, Agile Team Facilitation

6. www.luxoft.com
from ICAgile, Agile Team Facilitation

7. www.luxoft.com
from ICAgile, Agile Team Facilitation

8. www.luxoft.com
from ICAgile, Agile Team Facilitation

9. www.luxoft.com
What is Scrum?

10. www.luxoft.com
Scrum Structure
Courage
Respect
Commitment
Openness
Focus

11. www.luxoft.com
Scrum Components
ARTIFACTS
EVENTS
ROLES
Sprint Pulse
Scrum Master
Product Owner
Development Team
Main PBR Local PBR Local PBR Local PBR Local PBR
Increment
Sprint BacklogProduct Backlog

12. www.luxoft.com
Scrum Team
Scrum Master
Product Owner Development Team
• Cross-functional and self-organizing
• No titles other than Developer
• No sub-teams
• Owns Daily Scrum
• Owns Sprint Backlog
• 7±2 in size
• Tracks the total work remaining every day
• Delivers useable increment each Sprint
• Maximizing the value of the product and the work of the Dev. team.
• Managing Product Backlog
• Is one person, not a committee
• Ordering Product Backlog Items
• Clearly expressing PBIs
• Ensure Development Team understands PBIs to the level needed
• Only person who can cancel the Sprint
• Owner of Product Backlog Refinement meetings
• Tracks the amount of work remaining at least every Sprint Review
• Understanding and practicing Agility
• Facilitating Scrum Events as needed
• Coaching Development Team
• Removing impediments
• Leading and coaching organization in Scrum adoption
• Causing change that increases productivity
• Helping stakeholders understand Scrum and empiricism
• Ensuring Scrum rules are followed
• Increases the transparency of the artifacts
• Helps PO in finding effective Product Backlog techniques

13. www.luxoft.com
Scrum Events
Main PBR Local PBR Local PBR Local PBR Local PBR
• is a time-box of one month or less
• has a goal.
• new Sprint starts after the conclusion of the previous one.
• is 15-minute time-boxed
• is held at the same time and place each day
• consists of 3 questions to inspect progress
toward the Sprint Goal
• Is the act of adding detail, estimates, and order to PBIs
• Scrum Team decides how and when refinement is done
• PBR usually consumes >10% of the capacity of Dev. team
• is done by the collaborative work of the entire Scrum Team.
• is time-boxed to a maximum of eight hours for a one-month Sprint.
• answers two questions:
• what can be delivered in the Increment?
• how will the work needed to deliver the Increment?
• Is held at the end of the Sprint to inspect the Done work
• All Scrum Team is present on Review
• Dev. team demonstrates “Done” User Stories to PO
• Occurs after the Review and prior to the next Planning
• Discuss what went well and what can be improved
• Create a plan for implementing improvement
Planning
Standup
Review
Sprint
PBR Retrospective

14. www.luxoft.com
Scrum Artifacts
Increment
Sprint Backlog
Product
Backlog
• is an ordered list of everything that might be needed in the product
• Is single source of requirements for any changes to be made to the product;
• is never complete. It evolves as the product and its environment evolves
• is dynamic - changes in business requirements, market conditions, or
technology may cause changes in it
• higher ordered PBI are usually clearer than lower ordered ones.
• is the set of PBI selected for the Sprint
• is plan for delivering the product Increment
• makes visible all of the work for the Sprint
• Dev. team modifies the Sprint Backlog throughout the Sprint
• as new work is required, the Dev. team adds it to Sprint
Backlog
• only Dev. team can change its Sprint Backlog during a Sprint.
• it belongs solely to the Dev. team.
• The Increment is the sum of all PBIs completed during a
Sprint and value of the increments of all previous Sprints.
• At the end of a Sprint, the new Increment must be “Done”
• Definition of Done document is used to create increment

15. www.luxoft.com
Capacity and Velocity
• Capacity – number of ideal hours available during next sprint
• Forecast
• Velocity – number of story point completed during previous sprint
• Experience
 Using velocity and capacity all together helps to align workload basing on the past experience and
future availability of development time, it make planning more accurate and results more expectable

16. www.luxoft.com
Top 3 Questions about Scrum
 Why do we need Scrum?
 Does Scrum work?
 Do you believe in Scrum?

17. www.luxoft.com

18. www.luxoft.com
Way Forward – Scrum Guide
Scrum Guide - http://www.scrumguides.org/scrum-guide.html

19. www.luxoft.com
Way Forward - Open Assessments
Open Assessments - https://www.scrum.org/Assessments/Open-Assessments

20. www.luxoft.com
Way Forward – Agile Training
Professional Scrum Master
• About - https://www.scrum.org/Courses/Professional-Scrum-Master
• How to apply:
• Luxoft - https://inthr.luxoft.com/IntHRWebApp/aspx_PTC/CreateRequestInternal.aspx?Course=SDP-033
• Non-Luxoft – email me smukhina@luxoft.com
ICAgile Agile Fundamentals
• About – https://icagile.com/icagile-certified-professional
• How to apply:
• Luxoft – https://inthr.luxoft.com/IntHRWebApp/aspx_PTC/CreateRequestInternal.aspx?Course=SDP-031
• Non-Luxoft – email me smukhina@luxoft.com

21. www.luxoft.com
Overview of Scrum for your Team
Invite Agile coach for 1 hour session
• Make sure your management and team don’t mind coaching
• Write me email smukhina@luxoft.com with the request