Failure and Agility

24

description

Blaise Vignon of Microsoft and Emmanuel Levi-Valensi share the ins and outs of how to be Agile and when.

Transcript of Failure and Agility

Page 1: Failure and Agility
Page 2: Failure and Agility

Emmanuel Levi-Valensi

• Your contact for everything startup

Startup guy @ Microsoft France

• Software• Support• Visibility• And more

Bizspark:

• Or [email protected]

@blaise_v

Blaise Vignon

• Consultancy & agile web and mobile development

Founder/GM People in Action

• Value driven• Innovation• User Experience• And more

Lean and agile practicioner:

• Or [email protected]

@PIA_Emmanuel

Page 3: Failure and Agility

Failure and agility

Page 4: Failure and Agility

A sad statistic

Source : Illusions of EntrepreneurshipScott Shane (US Data, all industries)

Proportion of New Businesses Founded in 1992 Still Alive By Year. Most startup failures are

due to running out of money before having the right product

There can be other causes (WCR, founder shoutfest, litigation)

But not in the context of this talk

Page 5: Failure and Agility

The following slides were built with software engineering in mindSoftware engineering is• Highly creative• Very interdependant on coworkers• Loosely coupled

In short, it is like many other startup functions• Marketing• PR/Communication• Business Development• Product design

The learning from Software Engineering have been applied to broader fields

Page 6: Failure and Agility

The longer the project, the likelier the failure

Page 7: Failure and Agility

….because it is the less clear what success looks like …

0tan9a5

6609

0tan10a5

66010

0tan24a5

66224

0tan16a5

68716

0tan8a5

93480tan28a566028

0tan9a56609

0tan19a566019

0tan29a566029

0tan9a56609

0tan19a566019

0tan29a566029

Project size (measured in function points, yes, we know…)

% o

f pro

ject

requ

irem

ent c

hang

es

Page 8: Failure and Agility

… and noise levels can get out of control…

Undefined

Well defined

Requ

irem

ents

Technology(project environment in

general)

Mat

ure

Cutti

ng e

dge

Complicated

ComplexAnarchy

Page 9: Failure and Agility

…but do we know why projects should be big?

Only 20% of features are used

often

Page 10: Failure and Agility

… and designing the wrong thing is easy…

(we do not always know what the customer will look like)

Page 11: Failure and Agility

Project (and startup) management can be like this

Page 12: Failure and Agility

Inefficient way of working

The « break-down and specialize » management method leads to many wastes:

Stock of useless functionalities, documentation

High cost of coordination and communication

Page 13: Failure and Agility

Agility proposes a different management paradigm…

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Source: http://agilemanifesto.org/

Page 14: Failure and Agility

Important Agile Principles

Customer satisfaction is the main goal

Intrinsic quality

Measure to objectivize

Collective commitment

Page 16: Failure and Agility

Agile way of delivering The Scrum process

Page 17: Failure and Agility

Fail fast, fail early

• As we are delivering fast, we can harvest positive and negative feedbacks

• As we accept changes, we can take into account these feedbacks and adapt our plans

• Feedback is more precious than perfection

Page 18: Failure and Agility

Tips to accelerate failure (or success)

• Instead of building a full product or service, prototype it

• There are several prototype types:

Mechanical turk Pinocchio The Provincial The Minimal Viable Product

Page 19: Failure and Agility

Agile Marketing

Validate market hypothesis

Imagine and validate the MVP Generate demand

Accelerate!

Page 20: Failure and Agility

Some great books…

http://institut-agile.fr

Page 21: Failure and Agility

Utilisation

Char

ge

Temps

Utilisation

Périoded’inactivité

“On / Off “ Ch

arge

Temps

“Unpredictible load“

Utilisation

Utilisation

Char

ge

Temps

“Fast growth“

Char

geTemps

Utilisation

“predictible load“

Use a cloud … it tracks your need

Page 22: Failure and Agility

Use a cloud… it reduces waste

Page 23: Failure and Agility

Use a cloud … focus on your own work

Traditonal hosting

Stockage

Serveurs

Réseau

O/S

Middleware

Virtualisation

Données

Applications

Runtime

Vou

s gére

z

Cloud IaaSInfrastructur

e

Storage

Servers

Networking

O/S

Middleware

Virtualization

Data

Applications

Runtime

Géré

par l’o

péra

teur

Clo

ud

Vou

s gére

z

Cloud PaaS

Plateform

Vou

s gére

z

Storage

Servers

Networking

O/S

Middleware

Virtualization

Applications

Runtime

Data

Géré

par l’o

péra

teur

Clo

ud

• Dans le cadre d’un cloud privé, l’opérateur de Cloud, c’est vous• La gestion des couches « grises » est souvent automatisée au maximum

Page 24: Failure and Agility