Gives an overview for any one who just started usinig Scrum

1. I believe in Agile Bet
you Scrum works?
Prasad_keral@rediffmail.com
© Satyam 2009

2. Why this talk?
Right - Business imperative
Since Jan 2009 we have submitted many proposal on Agile and scrum, we
need to quickly ramp up the competencies Venkatesh_Kempareddy,
Agile SO Qedge
In this challenging business environment Agile has excellent ROI than any
other method, many of our customers are migrating to Agile - Suresh_P,
MS, RCC
RCC
Many project managers are requesting for developers sensitized and
worked in Agile project Lakshman_Kokonda, Java RCC
© Satyam 2009 2

3. Agenda for this talk
What is SCRUM?
Roles in Scrum
Artifacts in Scrum
How do we do SCRUM? Rituals
FAQ s
Key takeaway
References and further reading
© Satyam 2009 3

4. What is SCRUM ?
Scrum is an agile, lightweight process to manage and control
development/ maintenance work.
Scrum is a wrapper for existing engineering practices.
Scrum is a team-based approach to iteratively, incrementally
develop systems and products when requirements are rapidly
changing
Scrum is a process that controls the chaos of conflicting
interests and needs.
© Satyam 2009 4

5. Ro le s In S c ru m
3 roles in Scrum
The Product Owner
The Scrum Team
The Scrum Master
© Satyam 2009 5

6. Product owner
The Product Owner is responsible for achieving maximum business value,
by taking all the inputs into what should be produced, from the customer or
end-user of the product, as well as from Team Members and stakeholders
and translating this into a prioritized list called Product Backlog .
< customer representative, who knows what product features need to be build>
© Satyam 2009 6

