2. PURPOSE OF THE COURSE
1. History and definition of Scrum
2. The Scrum theory
3. The Scrum team (roles)
4. Scrum Artifacts
5. Scrum events (workflow)
6. Scrum development tools
7. Conclusion
2
5. THE SCRUM THEORY
• Scrum is founded on empirical process control
theory, or Empiricism.
• Scrum implements the empirical process using :
➢ Transparency
➢ Inspection
➢ Adaptation
to optimize predictability and control risk
5
7. SCRUM ARTIFACTS(DOCUMENTS USED IN SCRUM)
7
Where product owner
create a list of ordered
features (user stories)
It contains also the
changes to be made to
the product.
It is the set of Product
Backlog items
selected for the
Sprint, plus a plan for
delivering the product
Increment and
realizing the Sprint
Goal
Y:tasks that must be
completed to finish the
project
X:times of the project
=> To measure project
progress
8. SCRUM ARTIFACTS(DOCUMENTS USED IN SCRUM)
• User Story is written as the following
As a <role>
I need <task list >
to get <result>
Example
As an online buyer,
I need to be able to add items to my shopping cart ,
delete the items ….
so that you can buy only what I am really certain
about
8
11. SCRUM EVENTS (WORKFLOW)
• The Sprint is the heart of Scrum
• A time-box of one month or less during which a
potentially releasable product Increment is
created.
• Never extend the duration but in the extreme
case reduce what needs to be done.
➢ Consisted of 4 events;
11
12. SCRUM EVENTS (WORKFLOW)
• Sprint Planning
This plan is created by the collaborative work of the entire Scrum Team.
Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint
➢ Setting the goal of the sprint
➢ Identifying the details of the work (tasks)
➢ Definition of acceptance criteria
• Daily Scrum
the scrum master ensures that the daily scramble takes place,
but the development team that is responsible for it and it takes only 15min.
➢ It is the key of inspection and adaption
➢ Synchronization of the activities of the team
➢ Discussing what is done, remains to be done, obstacles
encountered.
Daily scrum example.mp4 12
13. SCRUM EVENTS (WORKFLOW)
• Sprint review
➢ Takes place at the end of the sprint
➢ Aims to inspect the Increment and adapt the Product
Backlog if needed
➢ Time boxed to 4 hours
➢ The Development Team demonstrates the work that it has
“Done” and answers questions about the Increment
➢ The entire group collaborates on what to do next
• Sprint Retrospective
➢ Occurs after the Sprint Review and prior to the next Sprint
Planning
➢ 3 hours time boxed
➢ Between the Scrum team to inspect the sprint
➢ Plan to ameliorate the upcoming sprint 13