Your SlideShare is downloading. ×
Failure and agility
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Failure and agility

962
views

Published on

Published in: Technology, Business

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
962
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Blaise Emmanuel Vignon Levi-ValensiStartup guy @ Microsoft France Founder/GM People in Action• Your contact for everything • Consultancy & agile web and startup mobile developmentBizspark: Lean and agile practicioner:• Software • Value driven• Support • Innovation• Visibility • User Experience• And more • And more@blaise_v @PIA_Emmanuel• Or blaisev@microsoft.com • Or elv@pia-conseil.com
  • 2. A sad statisticProportion of New BusinessesFounded 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)Source : Illusions of Entrepreneurship But not in the context of thisScott Shane (US Data, all industries) talk 
  • 3. The following slides were built with software engineering in mindSoftware engineering is• Highly creative• Very interdependant on coworkers• Loosely coupledIn 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
  • 4. The longer the project, the likelier the failure
  • 5. ….because it is the less clear what success looks like … 60% of project requirement changes 50 40 30 20 10 0 10 100 1000 10000 100000 Project size (measured in function points, yes, we know…)
  • 6. … and noiіse levels can get out of control… Undefined Anarchy Requirements ComplexWell defined Cutting edge Mature Technology (project environment in general)
  • 7. …but do we know why projects should be big? Only 20% of features are used often
  • 8. … and designing the wrong thing is easy…(we do not always know what the customer will look like)
  • 9. Project (and startup) management can be like this
  • 10. Inefficient way of workingThe « break-down and specialize »management method leads to many wastes:Stock of useless functionalities, High cost of coordinationdocumentation and communication
  • 11. Agility proposes a different management paradiіgm…Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan Source: http://agilemanifesto.org/
  • 12. Important Agile Principles Customer satisfaction Collective is the main goal commitment Measure to Intrinsic objectivize quality
  • 13. Agility proposes a different management paradiіgm…
  • 14. Agile way of delivering The Scrum process
  • 15. 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
  • 16. 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
  • 17. Agile MarketingImagine and Generate demandvalidate the MVPCu s t omer Cu s t omer Cu s t omer Companydis c over y Val idat ion c r eat ion bu il ding Validate market Accelerate! hypothesis
  • 18. Some great books…http://institut-agile.fr