W w w. n e s s. c o m Introduction to SCRUM. w w w. n e s s. c o m “The problem we face has...

w w w . n e s s . c o m

Introduction to SCRUM


“The problem we face has nothing to do with process and technology, but with people.

Scrum and Agile are based on the hypothesis that there is no meta-solution for software development. Just a framework within which we will be empirical – inspect and adapt.

This is very frustrating to those looking for procedures and final answers.”

- Ken Schwaber


Agile Manifesto

A Statement of ValuesIndividuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Source : www.agilemanifesto.org


Iterative development


SCRUM

A play in Rugby in which the two sets of forwards mass together around the ball and, with their heads down, struggle to gain possession of the ball.


•Scrum is an agile process that allows us to focus on

delivering the highest business value in the shortest time.

•It allows us to rapidly and repeatedly inspect actual

working software (every two weeks to one month).

•The business sets the priorities. Teams self-organize to

determine the best way to deliver the highest priority

features.

•Every two weeks to a month anyone can see real working

software and decide to release it as is or continue to

enhance it for another sprint.

SCRUM in 100 Words


New product classNo proven models

Incremental model with rapid feedback a necessity

Hyper-productive development environmentDevelopment far out-paced planning and testing

Solution:Apply an empirical process

Apply lean value chain analysis methods to optimize test and planning functions

Create cross-functional team to optimize communication and collaboration

The First Scrum


What is SCRUM?


What is SCRUM?


Scrum framework

•Product owner•ScrumMaster•Team

Roles

•Sprint planning•Sprint review•Sprint retrospective•Daily scrum meeting

Ceremonies

•Product backlog•Sprint backlog•Burndown charts

Artifacts


Sprints

• Scrum projects make progress in a series of “sprints”

• Analogous to Extreme Programming Iterations

• Typical duration is 2–4 weeks or a calendar month at most

• A constant duration leads to a better rhythm

• Product is designed, coded, and tested during the sprint


Sequential vs. Overlapping Development

Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986.

Rather than doing all of one thing at a time... ...Scrum teams do a

little of everything all the time

Requirements Design Code Test


No changes during a sprint

• Plan sprint durations around how long you can commit to keeping change out of the sprint

Change


Scrum Framework - Roles


Ceremonies


Artifacts


Roles


Product owner

• Define the features of the product

• Decide on release date and content

• Be responsible for the profitability of the product (ROI)

• Prioritize features according to market value

• Adjust features and priority every iteration, as needed

• Accept or reject work results


The ScrumMaster

• Represents management to the project

• Responsible for enacting Scrum values and practices

• Removes impediments

• Ensure that the team is fully functional and productive

• Enable close cooperation across all roles and functions

• Shield the team from external interferences


Resolves obstacles

Monitors the process

The ‘driver’ of the Team

Keeps the Team moving

Responsible for the team functioning

Scrum Master Role

25


Meetings

Artifacts

Coaching

Working with the Product Owner

Activities of a Scrum Master

26


SCRUM Team

• Typically 5-9 people

• Cross-functional:

• Programmers, testers, user experience designers, etc.

• Members should be full-time

• May be exceptions (e.g., database administrator)

• Teams are self-organizing

• Ideally, no titles but rarely a possibility

• Membership should change only between sprintsInvolved from conception to releaseEqual treatment and respect for all


Scrum Ceremonies


Roles


Artifacts

•Sprint planning•Daily scrum meeting

•Sprint review•Sprint retrospective

Ceremonies


Sprint Planning


2-5 WEEKS

2-3 DAYS(PLANNING)

RECAP,DEMO,

RETROSPECTIVE,RELEASE,KICK-OFF

Sprint


Sprint planning meeting

Sprint prioritization• Analyze and evaluate

product backlog• Select sprint goal

Sprint planning

• Decide how to achieve sprint goal (design)

• Create sprint backlog (tasks) from product backlog items (user stories / features)

• Estimate sprint backlog in hours

Sprintgoal

Sprintgoal

SprintbacklogSprint

backlog

Business conditionsBusiness

conditions

Team capacityTeam

capacity

Product backlogProduct backlog

Technology

Technology

Current productCurrent product

Sprint Planning


Initiated through ITIL/CAB, PMO or ad-hoc processes

Internally generated requests

Customer driven

Market driven

Describe what your doing and why your doing itCustomer need and/or market assessment

Business case

High-level use cases, requirements, episodes …

Level of formality will vary based on value/cost of the request

May involve a formal approval processes

Conception


The Sprint Goal

A short statement of what the work will be focused on during the sprint

Database Application

Financial services

Life Sciences

Support features necessary for population genetics studies.

Support more technical indicators than company ABC with real-time, streaming data.

Make the application run on SQL Server in addition to Oracle.


Managing the Sprint Backlog

• Individuals sign up for work of their own choosing

• Work is never assigned

• Estimated work remaining is updated daily

• Any team member can add, delete or change the sprint backlog

• Work for the sprint emerges

• If work is unclear, define a sprint backlog item with a larger amount of time and break it down later

• Update work remaining as more becomes known


Activity: Sprint Planning meeting

Goal of Sprint Planning Meeting:For the team to make a good commitment around what it will deliver by the end of the Sprint

What’s a good commitment?Clearly understood by allShared among the teamAchievable without sacrificing qualityAchievable without sacrificing sustainable pace

