The Scrum cycle begins with a Stakeholder Meeting, during which the Project Vision 

is created. The
Product Owner then develops a Product Backlog which contains a prioritized list of business and project
requirements written in the form of User Stories.

Product Backlog
Using Scrum, we always do the most valuable work first. The product owner is
responsible for determining and managing the sequence of this work and
communicating it in the form of a prioritized list known as the product backlog.

On new-product development the product backlog items initially are features

required to meet the product owner’s vision.
For ongoing product development, the product backlog might also contain new
features, changes to existing features, defects, needing repair, technical
improvements, etc.
The product owner collaborates with internal and external stakeholders to gather and
define the product backlog items.
Overall the activity of creating and refining product backlog items, estimating them,
and prioritizing them is known as grooming.
Size equates to cost, and product owners need to know an item’s cost to properly
determine its priority. In practice, many teams use a relative size measure such
as story points or ideal days.

Sprint Planning:
The Sprint Planning Meeting is attended by the Product Owner (voice of the customer), Scrum Master and
the Development Team.

The work to be performed in the Sprint is planned at the Sprint Planning.

During sprint planning, the product owner,scrum master or development team agree on
a sprint goal that defines what the current sprint is supposed to achieve.

The Sprint
During a Sprint, a working product Increment is developed. It is usually
of duration two weeks or one month, and this duration remains constant
for all the sprints in the project. We cannot have varying durations for
the different sprints in a project. A new Sprint starts immediately after
the conclusion of the previous Sprint.

A Sprint generally lasts between one and six weeks and involves the Scrum Team working to create
potentially product increments.
During the Sprint, short, highly focused Daily Standup Meetings are conducted where team members
discuss daily progress.

Toward the end of the Sprint, a Sprint Review Meeting is held during which the Product Owner and
relevant stakeholders are provided a demonstration of the Deliverables. The Product Owner accepts the
Deliverables only if they meet the predefined Acceptance Criteria. The Sprint cycle ends with a Retrospect

Sprint Meeting where the team discusses ways to improve processes and performance as they move
forward into the subsequent Sprint.

Sprint artifacts and their components include:

 Product Backlog—Everything, both technical and user-centric, that

must be completed within a project.
 Sprint Backlog—The set of all tasks to be completed within a sprint
iteration. These are taken from the Product Backlog during the Sprint
Planning Meeting.
 Product Backlog Item—An item from the Product Backlog that is to be
completed within a sprint iteration. It is usually broken down into a few
smaller tasks.
 Sprint Task—What you do to deliver a Product Backlog Item.

Daily Scrum
Each day of the sprint, ideally at the same time, the development team members
hold a timeboxed (15 minutes or less) daily scrum. This inspect-and adapt activity is
sometimes referred to as the daily stand-up because of the common practice of
everyone standing up during the meeting to help promote brevity.
A common approach to performing the daily scrum has the ScrumMaster facilitating
and each team member taking turns answering three questions for the benefit of the
other team members:

 What did I accomplish since the last daily scrum?

 What do I plan to work on by the next daily scrum?
 What are the obstacles or impediments that are preventing me from making
progress?

Daily Scrum Meeting—A Scrum meeting that takes place daily during a sprint.
They are brief and are intended to plan the development team’s activity for the
day.  This is the place for discussing obstacles encountered or confusion over
a user story. The meeting is presided over by the Scrum Master and attended
by the development team.
Sprint Review—The Sprint Review is a demonstration of the working product
developed during the sprint. This meeting occurs at the end of the sprint and is
primarily used to provide stakeholders a detailed look at what was
accomplished.

Sprint Retrospective—The Sprint Retrospective is a post-mortem to discuss

how the team did during the sprint and how it can improve its performance in
the future.