What is Agile and Scrum, their guiding principles and methods?

© 2017 ONE BCG. All Rights Reserved.
Agile - Scrum

2
Contents
- Agile Manifesto
- Roles and Artifacts
- Scrum Ceremonies
- Scrum and Software Development lifecycle
- Scrum Empirical Process

3
The Agile Alliance
Crystal XP
SCRUM DSDM
Pragmatic
Programming
Adaptive S/W
Development
THE AGILE ALLIANCE
Manifesto for Agile Software
Development
www.agilemanifesto.com

4
The Manifesto for Agile Software Development

5
Agile 12 Guiding Principles: Customer and Team
Customer Focused
1. Early and continuous delivery of software.
2. Welcome, Changing Requirements.
3. Deliver working software frequently.
Team Focused
4. Business and developers work together daily.
5. Build project around motivated individuals.
6. Emphasis on face to face conversation.

6
Agile 12 Guiding Principles: Development and Self Improvement
Development Focused
7. The working software shows progress.
8. Sustainable development phase.
9. Require technical excellence and good
design.
Remaining Features:
10. Simplicity.
11. Self organizing teams.
12. Regular team Retrospective and Adaptation.

7
What is Scrum?
● Scrum is an incremental, Iterative, Agile framework for software project
development and delivery.
● But Scrum is not just for software, it can be used for any type of complex project.
● Scrum significantly improves productivity and reduces time to benefits relative to
classic “waterfall” processes.
● Scrum processes allow organizations to adapt smoothly to rapidly-changing
requirements and produce a product that satisfies evolving business goals.

8
Scrum and Software Development Life Cycle

9
Scrum Roles and Artifacts

10
Scrum Roles and Artifacts
Product Backlog holds the feature, Bug fixes and Non functional requirements needed to
successfully deliver the product. Team is self organizing people who works on shippable
product every sprint. Team divides product backlogs into manageable user stories.
During planning higher priorities item move from product backlog to sprint backlog.
Product Owner owns the vision of product. What he wants to be product look like.
1. Helping the team to reach consensus for what can be achieved during a specific period
of time. (See sprint)
2. Helping the team to reach consensus during the daily scrum.
3. Helping the team to stay focused and follow the agreed-upon rules for daily scrums.
(See pigs and chickens)
4. Removing obstacles that are impeding the team's progress.
5. Protecting the team from outside distractions.

11
Scrum Artifacts

12
Copyright © 2018 ONE BCG. All rights reserved.
Scrum Ceremonies

13
Sprint Planning Meeting
Timebox: Eight hours for a four-week sprint, proportionately shorter for shorter sprints.
Attendees: The complete Scrum team, including all roles.
Most important: Team capacity and DoD (Definition of Done).

14

15
Daily Scrum
Timebox: Fifteen minutes is standard, irrespective of the duration of the sprint length.
Attendees: The complete Scrum team, including all roles.
Most important: To speak about any impediments.

16
Daily Scrum

17
Sprint Review Meeting
Timebox: Four hours for a four-week sprint, proportionately shorter for shorter sprints.
Attendees: The complete Scrum team, including all roles, plus any other stakeholders
who are interested in the project’s success.
Most important: Demo of working software and assessing the feedback.

18
Sprint Review Meeting

19
Sprint Retrospective Meeting
Timebox: Three hours for a four-week sprint, proportionately shorter for shorter sprints.
Attendees: The complete Scrum team, including all roles; the product owner's
attendance is optional.
Most important: To brainstorm and agree on what is working and what is not.

20

21
Backlog Grooming/Refinement/Management Meeting
Backlog grooming is when the product owner and some, or all, of the rest of the team
review items on the backlog to ensure the backlog contains the appropriate items, that
they are prioritized, and that the items at the top of the backlog are ready for execution.
Some of the activities that occur during this refinement of the backlog include:
● Removing user stories that no longer appear relevant.
● Creating new user stories in response to newly discovered needs.
● Re-assessing the relative priority of stories.
● Assigning estimates to stories which have yet to receive one.
● Correcting estimates in light of newly discovered information.

22
Principle
“Open And Honest Communication. People need to be free, and
to perceive that they are free, to offer suggestions. Open and
honest communication enables people to make better decisions
because the quality of the information that they are basing them
on is more accurate.”

23
Scrum Empirical Process
Empirical - Verifiable by observation

24
Protected Scrum
If the scrum attendee is a pig, it means he is directly accountable for completion of the
task at hand. If the attendee is a chicken, he may be somewhat involved in the task at
hand but is not the person whose "bacon is on the line" if the task doesn't get completed
on time. At daily scrums, pigs may talk. Chickens must remain silent.

25
Chickens?

26
Few Other Terms
Velocity: An optional, but often used, an indication of the average amount of Product
Backlog turned into an Increment of product during a Sprint by a Scrum Team,
tracked by the Development Team for use within the Scrum Team.
Burn-down Chart: a chart that shows the amount of work which is thought to remain
in a backlog. Time is shown on the horizontal axis and work remaining on the vertical
axis. As time progresses and items are drawn from the backlog and--completed, a
plotline showing work remaining may be expected to fall. The amount of work may be
assessed in any of several ways such as user story points or task hours. Work
remaining in Sprint Backlogs and Product Backlogs may be communicated using a
burn-down chart. See also: Burnup Chart

27
Burn-up Chart: A chart which shows the amount of work which has been completed.
Time is shown on the horizontal axis and work completed on the vertical axis. As time
progresses and items--are drawn from the backlog and completed, a plot line showing the
work done may be expected to rise. The amount of work may be assessed in any of
several ways such as user story points or task hours. The amount of work considered to
be in-scope may also be plotted as a line; the burn-up can be expected to approach this
line as work is completed.
SPIKE in Scrum: Spikes are an invention of Extreme Programming (XP), are a special
type of user story that is used to gain the knowledge necessary to reduce the risk of a
technical approach, better understand a requirement, or increase the reliability of a story
estimate.

28

What is Agile and Scrum, their guiding principles and methods?

More Related Content

What's hot (20)

Similar to What is Agile and Scrum, their guiding principles and methods? (20)

More from ONE BCG (11)

Recently uploaded (20)

What is Agile and Scrum, their guiding principles and methods?

Editor's Notes