7. Scrum Team
The team in Scrum is cross-functional it includes all the expertise
necessary to deliver the potentially shippable product each Sprint and it is
self-managing , with a very high degree of autonomy and accountability.
Typically 5-10 people
Cross-functional
QA, Programmers, UI Designers, etc.
Members should be full-time (May be exceptions (e.g., System Admin, architect etc.)
Teams are self-organizing
Ideally, no titles but rarely a possibility
Membership can change only between sprints
© Satyam 2009 7

8. The Scrum Master
The Scrum Master is one of the most important elements of Scrum success,
he / she is responsible for making sure a Scrum team lives by the values
and practices of Scrum, protects the team by making sure they do not over
commit themselves to what they can achieve during a sprint.
The Scrum Master facilitates the Daily Scrum Meeting and becomes
responsible for removing any obstacles that are brought up by the team
during those meetings.
© Satyam 2009 8

9. Key artifacts of Scrum
Product Back log
Sprint Back log
Burn out chart
© Satyam 2009 9

10. Product Back log
The Product Backlog is a master list of all functionality desired in the product; every
team member will have access to this list and be aware of the product backlog.
It is managed & prioritized and owned by the Product Owner, this backlog exists
(and evolves) over the lifetime of the product; it is the product road map.
It includes a variety of items, primarily new customer features, but also
engineering improvement goals, exploratory or research work and, possibly known
defects.
© Satyam 2009 10

11. Sprint Back log
The Sprint Backlog is the list of tasks that the Scrum Team is committed to complete
in the current Sprint. Each item has it s own status and should be updated every day
Items on the Sprint Backlog are drawn from the Product Backlog by the
team based on the priorities set by the Product Owner and the team's perception of
the time it will take to complete the various features.
© Satyam 2009 11

12. Burn down chart
This graph shows, each day, a new estimate of how much work (measured in
person hours) remains until the team s tasks are finished.
Ideally, this is a downward sloping graph that is on a trajectory to reach zero
effort remaining by the last day of the Sprint.
© Satyam 2009 12

13. How do we do scrum?
© Satyam 2009 13

14. Scrum Rituals / ceremonies
The Sprint Planning Meeting
The Sprint Planning Meeting is a collaborative meeting which takes place at the beginning of
each Sprint, The Sprint Planning Meeting is attended by the Product Owner, Scrum Master and the entire
Scrum Team. The Product Owner describes the highest priority features to the team, Team selects backlog
highest priority features to the team, Team selects backlog
items as per priority, Team estimates the efforts for the selected items, and makes a commitment to complete
the work
The Daily Scrum Meeting
This is a short (15 minutes or less) meeting that happens every workday at an appointed time.
Everyone on the Team attends. To keep it brief, it is recommended that everyone remain standing. It is the
team s opportunity to report to each other on progress and obstacles.
In the Daily Scrum, one by one, each member of the team reports three (and only three) things to
the other members of the team:
What they were able to get done since the last meeting;
What they are planning to finish by the next meeting
Any blocks or impediments that are in their way
Sprint Review Meeting
After the Sprint ends, there is the Sprint Review, where the team reviews the Sprint with the
Product Owner. The Sprint Review is an inspect and adapt activity for the product. It is a time for the Product
Owner to learn what is going on with the product and with the team; and for the team to learn what is going
on with the Product Owner and the market. The review includes a demo of what the team built during the
Sprint.
© Satyam 2009 14

15. FAQ s
Scrum is an agile process for developing software.
Scrum is an iterative, incremental framework.
With Scrum, projects progress via a series of iterations called sprints.
Sprints or Iterations are typically 1-4 weeks in length.
The Sprints are of fixed duration they end on a specific date whether the
work has been completed or not, and are never extended.
At the end of the Sprint, the team demonstrates what they have
accomplished.
Scrum Master abbreviated here as SM.
The list of requirements to be implemented is called a product backlog.
One cycle in the project life cycle is a sprint. Sprints last for 30 days.
The list of requirements to be worked in a particular sprint is a sprint backlog.
A daily status meeting is a daily scrum.
That accomplishments of the sprint are reviewed and demonstrated to the
customer at the end of each sprint.
Sprints are fixed duration work cycles.
© Satyam 2009 15
*

16. S cr u m Ba s ics
Key take away
Scrum is made up of three roles, three ceremonies and three
artifacts
Roles: The Product Owner, who is responsible for the business
value of the project; the Scrum Master, who ensures that the Scrum
team is functional and productive; and the self-organized team
Ceremonies: the sprint planning meeting, daily scrum meeting, and
sprint review meeting
Artifacts: the product backlog, the sprint backlog, and a burndown
chart
© Satyam 2009 16

17. References
http://infoq.com/minibooks/ scrum-xpfrom- the-trenches
www.sprint-it.de/scrum-checklists
Confessions of a serial product owner Based on a true story Anna Forss
Join Agile Alliance group @ Linkedin
Join Agile alliance charter CoP @ Oskar.satyam.com
Go to oskar.satyam.com ( give u r network id and password)
Select CoP-> join CoP
CoP Sites -> Agile Alliance
© Satyam 2009 17

18. Are you doing Scrum?
Do Nokia test
LEVEL 1
Iterations must be time-boxed to less than six weeks / Do your sprints start and end
on planned dates
Is the software completely tested and working at the end of an iteration
Can the iteration start before specification is complete
LEVEL 2
Does the team know who the product owner is
Is there a product backlog prioritized by business value
Does the product backlog have estimates created by the team
Does the team generate its burndown charts and knows its velocity
Does the team have outside people disrupting the work of the team during the sprint
© Satyam 2009 18

19. Thank you
Regards
prasad_prabhakaran@satyam.com
satyam.com
Safe Harbor
This document contains forward-looking statements within the meaning of section 27A of Securities Act of 1933, as amended, and
section 21E of the Securities Exchange Act of 1934, as amended. The forward-looking statements contained herein are subject to
certain risks and uncertainties that could cause actual results to differ materially from those reflected in the forward-looking
statements. Satyam undertakes no duty to update any forward-looking statements. For a discussion of the risks associated with our
business, please see the discussions under the heading Risk Factors in our report on Form 6-K concerning the quarter ended
September 30, 2008, furnished to the Securities and Exchange Commission on 07 November, 2008, and the other reports filed with
the Securities and Exchange Commission from time to time. These filings are available at http://www.sec.gov
© Satyam 2009 19

20. Ken Schwaber co-developed the Scrum process with Jeff Sutherland in the early
1990s to help organizations struggling with complex development projects. One of
the signatories to the Agile Manifesto in 2001, he subsequently founded the
AgileAlliance, a nonprofit organization dedicated to the creation of Agile software.
He then founded the ScrumAlliance, a nonprofit organization dedicated to expanding
the understanding of Scrum.
A 30-year veteran of the software development industry (from bottle washer to
boss), he has written three books about Scrum: Agile Software Development with
Scrum, Agile Project Management with Scrum, and The Enterprise and Scrum. He
lives in Lexington, Massachusetts with his family. His web site is
www.controlchaos.com.
© Satyam 2009 20

21. This document was created with Win2PDF available at http://www.win2pdf.com.
The unregistered version of Win2PDF is for evaluation or non-commercial use only.