Scrum is the most popular Agile Framework; during this presentation the attendees will understand the value, and an overview of the powerful scrum framework: its roles, its artifacts and its ceremonies

1. Introduction to
Scrum
Hasan Jaffal, PMP, CSM

2. Thanks to our sponsors
GOLD
SILVER BRONZE
HOST

3. THANKS TO OUR
MEDIA PARTNERS
ECO-SYSTEM PARNERS
SUPPORT SPONSORS ORGANIZER

4. Agenda
• What’s a Project? The Traditional SDLC…
• The Agile Way
• Scrum Framework: Process, Roles, Meetings and Artifacts

5. What’s a Project?
• PROJECT: According to the PMBOK
Guide, Fifth Edition, a Project is a
temporary endeavor undertaken to
create a unique product, service or
result
• NOT PROJECT: An ongoing and
repetitive work

6. Project vs Operations
Project
Always has a start and end
date.
Produces a unique
product, service or result.
Operation
Ongoing process of
functions
Always produces the
same product, service, or
result

7. The Traditional Grant Ideas
Requirements
Design
Development
Testing
Maintenance
Waterfall Development
is the traditional approach to
Software Development

8. The Traditional Grant Ideas
In 1970, Dr. Winston Royce published “Managing the Development of Large Software Systems ,”
in which the waterfall paradigm was first documented. He said:
“I believe in this concept, but the implementation described
above is risky and invites failure .”

9. Agile Development
Requirements
Design
Development
Testing
Maintenance

10. Manifesto for Agile Software Development
Individual and interactions Process and toolsOver
Working Software Comprehensive documentationOver
Customer Collaboration Contract negotiationOver
Responding to change Following a planOver

11. Agile Methodologies
Kanban
3
Scrum
9
13
XP
fewer rules to follow more rules to follow
120+
RUP

12. The Scrum Process
Sprint Review
Product
Backlog
Potentially
Shippable
Increment
Sprint
Backlog
1-4 WEEKS
24Hours

13. Backlogs
This is the
Product Backlog
This is the
Sprint Backlog
• The 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
• Analyze and evaluate product backlog to select sprint goal
• Create sprint backlog (tasks) from product backlog items
(user stories / features)
• Estimate sprint backlog in hours
• Individuals sign up for work of their own choosing, Work is
never assigned
• Estimated work remaining is updated daily
0
225
450
675
900
Hours

14. Backlogs
“As a <user role>, I want <goal> so that <reason <.”

15. Backlogs
Backlog item Estimate
Allow a guest to make a reservation 3
As a guest, I want to cancel a reservation. 5
As a guest, I want to change the dates of a reservation. 3
As a hotel employee, I can run RevPAR reports (revenue-per-
available-room(
8
Improve exception handling 8
... 30
... 50

16. Scrum Roles
TeamScrum MasterProduct Owner

17. Scrum Roles / Product Owner
• Define the features of the product
• Prioritize features according to
market value
• Adjust features and priority every
iteration, as needed
• Accept or reject work results

18. Scrum Roles / Scrum Master
• Responsible for enacting Scrum
values and practices
• Removes impediments
• Ensure that the team is fully
functional and productive
• Enable close cooperation across all
roles and functions
• Shield the team from external
interferences

19. Scrum Roles / The Team
• Typically 5-9 people
• Cross-functional
• Members should be full-time
• Teams are self-organizing

20. Scrum Ceremonies - Sprint Planning
• Select sprint goal
• Team selects items from the product
backlog they can commit to
completing
• Sprint backlog is created
• Tasks are identified and each is
estimated
• Collaboratively, not done alone by
the ScrumMaster
As a vacation planner, I
want to see photos of the
hotels.
Code the middle tier (8
hours(
Code the user interface ( 4(
Code the class ( 6(
Update performance tests
(4)
(1-16hours)

21. Scrum Ceremonies - Daily Meeting
• Not for problem solving
• Whole world is invited
• Only team members,
ScrumMaster, product owner,
can talk
• Helps avoid other
unnecessary meetings
Daily 15-minutes Stand-up

22. Scrum Ceremonies - Sprint Review
• Team presents what it
accomplished during the sprint
• Typically takes the form of a demo
of new features or underlying
architecture
• Informal
• Whole team participates
• Invite the world

23. Scrum Ceremonies - Sprint Retrospective
The sprint retrospective is usually the last thing done in a sprint.

24. Where to go next
• Other rooms
• Some of the slides of this presentation are created by
www.mountaingoatsoftware.com
• www.scrumalliance.org
• www.controlchaos.com
• www.scrum.org

25. Thank You
Hasan Jaffal
www.jaftalks.com
jaftalks@icloud.com