This provides basic introduction of Scrum and why we should use it.

1. Anmol Tuteja
Scrum Master & Agile Consultant

2. A Typical Project

3. Customer Requirements
Customer - I want an object that has 4 legs, 2ears 1trunk, 1tail, 2tusks

4. Project begins – Delivery in 6 months

5. Project Starts
Time
Scope
Budget
1. All Processes followed.
2. Everything documented.
3. Contract terms clearly defined.
4. Everything is planned.

6. After 6 months

7. Delivery Day
Project team is like - All Requirements have been met
1. 4 Legs
2. 2 Ears
3. 1 Trunk
4. 2 Tusks
5. 1 Tail
6. And we have a bonus free bee for your Halloween – The
pumpkin

8. What was expected What got delivered

9. Stakeholders be like

10. What’s the Solution?
Collaborate more with the
customer/Stakeholders More Feedback loops Build/Work Iteratively

11. To be Agile or Not?

12. Scrum

13. Scrum is not a process or a technique for
building products.

14. It is a framework within which you can employ various
processes and techniques.
The Scrum framework consists of Scrum Teams and their
associated roles, events, artifacts, and rules. Each component
within the framework serves a specific purpose and is essential
to Scrum’s success and usage.
The rules of Scrum bind together the events, roles, and
artifacts, governing the relationships and interaction between
them.
- Scrum Guide

15. Transparency
Inspection
Adaption
Scrum is founded on empirical process control theory, or empiricism. Empiricism
asserts that knowledge comes from experience and making decisions based on what
is known.

16. Scrum Principles
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

17. Scrum Values
Focus Courage Openness Commitment Respect

18. Scrum Framework

19. Sprint
• A Sprint is a specific period of time (1-4 weeks) which is required to
deliver some amount of work in the ever changing scope.
• With each Sprint we deliver a valuable set of things which can
potentially go live.

21. Scrum Roles
• 1. Development Team (No Roles, Titles etc. within the Dev Team)

22. 2. Product Owner

23. 3. Scrum Master

25. Accountability

26. Accountability

27. Scrum Activities
1. Product Backlog Refinement – Keep the Product Backlog items
ready, uncertainty to Certainty.

28. 2. Sprint Planning – Define Sprint Goal, achievable outcome.

29. 3. Daily Scrum – Plan for the Day, Inspect and Adapt
daily towards reaching the Sprint Goal.
Note: Its not a status meeting

30. 4. Sprint Reviews – Get Feedback on the Work
Done during the Sprint. Inspect and Adapt.

31. 5. Sprint Retrospective – To Inspect and Adapt to become
more effective and Efficient on process, people, culture
aspects.

32. Artifacts
The Product Backlog is an ordered list of everything that might be needed in the product and is the
single source of requirements for any changes to be made to the product.
The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering
the product Increment and realizing the Sprint Goal.

33. User Story – (Not a Part of Scrum Framework, taken from XP)It is a token for communication between the
Product Owner and the Dev Team.
It has 3 parts
1. Who – Describe the intended user.
2. What – List what they need and want.
3. Why – Purpose of the task.

34. Information Radiators
1. Sprint Board
1. Because we are Transparent.
2. Check our Progress
3. Inspect and Adapt

35. 2. Sprint Burndown Chart
1. Know if we are going slow or fast
2. Know how much work is left at any given
point in time.
3. Take actions to increase the speed if
necessary.