Professional Documents
Culture Documents
Case Study
INFORMATION TECHNOLOGY
Product Backlog
The product backlog is a high-level document for the entire project. The set of features that go into a sprint come
from the product backlog, which is a prioritized set of high-level requirements of work to be done.
Sprint Backlog
The sprint backlog is a very detailed document containing information about how the team is going to implement the
requirements for the upcoming sprint. Which backlog items go into the sprint form product backlog is determined
during the sprint-planning meeting. During this meeting, the Product Owner informs the team of the items in the
product backlog that he wants completed.
The team determines how much of proposed backlog they can commit to complete during the sprint. During a sprint,
no one is able to change the sprint backlog, which means that the requirements are frozen for that sprint. After a sprint
is completed, the team demonstrates the use of the software.
SprintA
Sprint is a time-boxed period of time (quite often 30 days) during which the Team works to turn the selected Product
Backlog items into an increment of potentially demonstrable product functionality.
At the end of each sprint, team must produce demonstrate-able, release-able software. After just a few sprints,
the software is used in sales demonstrations. The product can be released to market early with only the highest
priority features.
INFORMATION TECHNOLOGY
SCRUM Roles
Product Owner
The Product Owner represents the voice of the customer. They ensure that the SCRUM Team works with the
prioritized backlog from a business perspective. The Product Owner writes User Stories, prioritizes them, and then
places them in the Product Backlog.
Scrum Master
(or Facilitator)A Scrum Master, whose primary job is to remove impediments to the ability of the team to deliver the
sprint goal, facilitates SCRUM. The Scrum Master is not the leader of the team (as they are self-organizing) but acts
as a buffer between the team and any distracting influences. The Scrum Master ensures that the SCRUM process is
used as intended. The Scrum Master is the enforcer of rules.
Team
The team has the responsibility to deliver the product. A small team (5-9 people) with cross-functional skills such as
designer, developer, tester, etc. to do the actual work.
The SCRUM Meeting
Each day during the sprint, a project status meeting occurs. This is called a SCRUM or "the daily standup". The
SCRUM has specific guidelines:
During the meeting, each team member answers three questions:
What have you done since yesterday?
What are you planning to do by today?
Do you have any problems preventing you from accomplishing your goal? (It is the role of the Scrum Master
to take a note of these impediments.)
At the end of every sprint cycle a sprint retrospective is held at which all team members reflect about the past sprint.
The purpose of the retrospective is to make continuous process improvement. Two main questions are asked in the
sprint retrospective:
What went well during the sprint?
What could be improved in the next sprint?
Mischievous Fact:
INFORMATION TECHNOLOGY
Advantage SCRUM
A higher-quality solution:
Improved communication between stakeholders and teams through regular demonstrations and the prioritized
product backlog
Testing being conducted throughout, rather than squeezed at the end
An on-schedule solution:
SCRUM enables the creation of self-organizing teams by encouraging communication across all team members
and disciplines that are involved in the project.
A release-able solution at the end of each sprint
In a nutshell, SCRUM provides a way for the business to maximize its ROI by using iterative development to rapidly
create working software. It ensures that the team is always working to deliver the highest priority features.
The SCRUM Approach - The Digital Experience
Improved Visibility: Uncovers many hidden issues that exist within teams in beginning such as Project & Task
estimation, Lack of product focus/priorities, Dependencies etc.
Increased Clarity & Communication: Force and clears product expectations between both product owner and
product team through dialogue.
Iterative innovation: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts
its behavior accordingly.
Increased Productivity, Improved Ownership & Accountability, Enhanced Planning, Improved Collaboration &
Cooperation, Focused Quality are few salient advantages Digital has experienced with SCRUM Implementation.
Level