3. Scrum Process
Scrum is an Agile Process for running Software
Development Projects.
Uses an Empirical Process control model instead
of a Defined Process control model.
This means it depends on “Inspect and Adapt”
cycles, instead of phases, hand-offs, sign-offs,
and blame.
4. Scrum Process
These cycles require regular inspections of the
process and constant adaptations to steer the
direction of the process based on those
inspections.
Scrum is made up of two cycles:
The Monthly Scrum Sprint (“the Sprint”)
The Daily Scrum Meeting (“the Scrum”)
All activity takes place within these two cycles.
5. Scrum Process flow
Sprints should be protected from changes. This is
very important for team to have maintain focus within
the Sprint
6. Scrum team
Product owner defines product backlog,
prioritizes them and is responsible for validating
sprint outputs.
Scrum master enacts Scrum values and removes
impediments of the team.
Team is cross-functional consisting of members
with various skills and roles.
8. Scrum team
The Team consists of 5-9 people who will develop
the product.
During each Sprint, the Scrum Team has two
requirements:
Attend the Daily Scrum
Update the Sprint Backlog
9. Scrum team
The important metric on the Sprint Backlog is the
estimated work remaining, not the work already
done.
A task that had 3 hours remaining on Monday
may have 5 hours remaining on Tuesday and 10
hours remaining on Wednesday, even though the
developer has worked on it solid for 2 days. This
is normal!
10. Scrum team
A not-so-funny joke:
A chicken and a pig decide to start a restaurant.
The pig says, "What should we call it?“
The chicken says, "How about 'Ham & Eggs'?“
The pig says, "No thanks. I'd be committed, but
you'd just be involved!"
People on the Scrum Team are Pigs (committed)
– everyone else is a Chicken (involved).
11. Scrum team
At the Daily Scrum, only Pigs can talk. Chickens
can come to the meeting to observe and learn,
but they cannot:
Talk
Make funny faces
Whisper
Take notes loudly
Communicate in any way
If they do, they must leave.
If they persist, they will be banned from the
meeting.
13. Planning
Team creates Sprint backlog from product
backlog items of highest priority.
Team defines the Sprint goal based on the items
that are planned for current Sprint.
Team breaks down the Sprint backlog features
into tasks.
Typically tasks are created in such as way that
each task can be completed in one day.
17. Daily Scrum
Team tracks Spring progress with daily scrum.
What did I do yesterday?
What will I do today?
Is there anything in my way?
18. Scrum review
The entire Sprint Team and the Scrum Master
should attend.
Others who are interested in seeing the results of
the Sprint may also attend.
Customer attendance is highly desirable.
Purpose is to solicit feedback.
Observations and comments will commonly
become items on the Product Backlog.
19. Scrum review
When the Sprint is complete, the Sprint Team
conducts a demonstration of what was
completed.
No more than 2 hours of preparation are allowed.
This should be purely a functioning demo – no
use of PowerPoint (unless you are developing
PowerPoint itself!) or other slides / mockups.
20. How To Implement Scrum in 10
Easy Steps
Step #1: Get your backlog in order!
Step #2: How to estimate your product backlog
Step #3: Sprint Planning/clarify requirements
Step #4: Sprint Planning/estimate tasks
Step #5: Create a collaborative workspace
21. How To Implement Scrum in 10
Easy Steps
Step #6: Sprint!
Step #7: Stand up and be counted!
Step #8: Track progress with a daily burn down
chart
Step #9: Finish when you said you would
Step #10: Review, reflect, repeat…
