using class of service to manage product risk

Download Using Class of Service to Manage Product Risk

If you can't read please download the document

Upload: siddhi

Post on 16-Apr-2017

1.659 views

Category:

Technology


0 download

TRANSCRIPT

Using Class Of Service To Manage Product Risk

Siddharta [email protected]

Sreekanth [email protected]

This webinar is being recorded

Slides will be made available

Use #enterprisekanban to tag your tweets

Siddharta Govindaraj

Director, Silver Stripe Software Pvt Ltd

Email: [email protected]: @toolsforagile

Sreekanth Tadipatri

Senior Consultant, DeccanTech

Email: [email protected]: @bugbasher

Silver Catalyst

A tool for distributed agile development teams

Supports Scrum and Kanban

Silver Stories

A tool for cross-team product management

Currently in beta

Supports user story mapping and enterprise kanban

Agenda

Introduction

Types of Product Risk

Three Types of Features

Cost of Delay Model

Using Class of Service

Agenda

Introduction

Types of Product Risk

Three Types of Features

Cost of Delay Model

Using Class of Service

Companies Hoping to Do Well Have Little Choice but to Produce Radically Improved Products

New Product Continuum

Discontinuous (New to the world)

New consumption pattern

Radio, TV

Continuous (Incremental)

Same consumption pattern

Coffee to Decaf

The degree of product Newness

Newnessto the Company

Newness to the target customers

New-to-the-world

High

Low

Reduced Costs

Product

Repositioning

to Existing Product Lines

Products

20%

26%

10%

7%

26%

Low

High

11%

New

Product

Lines

Revisions / Improvements

Agenda

Introduction

Types of Product Risk

Three Types of Features

Cost of Delay Model

Using Class of Service

Functionality

Well Understood

High Uncertainty

Commodity

Market Risk

Tech Risk

Commodity

Market Risk

Tech Risk

For commodity projects, we need to focus on business value

For commodity projects, we need to focus on business value

For strategic projects, we need to focus on risk mitigation

To mitigate product risk, focus on learning

Market Risk: Make cheap prototypes and validate them with your target market

Technology Risk: Spike early to understand technical challenges

Don't (yet) worry about quality or delivering every sprint

Jeff Patton's Chess Analogy

Jeff Patton

Agenda

Introduction

Types of Product Risk

Three Types of Features

Cost of Delay Model

Using Class of Service

Basic

Performance

Excitement

Take pictures, browse and delete pictures, autofocus

File formats, camera modes, pre-set settings

Image quality, resolution, changable lens, underwater use

Agenda

Introduction

Types of Product Risk

Three Types of Features

Cost of Delay Model

Using Class of Service

Agenda

Introduction

Types of Product Risk

Three Types of Features

Cost of Delay Model

Using Class of Service

Expedite

Emergency Bug

Class of ServiceCriteria

ExpediteEmergency bug fixes that need to be fixed and deployed in a few days

Fixed DateFeatures that have a fixed deadline

High UncertaintyFeatures exposed to market or technical risk.

BasicBasic features from the Kano model

High ValueDifferentiating features from the Kano model

SlackIntangible, long term improvements, to be picked up during times of slack

NormalEverything else

Expedite

* Only for emergency bug fixes* Moves to the head of backlog and all queues* Can override work in progress limits* Team members stop whatever they are working on and swarm to complete this work item

High Uncertainty

* High market or technology risk* Skip automated test stage

High Value

* Requires user experience stage* Requires additional automated tests* Requires additional manual exploratory tests

Benefits

Better business development alignment

Risk oriented view of the backlog

Risk oriented view

What if you have many high uncertainty items on the backlog?

Risk oriented view

What is the mixture of basic, linear and differentiating work items?

Risk oriented view

Can we amortize highly risky features over a period of time by breaking them down into smaller pieces and tackle them one by one?

Risk oriented view

Should we balance a release containing a high uncertainty feature with well understood basic features?

Risk oriented view

What is the long term impact of having too many expedite requests?

Questions?

Siddharta GovindarajDirector, Silver Stripe Software Pvt Ltd

Email: [email protected]: @toolsforagile

Sreekanth TadipatriSenior Consultant, DeccanTech

Email: [email protected]: @bugbasher

@toolsforagile

[email protected]

facebook.com/ToolsForAgile

#enterprisekanban