Scrum

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

An incremental and iterative project management framework

Scrum is an agile development methodology. The development is organized in cycles, in Scrum these cycles are called sprints. The length of a sprint is defined for a project and lasts usually between two and four weeks. During a sprint the team develops the most important customer requirements from a prioritized list. Thus, the functions that have the highest benefits for the customer are implemented first. At the end of each sprint, the team delivers the potentially shippable product increment and customer requirements can be changed or reprioritized for the next sprint.

Introducing Agile/Scrum means to achieve high benefits for customers with simple means

Scrum defines a minimal set of process elements that make up a Sprint. Scrum defines three roles (roles), three activities (ceremonies) and three types of results (artifacts).

Roles:

  • The ScrumMaster is responsible for facilitating Scrum. The ScrumMaster does not organize the team or its tasks. He facilitates the team by coaching, teaching and supporting it.
  • The Product Owner is responsible for the features and the ROI of the product.
  • The responsibility of the Team is to deliver the Potentially Shippable Product Increment each Sprint. Teams are self-organizing and cross-functional.

Ceremonies:

  • The purpose of Sprint Planning 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.
  • The Purpose of the Daily Scrum Meeting is to review the status in the Team to ensure communication and information flow inside the Team. Each team member answers the three questions "Waht did I do yesterday?", "What will I do today" and "Are there any impediments?".
  • 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.

Artifacts:

  • The purpose of a Product Backlog is to provide a prioritized list of all features (user stories) that cover all important details, which a customer (Product Owner) wants to have in a product.
  • The purpose of Sprint Backlog is to cover all selected backlog items which the Team will complete in the upcoming Sprint and give their commitment to. In the Sprint Backlog the Team the plans the required tasks to implement the selected backlog items.
  • The purpose of the Sprint Burn Down is to publicly display the remaining work of the current Sprint. If the Sprint Backlog is updated every day, it gives a simple view of the sprint progress, on a daily basis.

More information on Scrum:

Icon This article as PDF (196.7 KB)

Do you have questions?
portrait
Yvonne Fischer

Director General Operations


+49 6151 503349-21

[protected email]

[protected email]

Our next trainings:
25.4.
Certified Scrum Master
×
Certified Scrum Master
  • Trainer: Sascha Gessler
  • Language: German
  • City/Duration: Darmstadt, Germany, 2 days
25./26.April
17.5.
Certified Scrum Product Owner
×
Certified Scrum Product Owner
  • Trainer: Malte Foegen
  • Language: German
  • City/Duration: Darmstadt, Germany, 2 days
17./18.May
30.5.
Certified Scrum Master
×
Certified Scrum Master
  • Trainer: Sascha Gessler
  • Language: German
  • City/Duration: Darmstadt, Germany, 2 days
30./31.May
4.7.
Certified Scrum Product Owner
×
Certified Scrum Product Owner
  • Trainer: Malte Foegen
  • Language: German
  • City/Duration: Darmstadt, Germany, 2 days
4./5.July
Do you have questions?
portrait
Yvonne Fischer

Director General Operations


+49 6151 503349-21

[protected email]

[protected email]