confidential · scrum in 100 words scrum is an agile process that allows us to focus on delivering...
TRANSCRIPT
1
Confidential
2
Confidential
2
Introduction to Scrum
Oleksandra SkybinaAndrii Kulshan
3
Confidential
https://www.youtube.com/watch?v=RRy_73ivcms
4
Confidential
Waterfall vs Agile
5
Confidential
Values
Individuals and Interactions Over Processes and Tools. …
Working Software Over Comprehensive Documentation. …
Customer Collaboration Over Contract Negotiation. …
Responding to Change Over Following a Plan.
6
Confidential
Scrum in 100 Words
Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time
It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month)
The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features
Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint
7
Confidential
Scrum Characteristics
Self-organizing teams
Product progresses in a series of month-long “sprints”
Requirements are captured as items in a list of “product backlog”
No specific engineering practices prescribed
Uses generative rules to create an agile environment for delivering projects
One of the “agile processes”
8
Confidential
Plan sprint durations around how long you can commit to keeping change out of the
sprint
9
Confidential
ROLES
• Sprint planning• Sprint review• Sprint retrospective• Daily Scrum meetings• +Backlog refinement
CEREMONIES
• Product backlog• Sprint backlog• Sprint goal• Burndown chart
ARTIFACTS
Scrum Framework
• Product Owner• Scrum Master• Development Team
10
Confidential
ROLES
Product Owner
Scrum Master
Development Team
11
Confidential
▪ Overall project vision and goals
▪ Create user stories following Definition of Ready criteria
▪ Prioritize backlog items▪ Participates in Sprint
Planning and Sprint Review
Work on Backlog
▪ Determines Release plan▪ Accepts delivered work and
provides feedback▪ Managing project ROI vs Risks▪ Taking all inputs into what the
team should produce▪ Communicates with customer
Release vs Profitability
Product Owner
Jenson Button
12
Confidential
⮚ The ScrumMaster protects the team from anything that threatens its effectiveness, such as outside interference or disruption
⮚ The ScrumMaster will need to confront uncomfortable issues, both inside and outside the team
Protect
Scrum Master
⮚ The ScrumMaster takes action to help remove impediments to the team’s effectiveness
⮚ The ScrumMaster facilitates the team’s group interactions, to help the team achieve its full potential
⮚ The ScrumMaster coaches the team, to help them improve their practices and effectiveness
Serve
The ScrumMaster ensures that all standard Scrum rules and practices are followed
13
Confidential
• Typically 5-9 people• Full time (with some
exceptions)• No switches between
sprints
Size
• Programmers• Testers• Designers• …
Cross Functional
Development Team
• Self organized• Give the commitments• Tasks based on skills,
not just official “role”
Self management
14
Confidential
CEREMONIES
Sprint Planning
Sprint Review
Sprint Retrospective
Daily Standup
+Backlog refinement
15
Confidential
Sprint ReviewWhat has been accomplished in the
sprint that determines velocity
Daily Scrum15 minutes about 3 questions
Self-organize to improve
performance
Sprint PlanningProduct Backlog must be ready
before this meeting
RetrospectiveIdentify the top process
improvement and put in the backlog
for the next sprint
+ Backlog RefinementReview of Product Backlog Items –
ensure they are Sprint-READY!
16
Confidential16
Task Brakeout
Team selects starting at top as much as it
can commit to deliver by the end of Sprint
Ranked list of what is
required:Features, stories, ...
Finished workSprint end date and
team deliverabledo not change
Product OwnerThe Team
ScrumMaster
Sprint Planning Meeting
Daily ScrumMeeting
Sprint Review
SprintRetrospective
Sprint1-4 weeks
Standupdaily
The Basics of Scrum
+Backlog Refinement
17
Confidential
ARTIFACTS
Product Backlog
Sprint Goal
Sprint Backlog
Burndown Chart
18
Confidential
Product Backlog
Requirements
A list of all desired work on the project
Ideally expressed such that each item has value to the users or customers of the product
Prioritized by the product owner
Reprioritized at the start of each sprint
19
Confidential
Adding Visa/MC payment
methods
Sprint Goal
Possibility to add desired
delivery time
Iteration 7 Iteration 8
Improve usability of email
sending configuration
Iteration 9
The way you describe your work to the boss of your boss
20
Confidential
Sprint Goal
21
Confidential
Sprint Backlog
Best guess of what’s left and how long will it take
22
Confidential
Burndown Chart Cases
23
Confidential
Story Points Estimation
SIZE = Effort x Complexity x Uncertainty
24
Confidential
Planning Poker
25
Confidential
Velocity
Estimation in Scrum is based on what’s called velocity.
Velocity is measure of how much product backlog the team
can complete in a given amount of time.
26
Confidential
Velocity
27
Confidential
27
Task Brakeout
Team selects starting at top as much as it
can commit to deliver by the end of Sprint
Ranked list of what is
required:Features, stories, ...
Finished workSprint end date and
team deliverabledo not change
Product OwnerThe Team
ScrumMaster
Sprint Planning Meeting
Daily ScrumMeeting
Sprint Review
SprintRetrospective
Sprint1-4 weeks
Standupdaily
The Basics of Scrum
+Backlog Refinement
That is how Scrum suppose to work. Easy, right? At least this is the theory, we know reality is usually much more difficult.
Summary
28
Confidential
To Read
● Scrum Guide https://www.scrum.org/resources/scrum-guide
● Scrum Alliance https://www.scrumalliance.org/learn-about-scrum/scrum-elearning-series
● Lean Agile https://leankit.com/learn/lean/lean-agile/
29
Confidential
Thank you