ExumaTech Dev Process

572 views
509 views

Published on

Over the past couple of years we've migrated from a traditional, waterfall development process to more of an iterative one. At the same time we've moved from structured to object oriented programming languages. These are big transitions and we are proud to say that we've released our first .NET product built on an object oriented framework.

We have recently adopted the Lean Start-up Process first introduced by Eric Ries. This is a presentation I gave at our customer advisory board meeting that was adapted from Eric's presentation found here:

http://www.slideshare.net/startuplessonslearned/eric-ries-lean-startup-presentation-for-web-20-expo-april-1-2009-a-disciplined-approach-to-imagining-designing-and-building-new-products

Find us at http://exumatech.com or @ExumaTech

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
572
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

ExumaTech Dev Process

  1. 1. ExumaTechDevelopment Process
  2. 2. Traditional Product DevelopmentProblem: Solution:Known Known
  3. 3. Common Misconceptions• We know what customers want (Problem)• We know how to solve it (Solution)• Advancement is progress
  4. 4. Traditional Product DevelopmentProblem: Solution:Known Known
  5. 5. Commercial Software Reality• Problem = Known• Problem = Hypothesis• Solution = Hypothesis• Solution = Unknown
  6. 6. • Do customers recognize they have the need?• If there was a solution, would they buy it?• Would they buy it from us?• Can we build it?
  7. 7. Minimize TOTAL time through the loop
  8. 8. Validated Learning
  9. 9. Code Faster:ContinuousDeployment
  10. 10. Continuous Deployment• Deploy new software to Q/A quickly: Measure last check-in to Q/A deployment• Break large projects into small batches• Tell a good change from a bad change (quickly) and…• Revert a bad change quickly
  11. 11. Envelope StuffingYour job is to stuff 5 envelopes and stamp them.What’s faster?1. Folding all five sheets, then stuffing, then licking, then stamping?2. Doing each envelope one at a time?
  12. 12. Measure Faster: Customer Validation
  13. 13. Customer Validation• Indentify product champion or liaison• Validate hypothesis through customer use and interaction• Measure response across a sample set
  14. 14. Learn Faster:5 Whys Root Cause Analysis
  15. 15. 5 Whys Root Cause Analysis• A technique for continuous improvement of company processes• Ask “why” five times when something unexpected happens• Behind every supposed technical problem is a human problem
  16. 16. 5 Whys Example1. A new release broke a key feature for customers. Why? Because a particular server failed.2. Why did the server fail? Because an obscure subsystem was used in the wrong way.3. Why was it used in the wrong way? The engineer who used it didnt know how to use it properly.4. Why didnt he know? Because he was never trained.5. Why wasnt he trained? Because his manager doesnt believe in training new engineers, because they are "too busy."
  17. 17. Cam Collinscam@exumatech.comhttp://exumatech.com@CamCollins (Twitter)

×