Attended by Team, Product Owner, Scrum Master, StakeholdersMay require 1-2 hours for each week of Sprint duration


Product Owner prioritizes featuresIdentifies key external milestones and business commitments

Resource capacity plan is developed for the project

Each backlog item is estimatedHigh-level estimates (+/- 50% accuracy)

Team selects items from the product backlog they can commit to completing

Effort is compared to resource capacity and an initial burndown is projected

At the completion of Sprint 0, a release plan review is performed and the first sprint is kicked-off

Activity: Sprint Planning Meeting


As a vacation planner, I want to see photos of the hotels.

As a vacation planner, I want to see photos of the hotels.

Code the middle tier (8 hours)Code the user interface (4)Write test fixtures (4)Code the foo class (6)Update performance tests (4)

Activity: Sprint Planning Meeting


The backlog items are elaboratedUser Stories

Interaction design / screen flows

Feature content, release targets, capacity are re-calibrated by the Project Leads

Sprint is kicked-off with a team meeting to review and discuss goals

Sprint Definition and PlanningActivity: Sprint Planning Meeting


Feature content, release targets, capacity are continuously reviewed/discussed/debated

Key participants: Scrum Master and Product Owner

This is where the term Scrum came fromAt times, the process can be brutal, but in the end a try can be scored

Incremental Planning


Daily Scrum


The Daily Scrum

• Parameters

• Daily

• 15-minutes

• Stand-up

• Not for problem solving

• Whole world is invited

• Only team members, ScrumMaster, product owner, can talk

• Helps avoid other unnecessary meetings


Team meeting every day at the same time in the same place

Everyone attends – Development, Test, Product Owner

Led by the Scrum Master (Project Manager)

<15mins

Each member quickly reviews new accomplishments, next tasks, and raises any impediments

Impediments resolved offline!

Whiteboards – the more the better

The Daily Stand-Up


Everyone answers 3 questions

• These are not status for the ScrumMaster• They are commitments in front of peers

What did you do yesterday?What did you do yesterday?11

What will you do today?What will you do today?22

Is anything in your way?Is anything in your way?33


Sprint Review


The Sprint Review

• Team presents what it accomplished during the sprint

• Typically takes the form of a demo of new features or underlying architecture

• Informal

• 2-hour prep time rule

• No slides

• Whole team participates

• Invite the world


Sprint Retrospective


Sprint Retrospective

• Periodically take a look at what is and is not working

• Typically 15–30 minutes

• Done after every sprint

• Whole team participates

• ScrumMaster

• Product owner

• Team

• Possibly customers and others


Start / Stop / Continue

• Whole team gathers and discusses what they’d like to:

Start doingStart doing

Stop doingStop doing

Continue doing

Continue doing

This is just one of many ways to do a sprint retrospective.


Scrum Artifacts


Roles


Ceremonies


Artifacts


Product backlog

• The requirements

• A list of all desired work on the project

• Ideally expressed such that each item has value to the users or customers of the product

• Prioritized by the product owner

• Reprioritized at the start of each sprint

This is the product backlog

This is the product backlog


Artifact: Product Backlog

List of everything that could ever be of value to the business for the team to produce

Ranked in order of priority

Priority is a function of ROI and risk

Product Owner can make any changes they want before the start of a Sprint Planning Meeting

Items added, changed, removed, reordered

The farther down the list, the bigger and less defined the items become

~2 Sprints worth are defined in detail


Artifact: Product Backlog


A Sample Product Backlog

Backlog item Estimate

Allow a guest to make a reservation 3

As a guest, I want to cancel a reservation. 5

As a guest, I want to change the dates of a reservation.

3

As a hotel employee, I can run RevPAR reports (revenue-per-available-room)

8

Improve exception handling 8

... 30

... 50


A Sprint Burn Down ChartR

em

ain

ing

Hou

rs


SCRUM Issues: Scalability

• Typical individual team is 7 ± 2 people

• Scalability comes from teams of teams

• Factors in scaling

• Type of application

• Team size

• Team dispersion

• Project duration

• Scrum has been used on multiple 500+ person projects


Scaling through the Scrum of Scrums


Scrum of scrums of scrums


Artifact: Sprint Backlog

1. Product Owner, Team, and other Stakeholders talk through Product Backlog Items and prioritization

2. Team determines how much time it has available to Commit during the Sprint

3. Team selects as much of the Product Backlog as it can commit to deliver by the end of the Sprint, and turns it into a plan

3 Simple steps


Artifact: Burn Down Chart

Electronic may look more convenient for the Sprint Backlog and Burn Down Charts, but...• Paper is fast and easy • Paper is much more visible • Paper doesn’t “go down”


Scrum Disadvantages

Makes all dysfunction visibleScrum doesn’t fix anything: the team has to do it

May feel like things are worse at the beginning

Bad products will be delivered sooner

Doomed projects will fail faster

High risk of turnoverSome people will refuse to stay on a Scrum team

Partial adoption may be worse than none at all

If adoption fails, time will have been wasted, and some people may leave


Where to go next

• www.mountaingoatsoftware.com/scrum

• www.scrumalliance.org

• www.controlchaos.com

• [email protected]


Any Questions?

Thank You!

Date post:	22-Dec-2015
Category:	Documents
View:	220 times
Download:	0 times

W w w. n e s s. c o m Introduction to SCRUM. w w w. n e s s. c o m “The problem we face has...

Documents