Agenda: What is Agile & Scrum? Agile Manifesto & principles What is Scrum? How Scrum works Scrum Roles Scrum artefacts Scrum Ceremonies

1. www.concertcare.com - bd@concertcare.com

2. Overview of Agile methodology
& Scrum
- Sandhya Ravishankar
November 22nd 2019

3. Agenda
• What is Agile & Scrum?
• Agile Manifesto & principles
• What is Scrum?
• How Scrum works
• Scrum Roles
• Scrum artefacts
• Scrum Ceremonies

4. What is Agile and Scrum?
• Agile refers to a set of “methods and practices based on the values and
principles expressed in the Agile Manifesto
• Scrum is a framework that is used to implement Agile development.

5. Waterfall model

6. Agile Software Development Manifesto - Values
• Individuals and Interactions Over Processes and Tools
• Working Software Over Comprehensive
Documentation
• Customer Collaboration Over Contract Negotiation
• Responding to Change Over Following a Plan

7. The Twelve Agile Manifesto Principles
1. Customer satisfaction through early and continuous software delivery
2. Accommodate changing requirements throughout the development
process
3. Frequent delivery of working software
4. Collaboration between the business stakeholders and developers
throughout the project
5. Support, trust, and motivate the people involved
6. Enable face-to-face interactions
7. Working software is the primary measure of progress
8. Agile processes to support a consistent development pace
9. Attention to technical detail and design enhances agility
10. Simplicity
11. Self-organizing teams encourage great architectures, requirements, and
designs .
12. Regular reflections on how to become more effective

8. What is scrum?
• With scrum a product is built in a series of iterations called sprints. They
breakdown big complex projects into bite-size pieces. This makes projects
manageable, allowing teams to ship high quality work faster and more
frequently and gives them more flexibility to adapt and change.
• At its core Scrum is all about continuous learning and adjusting to change.
It acknowledges we don’t know everything at the start of a project…it is
structured to help teams naturally adapt to changing market conditions
and user requirements

9. The Importance of Iteration and Improvement
• Scrum revolves over short iterative release cycles called sprints that allows
you to ship often, reprioritise when needed and constantly improve
• One of the core features of Scrum, and what makes it so potentially
powerful, is the idea of iteration and improvement. This is in regards to
both the product being worked on, and the efficiency of the team itself
Why is this so important?
• Because it lets you collect feedback from users early on, helping guide
development of the product to ensure a good fit with the user.
• In Scrum, an empirical process is implemented where progress is based on
observation and experimentation instead of detailed, upfront planning
and defined processes.

12. Who can benefit from Scrum?
• Scrum is not just limited to engineers or developers. But the framework
can be beneficial for other types of projects too.
• Scrum has been used by everyone from the FBI, to marketing agencies, to
construction crews.
• Any time you’re producing some sort of product, be it software or an
email campaign, Scrum can help you organize your team and get more
work done in less time.

13. How does Scrum work? - The 3-5-3 of Scrum

14. SCRUM CEREMONIES

15. Sprint Planning
• Meeting where team decides what is to be accomplished during the next
sprint
• Is a ceremony that helps
– focus execution
– minimize surprises
– guarantees overall higher quality code
Typically 1hr/week of iteration. 2 hrs for a 2 week sprint
• Key ceremony at the beginning of the sprint- during this meeting PO, SM,
ST come together to address 2 key questions - What can we deliver during
this sprint to achieve our sprint goal and how will we deliver that work
• These questions help everyone agree on the Sprint goal and map out the
next 2 weeks of work & set the team up for success
• 3 step planning process – Backlog grooming; Sprint planning meeting; First
few action items

16. Sprint planning
• Retrospective recap – Scrum Master presents any relevant action items
from the retrospective
• Product & Market update – PO presents it so everyone is on the same
page & understands the broader context
• Planning conversation – PO starts it with Development Team by setting up
the Sprint goal and determining the velocity
• Having a goal and data like your average velocity can help inform the
conversation and makes things easier
• Sprint goal is an objective that can be met by implementing stories from
the backlog.
• It helps the Team by providing the Why or the purpose of their work
• Average velocity = amount of work typically completed in a Sprint
• Now you are ready to plan a sprint

17. Making It All Visual
An important principle in Scrum is the idea of transparency. All team
members involved should be aware of what everyone else is working on,
progress being made, and what the team is trying to accomplish.
A big piece of this is the Scrum Board. This is a place where you can organize
your Backlog, as well as tasks that are being worked on in the current sprint
and their progress.

18. Daily Standup
• During each day of the sprint, the team has a daily standup
• Super short meeting that happens at the Same Time Same Place
• Goal of the daily scrum is to get everyone on the same page
• Its also a time to voice any concerns you have or things that maybe
blocking you from making progress towards the sprint goal

19. Sprint Review
• Sprint review happens at the end of the sprint
• Sprint review is an informal session to view a demo and see what was
accomplished
• Dev team shows the backlog items that are completed to the product
owner who approves them for release

20. Sprint Retrospective
• Last step of every sprint is the Sprint retrospective
• Teams come together to talk about and document what went well and
what didn’t
• Could be about project sprint, people, relationship, tools and certain
ceremonies
• Idea is not to dwell on what went wrong, but create a safe space where
people can talk about what went well and what needs to be improved
next time
• This makes a space for our shortcomings and reminds everyone to keep a
positive spirit of continuous improvement

21. Sprint Retrospective
Regardless of what we discover, we understand and truly believe that
everyone did the best job they could , given what they knew at that time,
their skills & abilities, the resources available and the situation at hand.
- Norm Kerth

22. SCRUM ROLES

23. Product owners
• They are the champions for the product
• Main job is to bring product vision to life and have a constant pulse on the
market and the customer-
• Focussed on understanding business & market requirements and then
prioritising the work that the development team will do

24. Scrum Master
• Scrum masters are scrum experts within the team
• They coach developers, product owners and the business on the scrum
process
• Look for ways to fine tune their practise
• Referred to as Servant leaders by the official scrum guide

25. Development team
• Comprises the developers, designers , testers, analysts, writers– people
who the day in & day out work to accomplish the sprint goals
• Collaborate with the PO to forecast how much work they can complete in
a sprint.
• Scrum encourages teams to learn through experiences, self-organize while
working on a problem, and reflect on their wins and losses to continuously
improve.
• They think about how to improve the development practises as they learn
what works best

26. SCRUM ARTIFACT

27. Product Backlog
• Master todo list
• Product Owner maintains it and uses it to plan the sprint backlog

28. Sprint backlog
• list of stories that Development Team is working on in the current sprint to
complete the Increment or the Sprint goal

29. Product Increment
• Product Increment is the usable end product from a sprint
• At the end of each Sprint, the work completed should be ready to deliver
to a client. This does not mean that it’s a finished, complete project. Far
from it. Rather, it means that the work should be complete enough to
show some sort of Minimum Viable Product (MVP, in startup parlance).
• Usually team shows the increment at the end of sprint demo.
• A milestone, Sprint goal, full version of shippable product..every team has
a different definition of done

30. Please reach us if any questions
bd@concertcare.com
Thank You !!