Scribd
Upload
142 views11 pages

An Introduction - The Zen of Scrum

This document provides an introduction to the Scrum framework for agile software development. Scrum uses self-organizing cross-functional teams, sprints of 2 weeks or less to incrementally develop products, and emphasizes transparency, inspection, and adaptation. Key Scrum roles include the Product Owner, Scrum Master, and Development Team. Scrum ceremonies include sprint planning, daily standups, sprint reviews, and retrospectives. Artifacts include the Product Backlog, Sprint Backlog, and burn down charts. The goal of Scrum is to help teams deliver value to customers and continuously improve.

Uploaded by

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

An Introduction - The Zen of Scrum

This document provides an introduction to the Scrum framework for agile software development. Scrum uses self-organizing cross-functional teams, sprints of 2 weeks or less to incrementally develop products, and emphasizes transparency, inspection, and adaptation. Key Scrum roles include the Product Owner, Scrum Master, and Development Team. Scrum ceremonies include sprint planning, daily standups, sprint reviews, and retrospectives. Artifacts include the Product Backlog, Sprint Backlog, and burn down charts. The goal of Scrum is to help teams deliver value to customers and continuously improve.

Uploaded by

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

An Introduction The Zen of Scrum

What is the problem?

Requirements not clear Scope Creep Changes are hard to make Cost schedule over run Loss of reputation and market

Frequent Code Changes Stabilisation takes too long Quality is falling Customer dissatisfaction

Bug Find Fix syndrome Releases take too long Unpredictable time lines Loss of morale and motivation

Characteristics

Self-organizing teams Product progresses in a series of sprints (usually 2 weeks, sometimes month long) Requirements are captured as items in a list of product backlog (user stories) No specific engineering practices prescribed Uses generative rules to create an agile environment for delivering projects One of the agile processes

Scrum framework
Roles

Product owner ScrumMaster Team Ceremonies Sprint planning Sprint review Sprint retrospective Daily scrum meeting
Artifacts

Product backlog Sprint backlog Burndown charts

Putting it all together

Team capacity

Sprint planning meeting


Sprint prioritization

Product backlog

Analyze and evaluate product

backlog Select sprint goal

Sprint goal

Business conditions

Sprint planning

Current product

Technology

Decide how to achieve sprint goal (design) Create sprint backlog (tasks) from product backlog items (user stories / features) Estimate sprint backlog in hours

Sprint backlog

The daily scrum Everyone answers 3 questions

What did you do yesterday? What will you do today? Is anything in your way?

15-minutes Stand-up

1 2

Not for problem solving; Only team members, Scrum Master, product owner, can talk

The sprint review

Team presents what it accomplished

Whole team participates Invite the world

during the sprint Typically takes the form of a demo of new features or underlying architecture Informal
2-hour prep time rule No slides

Sprint retrospective

Periodically take a look at what is and is not working 30 - 60 minutes Done after every sprint Whole team participates

Scrum Master Product owner Team

Scrum Process Analysis: How How can we improve ourselves?


Inspection priorities : Team communication Relationship between team members Processes and Tools Training issues etc

ARTIFACTS

Presentation by: Ulhas Rao [email protected]

A Scrum reading list Agile Project Management with Scrum by Ken Schwaber
Succeeding with Agile by Mike Cohn

Adapted and based on Mike Cohn presentation

You might also like