Scribd
Upload
47 views3 pages

Scrum Theory

Scrum is an iterative and incremental framework based on empirical process control theory. The three pillars of transparency, inspection, and adaptation come to life when teams embody the Scrum values of commitment, courage, focus, openness and respect. A self-organizing cross-functional Scrum Team consists of a Product Owner, Development Team, and Scrum Master, with the Development Team delivering working software increments in each sprint through daily 15-minute stand-up meetings called Daily Scrums.

Uploaded by

arifa_136
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
47 views3 pages

Scrum Theory

Scrum is an iterative and incremental framework based on empirical process control theory. The three pillars of transparency, inspection, and adaptation come to life when teams embody the Scrum values of commitment, courage, focus, openness and respect. A self-organizing cross-functional Scrum Team consists of a Product Owner, Development Team, and Scrum Master, with the Development Team delivering working software increments in each sprint through daily 15-minute stand-up meetings called Daily Scrums.

Uploaded by

arifa_136
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Scrum Theory

Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that
knowledge comes from experience and making decisions based on what is known. Scrum
employs an iterative, incremental approach to optimize predictability and control risk.

Three pillars uphold every implementation of empirical process control: transparency,


inspection, and adaptation.

Scrum Values
When the values of commitment, courage, focus, openness and respect are embodied and lived by
the Scrum Team, the Scrum pillars of transparency, inspection, and adaptation come to life and build
trust for everyone. The Scrum Team members learn and explore those values as they work with the
Scrum roles, events, and artifacts.

Successful use of Scrum depends on people becoming more proficient in living these five values.
People personally commit to achieving the goals of the Scrum Team. The Scrum Team members have
courage to do the right thing and work on tough problems. Everyone focuses on the work of the
Sprint and the goals of the Scrum Team. The Scrum Team and its stakeholders agree to be open
about all the work and the challenges with performing the work. Scrum Team members respect each
other to be capable, independent people.

The Scrum Team


The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. Scrum
Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish
their work, rather than being directed by others outside the team. Cross-functional teams have all
competencies needed to accomplish the work without depending on others not part of the team.
The team model in Scrum is designed to optimize flexibility, creativity, and productivity. The Scrum
Team has proven itself to be increasingly effective for all the earlier stated uses, and any complex
work.

Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for
feedback. Incremental deliveries of “Done” product ensure a potentially useful version of
working product is always available.

The Development Team


The Development Team consists of professionals who do the work of delivering a potentially
releasable Increment of “Done” product at the end of each Sprint. A “Done” increment is
required at the Sprint Review. Only members of the Development Team create the Increment.

Development Teams are structured and empowered by the organization to organize and
manage their own work. The resulting synergy optimizes the Development Team’s overall
efficiency and effectiveness.
Development Teams have the following characteristics:

• They are self-organizing. No one (not even the Scrum Master) tells the Development Team how
to turn Product Backlog into Increments of potentially releasable functionality;
• Development Teams are cross-functional, with all the skills as a team necessary to create a
product Increment;
• Scrum recognizes no titles for Development Team members, regardless of the work being
performed by the person;
• Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to
be addressed like testing, architecture, operations, or business analysis; and,
• Individual Development Team members may have specialized skills and areas of focus, but
accountability belongs to the Development Team as a whole.

Daily Scrum
The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum is held
every day of the Sprint. At it, the Development Team plans work for the next 24 hours. This optimizes
team collaboration and performance by inspecting the work since the last Daily Scrum and
forecasting upcoming Sprint work. The Daily Scrum is held at the same time and place each day to
reduce complexity.

The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to
inspect how progress is trending toward completing the work in the Sprint Backlog. The Daily Scrum
optimizes the probability that the Development Team will meet the Sprint Goal. Every day, the
Development Team should understand how it intends to work together as a self- organizing team to
accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint.

The structure of the meeting is set by the Development Team and can be conducted in different
ways if it focuses on progress toward the Sprint Goal. Some Development Teams will use
questions, some will be more discussion based. Here is an example of what might be used:

• What did I do yesterday that helped the Development Team meet the Sprint Goal?
• What will I do today to help the Development Team meet the Sprint Goal?
• Do I see any impediment that prevents me or the Development Team from meeting the
Sprint Goal?

The Development Team or team members often meet immediately after the Daily Scrum for
detailed discussions, or to adapt, or replan, the rest of the Sprint’s work.

The Scrum Master ensures that the Development Team has the meeting, but the Development
Team is responsible for conducting the Daily Scrum. The Scrum Master teaches the Development
Team to keep the Daily Scrum within the 15-minute time-box.

The Daily Scrum is an internal meeting for the Development Team. If others are present, the
Scrum Master ensures that they do not disrupt the meeting.
Daily Scrums improve communications, eliminate other meetings, identify impediments to
development for removal, highlight and promote quick decision-making, and improve the
Development Team’s level of knowledge. This is a key inspect and adapt meeting.

You might also like