The document appears to be a presentation about agile software development and the scrum framework. It defines what agile and scrum are, describes the core parts of the scrum process including products, product backlogs, sprints, daily standups, and retrospectives. It also notes some potential issues with agile approaches.

2. I am…..…
www.ticketslk.com
Sameera
Team lead / Senior Software Engineer
Ridgecrest Asia (pvt) Ltd
Agile software development with scrum
2
sameera

3. Let’s try and find out
• What is agile ?
• What is scrum ?
• Will scrum really be able to solve all your
problems ?
Agile software development with scrum
3
sameera

4. Software development..
Agile software development with scrum
4
sameera

5. Agile in my eyes
Comes in handy to find out mistakes/errors at
the early stages
Agile software development with scrum
5
sameera

6. What is in the Agile “Game”???
• Iterative development.
• Cross functional teams.
• Expecting changes.
• Frequent inspection and adaptation.
• Teamwork / leadership.
Agile software development with scrum
6
sameera

7. Agile’s walk from the Past…..
The modern definition of agile software development evolved in the mid-1990s as part of a reaction
against "heavyweight" methods, perceived to be typified by a heavily regulated, regimented, micro-
managed use of the waterfall model of development. The processes originating from this use of the
waterfall model were seen as bureaucratic, slow, demeaning, and inconsistent with the ways that
software developers actually perform effective work. A case can be made that agile and iterative
development methods mark a return to development practice from early in the history of software
development.[1] Initially, agile methods were called "lightweight methods.“
An adaptive software development process was introduced in a paper by Edmonds (1974). [2] Notable
early Agile methods include Scrum (1995), Crystal Clear, Extreme Programming (1996), Adaptive
Software Development, Feature Driven Development, and Dynamic Systems Development Method
(DSDM) (1995). These are now typically referred to as Agile Methodologies, after the Agile
Manifesto published in 2001.
In 2001, 17 prominent figures[3] in the field of agile development (then called "light-weight methods")
came together at the Snowbird ski resort in Utah to discuss ways of creating software in a lighter,
faster, more people-centric way. They coined the terms "Agile Software Development" and "agile
methods", and they created the Agile Manifesto, widely regarded as the canonical definition of
agile development and accompanying agile principles. Later, some of these people formed The
Agile Alliance,[4] a non-profit organization that promotes agile development.
Wikipedia
Agile software development with scrum
7
sameera

8. Principles of agile development
• Individuals and interactions over processes
and tools
• Working software over comprehensive
documentation
• Customer collaboration over contract
negotiation
• Responding to change over following a plan
http://agilemanifesto.org/
Agile software development with scrum
8
sameera

9. Agile methods…
• Extreme Programming (XP).
• Scrum.
• Getting Real (37Signals).
• Etc..
Agile software development with scrum
9
sameera

10. Agile software development with scrum
10
sameera

11. Pig and Chicken
• A pig and a chicken are walking down a road.
The chicken looks at the pig and says, "Hey,
why don't we open a restaurant?" The pig
looks back at the chicken and says, "Good
idea, what do you want to call it?" The chicken
thinks about it and says, "Why don't we call it
'Ham and Eggs'?" "I don't think so," says the
pig, "I'd be committed, but you'd only be
involved."
Agile software development with scrum
11
sameera

12. Let’s start the story…..
• Product
Agile software development with scrum
12
sameera

13. Product should have a…
Product owner who represents Stakeholders
Agile software development with scrum
13
sameera

14. Product should have a..
Product backlog
Agile software development with scrum
14
sameera

15. Product owner has to ensure..
• The product backlog will only contain necessary features.
Agile software development with scrum
15
sameera

16. Then comes the Scrum Master
• Facilitator
Agile software development with scrum
16
sameera

17. Following him the Scrum Team
• Cross functional 7-9 people
Agile software development with scrum
17
sameera

18. Then they create Release backlog
• Release backlog is a subset of product
backlog.
Agile software development with scrum
18
sameera

19. Then it is divided to sprint backlogs
Agile software development with scrum
19
sameera

20. Wait.. Let’s break it down…
Agile software development with scrum
20
sameera

21. They have Daily Standup
• What have you done since yesterday?
• What are you planning to do today?
• Do you have any problems preventing you from accomplishing
your goal?
Agile software development with scrum
21
sameera

22. What about bugs ?
•Should be fixed as and when you find it.
•Might have 1-2 more sprints to fix critical
bugs.
Agile software development with scrum
22
sameera

23. They measure their work with
Burn down charts
Agile software development with scrum
23
sameera

24. Then they have Sprint Review
Meeting
• Present the completed work to the
stakeholders (a.k.a. "the demo")
Agile software development with scrum
24
sameera

25. Finally …Sprint Retrospective meeting
• Discussion about completed sprint.
Agile software development with scrum
25
sameera

26. …..
Agile software development with scrum
26
sameera

27. Is Agile / Scrum, the Aladin’s lamp ?
• No, Agile also can go wrong..
Agile software development with scrum
27
sameera

28. Q&A
Agile software development with scrum
28
sameera