wibas Scrum Browser


Summary

Scrum
is a project management framework for developing complex products and systems.
Scrum
employs a lean iterative and incremental approach with empirical process control.

Description

The heart of
Scrum
are iterations (called
Sprint
s) with a length of 2 - 4 weeks. All
Sprint
s use the same
Scrum
framework, and all
Sprint
s end with a
Potentially Shippable Product Increment
. The increment is a complete slice, or piece, of the finished product or system that is developed by the end of an iteration, or
Sprint
. One
Sprint
starts immediately after the prior
Sprint
ends.
Within each iteration,
Scrum
employs self-organizing, cross-functional
Team
s to optimize flexibility and productivity. The key roles are:
  • ScrumMaster
  • Product Owner
  • Team

Scrum
uses time boxes to create regularity. Elements of
Scrum
that are timeboxed are:
  • Release Planning
  • Sprint Planning 1
  • Sprint Planning 2
  • Sprint
  • Daily Scrum
  • Sprint Review
  • Sprint Retrospective

Scrum
uses four main artifacts:
  • Product Backlog
  • Sprint Backlog
  • Sprint Burn Down
  • Release Burn Down



Breakdown Structure

"wibas Scrum Browser" includes

Release Planning
The purpose of
Release Planning
is to establish a plan and goals that the
Scrum
Team
s and the rest of the organization can understand and communicate.
Sprint Planning 1
The purpose of
Sprint Planning 1
is that the
Product Owner
presents the
Product Backlog
with his prioritized requirements (user stories). After that the
Team
selects the items it can deliver in the next
Sprint
and a Sprint goal is defined.
Sprint Planning 2
The purpose of
Sprint Planning 2
is that the
Team
plans in detail, which tasks are necessary to fulfil the selected requirements (user stories).
Sprint
A
Sprint
is the time period in which development occurs on a set of backlog items that the
Team
has committed to.
Daily Scrum
The Purpose of
Daily Scrum
is to ensure communication and information flow inside the
Team
.
Sprint Review
The purpose of the
Sprint Review
is to present and demonstrate the
Sprint
result to the customer (
Product Owner
) or other relevant stakeholder and get the acceptance for delivered
Potentially Shippable Product Increment
.
Sprint Retrospective
The purpose of
Sprint Retrospective
is that the team documents the highlights, searches best practices and identifies improvement measures.