The document discusses Scrum, an agile framework for managing complex projects. It describes Scrum's core components like sprints, roles, artifacts, and events. Sprints are short, timed iterations where self-organizing teams work on prioritized backlog items to create shippable increments. Key roles include the Product Owner who prioritizes features, and the Scrum Master who coaches the team. Artifacts include the Product and Sprint Backlogs and shippable increments. Events help the team inspect and adapt their process through planning, daily check-ins, reviews, and retrospectives. Many large companies have adopted Scrum to deliver working software frequently in response to changing requirements.

1. Scrum In Action
Mona Shokrof
Agile Coach and Trainer
Scrum Master, ITWORX Education

2. What is Scrum
2
Agile framework for completing
complex projects

3. Agile Values
Working Software over documentation
Individuals and interactions over process and tools
Responding to change over following a plan
Customer Collaboration over Contract Negotiation
3

4. Principles behind Agile
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
Working software is the primary measure of progress.
Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
4

5. Principles behind Agile
The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
Business people and developers must work
together daily throughout the project.
Simplicity--the art of maximizing the amount
of work not done--is essential.
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.
5

6. Principles behind Agile
Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
Continuous attention to technical excellence
and good design enhances agility.
The best architectures, requirements, and designs
emerge from self-organizing teams.
At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.
6

7. Scrum been used by
• Microsoft
• Yahoo
• Google
• Apple
• Qualcomm
• Time Warner
7
• IBM
• Philips
• Siemens
• Nokia
• BBC

8. Scrum Usage
8

9. Scrum Origin
9

10. Characteristics
• Progress made through sprints
• Self organizing teams
• Inspection and adaption
• Team works as a unit , doing all work in iterations
10

11. Sprint
• One to four weeks long - constant duration
• No requirement change during the sprint
• Work on all stages until work done during the sprint
11

12. Scrum Roles
• Team
• Scrum Master
• Product Owner
12

13. Scrum Team
• 5-9 persons
• Cross-functional
• Co-located
• Self Organizing
13

14. Product Owner
• Represents the Business side
• Makes scope vs. schedule decisions
• Prioritize the features
• Works with the team closely
14

15. Scrum Master
• Servant/Leader
• Focus on Agile values and principles
• Removes impediments
• Coach the team to be self organizing
• Protects the team from external interference
15

16. Scrum Artifacts
• Product Backlog
• Sprint Backlog
• Shippable Product Increment
16

17. Product Backlog
17
• Responsibility of the Product Owner
• Prioritized by the Product Owner

18. Product Backlog
• Features
• Defects
• Enhancements
• Experiments
Set of items that represent the components of the product

19. Product Backlog
Upcoming
sprints (2-3)
Current release
Future releases

20. Sprint Backlog
• Set of tasks to work on Product backlog item
• Responsibility of the team
• Task state updated daily
• Emerging tasks are added while working
20

21. Sprint Backlog
21

22. Product increment
• Working part of the product
• Potentially shippable
• Approved by the product owner
22

23. Definition of "Done"
• Team agreement
• What “Done” means ??
• Product Backlog item
• Task
23

24. Scrum Events
• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective
24

25. Sprint Planning
• All team attends the meeting
• Choose highest priority product backlog items to work
upon
• Break down items into tasks
• Team estimate tasks
• Team commits to finish these items
25

26. Sprint Planning
• Typically 2 - 4 hours for 2 weeks sprint
• High level Technical design may be considered
26

27. Sprint Planning
• Sprint Goal : goal statement of the sprint
• Sprint Backlog
27
Output

28. Daily Scrum
• aka daily standup
• maximum 15 mins
• Defined time and place everyday
• Team alignment
• Not status for Scrum Master
28

29. Daily Scrum
• What did you do yesterday?
• What will you do today?
• Is there anything blocking/delaying you?
29

30. Sprint Review
• Demo for potentially shippable product increment
• Product owner/team are attending
• Other stakeholders may attend
• Purpose is to inspect and adapt the product
30

31. Sprint Review
• Feedback gathered and put in Product Backlog
• Could include highlights of the done/remaining
product backlog items
• Typically 30 - 60 mins
31

32. Sprint Retrospective
• Team and Scrum master
• Product owner may attend
• Purpose is to inspect and adapt the process
• All team encouraged to speak
• Typically 1-2 hours
32

33. Sprint Retrospective
33

34. Scrum Brief
34

35. Additional Artifacts
• User Stories
• Burn down charts
• Burn up charts
35

36. User Stories
As a (user) , I want to (feature)
so I can (reason-benefit)

37. Burn down chart

38. Burn up chart

39. Additional Events
• Release planning
• Backlog refinement
39

40. Release planning
40

41. Workshop
41
The Greeting Card Application

42. References
• Scrum Guide
http://www.scrumguides.org/scrum-guide.html
• Mike Cohn Blog
http://mountaingoatsoftware.com/
• Agile Manifesto
http://agilemanifesto.org/
42

43. About Mona
Agile Coach and Trainer
www.shokrof.com
mona@shokrof.com
LinkedIn : Mona Shokrof
Agile ‫بالعربي‬