Scrum is an agile framework for managing product development that focuses on quality, collaboration, and adaptability over rigid adherence to processes or plans. It emphasizes frequent inspection and adaptation, self-organizing cross-functional teams, and transparency. Key aspects include prioritizing a backlog of features based on business value, conducting short development iterations called sprints, and daily stand-up meetings for teams to share progress and issues. The goal is to deliver high quality, valuable software more quickly through an adaptive process of continuous improvement.

1. SCRUM Overview
By Daniel R Borsato

2. Summary

3. Software business evolution

4. Software business evolution

5. Software business evolution
Waterfall on theory

6. Software business evolution
Waterfall for real

7. Finally, Agile
● Focus on quality
● “The new product development game”
● Unpredictability
Lean Thinking

8. Agile Manifesto
● Individuals and Interactions over Processes and Tools
● Customer Collaboration over Contract Negotiation
● Responding to change over Following a plan
● Working Product over Comprehensive Documentation

9. Scrum? What is it?

10. Framework
A method which says that methods is not so important.

11. Adaptable
Rule number 1: The rules can be changed.

12. Why? What is the benefits?
High quality with robust software

13. Why? What is the benefits?
Faster than ever!
● At least 4 times
more productive
● There are some
cases that is
possible to find 10
times more
productive

14. Why? What is the benefits?
Transparency and visibility
● Daily revision;
● Each iteration with
new product
version;

15. Why? What is the benefits?
Team communication

16. Iceberg Planning

17. First concepts
●
● Time-box planned
● 1 to 4 weeks of work

18. First concepts
● List of in format
● Ordered by

19. First concepts
● List of to do into the sprint;
● Based on on Product Backlog;
● Accordingly to the capacity of the

20. Breaking Paradigms
Slice Development

21. Breaking Paradigms
Flexible scope
● Scope
● Deadline
● Cost
● Quality
Changed Requirements are welcome!

22. Breaking Paradigms
Continuous Planning

23. Breaking Paradigms
Iterative and incremental

24. Persons

25. Product Owner
● Business vision
● Prioritized Product Backlog
● Maximize ROI (Return of investment)
● Provides feedback
● Available to clarify doubts

26. Scrum Master
● Protects team
● Owns the process
● Not the boss
● Facilitator
● Guardian of values and practices

27. Development Team
● Multidisciplinar
● Self Manageable
● Self Organising
● Has skills to deliver
● Constant Communication
● Compromised to the objective

28. Meetings

29. Planning
Stakeholders: Development Team + PO +
Scrum master
Frequency: Once per sprint
When: Before Sprint starting
Objective: Select the Sprint Backlog and sprint
goal

30. Stand-up
Stakeholders: Development Team + Scrum
Master. PO is optional
Frequency: Once per day
Maximum 15 minutes
Objective: Show the progress, identify blocked
issues, keep focus.
Not Objective: Discuss technical issues

31. Refinement - Grooming
Stakeholders: Development Team + PO
Frequency: Once per sprint
When: Before planning
Objective: Estimate the tickets in Product
Backlog

32. Retrospective
Stakeholders: Development Team + Scrum
Master + PO
Frequency: Once per sprint
When: At the end of the sprint
Objective: Look at the positive and negative
points, taking actions to improve the work in next
sprint

33. Review
Stakeholders: PO + Scrum Master +
Development Team. Customer is optional
Frequency: Once per sprint
When: At the end of sprint
Objective: Show the part of product delivered in
the sprint
PO < customer < stakeholders < final user
Monthly < Weekly < Daily
Dev < QA < Production

34. Story, how can I write it?
● DoD
● Story Points

35. Estimation

36. Estimation

37. Estimation

38. Estimation