How Scrum Works: Pashun Consulting Limited

How Scrum works
Pashun Consulting Limited
Pashun Consulting
www.freescrumebook.com
How Scrum works

Chapters:
1. Introducing Scrum
What is Scrum
Theory
Roles, Artifacts, Rules and Practices
2. Overview
Root Cause analysis

Stakeholders
Scrum Master, Product Owner and Team
Product Backlog
Release Planning Meeting
Sprint
Sprint Planning Meeting

Daily Scrums
Deliver Working Increment
Sprint Review
Sprint Retrospective
Sprint and release Burndown
Pashun Consulting
Waterfall Model
Pashun Consulting
Common Issues
Vague requirements not tied down
Unrealistic expectations (deadlines,
estimates, scope)
Changing requirements too often / Scope
creep
Defects/Issues hamper progress
Disappearing Resources (people pinching)
Support issues impact project work
Pashun Consulting
Introducing Scrum
Founders of Scrum
Developed by Ken Schwaber and Jeff Sutherland
What is Scrum
an Agile process that can be used to manage and
control complex software and product development
using iterative, incremental practices
Self organizing cross functional teams
Working in Iterations:
Allows business flexibility to change requirements
Gives development team certainty within iteration
Pashun Consulting
Scrum Theory
Based on Empirical Process Control Theory
iterative
incremental
Consists of 3 principles
1. Transparency (done means done)
2. Inspection
(check on progress)
3. Adaptation
(change the product based on inspection)
Pashun Consulting
The Scrum Skeleton
Pashun Consulting
Scrum Roles, Rules, Timeboxes

and Artifacts
Roles
Rules and Time Boxes
Scrum Master
Product Owner
Team
Sprint
Sprint Review
Daily Scrum
Artifacts
Product Backlog
Sprint Backlog
Increment of Potentially
Shippable Product
Functionality
Pashun Consulting
Establish Scrum Master, Product

Owner and Team
Scrum Master
Product Owner
Understands scrum rules and

practices.
Responsible for removing
impediments to delivery and
Helps team understand how
to self organize and work in a
Scrum manner.
Creates requirements on
behalf of business
Prioritizes as per business
needs
Responsible for managing
product backlog
Team
Create each increment of shippable product

Self organizing
Collaborative
Optimum size of 7 plus or minus 2
Skilled in whatever is needed for project eg. design, Java, sql, information
architecture
Pashun Consulting
Build Initial Product Backlog

Feature from a User's perspective
As a User
I want a News Page
So that I can see the top 10 news stories
User Story
Pashun Consulting
Build Initial Product Backlog
Organise Stakeholder meetings

Negotiate between stakeholders
Find common ground
Manage Changing requirements as needed
Customer
Final Product Vendor
Product Backlog
CEO
Director/Head of dept.
Pashun Consulting
Release Planning Meeting

Note: Release Planning is not an official event in scrum but still
recommended for complex projects.
select items from product backlog

prioritised for first release
give high level estimates for each
item (complexity points or ideal days)
Release backlog is created
Release Backlog
(subset of product backlog)
Product Backlog
Pashun Consulting
Release Burn Down
Sprints
Pashun Consulting

Prioritised selection of items chosen from release backlog
The team break the items (stories) into sub tasks
Sub tasks are given estimates (hours) and stories also given
estimates (complexity points/ideal days)
Agree velocity
Pick stories that fit into velocity
Estimates and stories form Sprint backlog
+
Subtasks
Release Backlog
(subset of product backlog)
Pashun Consulting
Sprint Backlog
(subset of release backlog with sub tasks)
Sprint
1week 30days
Cannot change items in sprint backlog
Team works on tasks from Sprint Planning meeting
Aim to complete all tasks (and therefore items in backlog)
Any items not completed are rolled over to next sprint
+
Subtasks
Sprint Backlog
(subset of release backlog with sub tasks)
Pashun Consulting
Team
Daily Scrum
Whole team attends

Meeting held in same spot daily
Scrum master facilitates
One person speaks at a time
Burndown and sprint backlog are visible
What
WhatI Iaim
aimto
to
do
dotoday
today
What
WhatI Idid
did
yesterday
yesterday
I Ihave
havethe
the
following
following
impediments
impediments
Team
Pashun Consulting
Sprint Burn Down
Pashun Consulting
Sprint Review
Demo of the sprints functionality

Stakeholders present
Product owner and Stakeholders discuss backlog
Stakeholders ask questions
CEO
Product owner
Customer
Final Product Vendor

Director/Head of dept.
Pashun Consulting
Team
Scrum Master
Working Increment
Deployable to the live system (potentially shipable)
Collection of all features in the sprint
Pashun Consulting
What went well this sprint?
What could we improve next sprint?
Dev Environment, working practices, communication
Product owner
Team
Pashun Consulting
Scrum Master
How Scrum works
Thanks for your time
Any Questions ?
Pashun Consulting
Pashun Consulting

How Scrum Works: Pashun Consulting Limited

Uploaded by

Copyright:

Available Formats

How Scrum Works: Pashun Consulting Limited

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

How Scrum Works: Pashun Consulting Limited

Uploaded by

Copyright:

Available Formats

How Scrum works

Pashun Consulting Limited

How Scrum works

Root Cause analysis

Sprint Planning Meeting

The Scrum Skeleton

Scrum Roles, Rules, Timeboxes

Rules and Time Boxes

Establish Scrum Master, Product

Understands scrum rules and

Create each increment of shippable product

Build Initial Product Backlog

Build Initial Product Backlog

Organise Stakeholder meetings

Final Product Vendor

Release Planning Meeting

select items from product backlog

Release Burn Down

Sprint Planning Meeting

Whole team attends

Sprint Burn Down

Demo of the sprints functionality

Final Product Vendor

How Scrum works

Thanks for your time

You might also like