Presentation about how to start implementing scrum in projects. Explaining core concepts and artifacts

1. Starting with Scrum
Jimmy Campos

2. Agenda
• SCRUM
• Actors
• Product Backlog
• Sprint Backlog
• Definition of Done
• Daily Scrum Meeting
• Sprint Review
• Sprint Retrospective

3. What is?
• Scrum is a simple framework for effective
team collaboration on complex projects.
• Is an agile methodology, it allows us
deliver products more faster.

6. Product Backlog
• Ordered list of ideas for the product
• It is the single source from which all
requirements flow
• Product backlog usually doesn’t change

7. Product Backlog Meeting
• Keeping the product backlog ordered
• Removing or demoting items that no
longer seem important
• Adding or promoting items that arise or
become more important
• Splitting items into smaller items
• Merging items into larger items
• Estimating items

8. Sprint Backlog
• Sprint Duration: 2-4 week
• Plan what item of the product backlog we
will work, estimate it and split it in tasks

9. Definition of Done
• When the product increment is delivered, it
needs to be "done" according to a shared
understanding of what "done" means. This
definition is different for every Scrum
team, and as the team matures the
Definition of Done will expand and become
more stringent.

10. What is Done?
• All code is finished?
• Code is finished and tested?
• Code is deployed?
• Client approval?

11. Daily Scrum Meeting
• Time boxed meeting (15 minutes) where
all the team talk about
– What I have accomplished yesterday?
– What I plan to accomplish today?
– What (if anything) is impeding my progress?
• This can be at 9am

12. Sprint Review
• At the end of the sprint, the Scrum team
and stakeholders review the sprint's
output.
• Time box: Recommended 1 hour per
week of sprint duration.

13. Sprint Retrospective
• Review how things went in terms of the
process, relationships among people, and
the tools.
• What went well and what didn't go so
well, and it identifies potential
improvements

14. Q&A

15. Thanks!