2. What is Agile and Scrum
Scrum Principle
Scrum Role
Scrum Activities - Ceremonies
◦ Iteration Planning
◦ Daily Scrum
◦ Iteration Review
◦ Iteration Retrospective
◦ Scrum Artifacts
◦ Product Backlog
◦ Iteration backlog
◦ Burn Down Chart
Scrum Glossary
What Agile is Not?
3. Agile is a framework for project management in all
mechanic aspects of the project and a new mindset in
order to achieve better successful projects.
In short, Agile is the WHAT and Scrum is the HOW
4. Scrum
FDD (Feature Driven Dev)
Crystal
(small teams and low profile project)
DSDM (Dynamic Sys. Dev method)
Lean
Extreme Programming (XP)
Scrum is one way to achieve it.
6. Let’s make a to-do list
What do I need
to do, so I can
watch T.V.?
To-Do List
Science HW
Math HW
History Project
Music Class
Play time
Watch T.V.
7. You guess the time for each task
Looks like I can
still manage to
watch T.V ….
To-Do List
30 mins Science HW
30 mins Math HW
60 mins History Project
60 mins Music Class
60 mins Play time
60 mins Watch T.V.
5 Hrs
8. Dang, mom
Set the priorities says I have to
sleep @ 9 can’t
watch T.V.….
Most important To-Do List
30 mins Science HW
30 mins Math HW
60 mins History Project
60 mins Music Class
60 mins. Play time
60 mins Watch T.V.
Least important
10. Only instead of this We use impressive name
Backlog / User Story
=>
To-do List / Task
Guess Estimates
Important or Not Prioritized
11. Most important
User Stories
Create new device
Review the Design Doc
3 Wk Fix P1,P2 Defects
Technical Documentation
Prepare the demo
Update Wiki
Fix P3 defects
Least important
1 Wk 1 Wk 1 Wk
12. Three things to remember
1. Make a list of stories – Backlog
2. Guess the effort – Estimates
3. Is it important - Prioritized
13.
14.
15.
16. Satisfy Customer
Accommodate Change - even late in development
Working software
Work as a Team (Individuals and interaction)
Communicate face-to-face
Co-located, where possible
18. 1. Product Owner
◦ Owner of the project vision
◦ Represent customer
◦ Define features
◦ Prioritize features
◦ Define acceptance criteria
◦ Accepts or Rejects results
2. Team - ” work force “
◦ Small (5-9 people)
◦ Empowered
◦ Self Organized
◦ Flat hierarchy
◦ Adaptive
◦ Define task and Estimates effort
◦ Develop product and Ensure quality
◦ Co-located
3. Scrum Master
◦ Scrum guide
◦ Facilitate the team
◦ Support the processes
◦ Team protector
◦ Help Remove impediments
20. Prioritize features / stories
Discuss acceptance criteria
Verify understanding
Estimates the effort
½ - 1 hr per Iteration week
21. What did I do yesterday
What I plan to do today
What are the impediments / road blocks
Team talks to the team (not to the scrum
master)
No problem solving, take action item and
move on
15 mins daily
22. Whole team is needed
Show complete features
Accept or Reject results
1-2 hours per Iteration
23. Whole team participates
What worked
What didn't’t work
What to improve
½ - 1 hr per Iteration
Evolve the process
24. 1. Product Backlog - Product owner compiles prioritized list
of all the requirements.
2. Iteration Backlog – Set of work from the product backlog
that team agrees to complete in a given Iteration. Before
each Iteration, the highest prioritized goals are transferred to
a Iteration Backlog.
Story : As a <user> I want <functionality> so that
<benefit>
A good story is
◦ Independent
◦ Negotiable
◦ Valuable
◦ Estimable
◦ Small
◦ Testable
3. Burn Down Chart: At a glance look the remaining work Vs
complete work
25. A product owner creates a prioritized list of requirements in terms of stories
called a product backlog.
During Iteration planning, the team pulls a small chunk from the top of that wish
list, a Iteration backlog, and decides how to implement those pieces.
The team has a certain amount of time, a Iteration, to complete its work - usually
two to four weeks - but meets each day to assess its progress (daily scrum).
Along the way, the Scrum Master keeps the team focused on its goal.
At the end of the Iteration, the work should be potentially shippable, as in ready
to hand to a customer, put on a store shelf, or show to a stakeholder.
The Iteration ends with a Iteration review and retrospective.
As the next Iteration begins, the team chooses another chunk of the product
backlog and begins working again.
The cycle repeats until Minimum Marketable Features (MMF) from the product
backlog have been completed or a deadline arrives.
26. Agile is NOT an excuse to stop producing
documentation.
It IS a reason to examine why you are producing the document
Agile is NOT an opportunity to eliminate
planning.
It IS an opportunity to institute rolling wave planning
Agile is NOT open season on scope creep.
It IS an invitation to the customer to collaborate
Agile is NOT about blindly following a set of
“best” practices.
Agile IS about doing what makes sense,
27.
28. Scrum A type of agile method designed for product management and development, characterized by short cycles of work with
constant feedback from customers
Scrum Master The person who facilitates the Scrum process
Scrum Team A self-organizing group of people who have the skills and time to work on the items in the product backlog
Product Owner The person who manages the priority of the team's work through the use of a Product Backlog
Iteration A time boxed mini-project for the team to deliver a small number of items from the top of the product backlog
Story / User Story In Scrum, work is expressed in the backlog as user stories. A team may write its user stories in a number of
ways as long as they are written from the perspective of the end user. Put another way, team members are encouraged to
think of their work from the perspective of who will use it (hence “user” story).
Story Point Story point is a arbitrary measure used by Scrum teams. This is used to measure the effort required to implement a
story.
Acceptance Criteria / DoD ( Definition of Done) Acceptance Criteria or Definition of Done is a simple list of activities (writing
code, coding comments, unit testing, integration testing, release notes, design documents, etc.) that add
verifiable/demonstrable value to the product.
Product Backlog A prioritized list of valuable work to be done by the team
29. Iteration Backlog the detailed tasks the team will finish in order to complete the
product backlog items they have selected for the Iteration
Iteration Planning Meeting The time when the team selects product backlog items
and creates the Iteration backlog for the current Iteration
Daily Scrum A meeting that occurs every day during which the team members report
status to the rest of the team
Demo The first part of the Iteration Review Meeting where the team shows its work
results to interested stakeholders
Iteration Review Meeting The time at the end of the Iteration when the team gets
feedback on the delivered results and looks for process improvements
Burn down Chart A graphical representation of the amount of work remaining in a
Iteration, release or project
Impediment or Obstacle Something that is preventing a team member or the team
from getting their work done
Retrospective The second part of the Iteration Review meeting where the team finds
ways to improve how it works
Stakeholders All the people outside the team who care about the value delivered by
the team, often including management, clients, users, and suppliers
Velocity The amount of work that the team can get done in a Iteration
30. Some other terms you may here…
1. Iterative
2. Time-boxed delivery
3. Adaptive planning
Characteristics of agile teams
◦ Empowered
◦ Self-directed
◦ Adaptive
◦ Flat hierarchy
