LIFECYCLE OF SCRUM:
• Sprint:
A Sprint is a time-box of one month or less. A new Sprint starts
immediately after the completion of the previous Sprint.
• Release:
When the product is completed then it goes to the Release stage.
• Sprint Review:
If the product still have some non-achievable features then it will be
checked in this stage and then the product is passed to the Sprint
Retrospective stage.
• Sprint Retrospective:
In this stage quality or status of the product is checked.
• Product Backlog:
According to the prioritize features the product is organized.
• Sprint Backlog:
Sprint Backlog is divided into two parts Product assigned features to
sprint and Sprint planning meeting.
HOW SCRUM WORKS
• In a rugby scrum, all the players literally put their heads together. When it comes to software
development, a scrum can be characterized by
developers putting their heads together to address complex problems.
• Scrum software development starts with a wish list of features — a.k.a. a product backlog. The team
meets to discuss:
• The backlog.
• What still needs to be completed.
• How long it will take.
• Scrum relies on an agile software development concept called sprints:
• Sprints are periods of time when software development is actually done.
• A sprint usually lasts from one week to one month to complete an item from the backlog.
• The goal of each sprint is to create a saleable product.
• Each sprint ends with a sprint review.
• Then the team chooses another piece of backlog to develop — which starts a new sprint.
• Sprints continue until the project deadline or the project budget is spent.
• In daily scrums, teams meet to discuss their progress since the previous meeting and make plans for that
day.
• The meetings should be brief — no longer than 15 minutes.
• Each team member needs to be present and prepared.
HOW SCRUM WORKS
INTRODUCTION TO SCRUM TERMS
• An introduction to Scrum would not be complete without knowing the Scrum
terms you'll be using. This section in the Scrum overview will discuss common
concepts in Scrum.
• Scrum team: A typical scrum team has between five and nine people, but Scrum
projects can easily scale into the hundreds. However, Scrum can easily be used
by one-person teams and often is. This team does not include any of the
traditional software engineering roles such as programmer, designer, tester or
architect. Everyone on the project works together to complete the set of work
they have collectively committed to complete within a sprint. Scrum teams
develop a deep form of camaraderie and a feeling that “we’re all in this together.”
WHO IS IN THE SCRUM?/SCRUM TERMS
• Product owner: The product owner is the project’s key stakeholder and represents users,
customers and others in the process. The product owner is often someone from product
management or marketing, a key stakeholder or a key user.
• Scrum Master: The Scrum Master is responsible for making sure the team is as productive
as possible. The Scrum Master does this by helping the team use the Scrum process, by
removing impediments to progress, by protecting the team from outside, and so on.
• Product backlog: The product backlog is a prioritized features list containing every desired
feature or change to the product. Note: The term “backlog” can get confusing because it’s
used for two different things. To clarify, the product backlog is a list of desired features for
the product. The sprint backlog is a list of tasks to be completed in a sprint.
