090214 Fail Software Development
-
Upload
ed-kuiters -
Category
Business
-
view
240 -
download
2
Transcript of 090214 Fail Software Development
- 1. how to fail at software development
- 2. Standish Report ('95) More than 30% never completes More than 50% doubles original budget Est costs US $ 140 billion Failures are covered up, ignored, rationalized ...and not only by others...
- 3. Program 1. Identify failure 2. Learn from from failure 3. Change approach
- 4. Product
- 5. Make an irrelevant product
- 6. Beating a dead horse
- 7. UseBIGtools forsmalljobs
- 8. Wrong platform
- 9. Management
- 10. Fixed price innovation
- 11. Single step approach
- 12. Choke your supplier
- 13. Don't share intentions
- 14. Attitude
- 15. Hope for the best
- 16. Don't listen to your inner voice
- 17. You are right!
- 18. I am not responsible
- 19. Lessons learned?
- 20. Failures Trefpunt Kiddy KPN Leiden !Go Fabory Semecs RHG Profile Heuver ABS OSN Total solve problem 1 1 1 3 dead horse 1 1 1 1 4 big tool 1 1 platform 1 1 2 fixed price innov 1 1 2 1 step 1 1 1 1 4 uitknijpen 1 1 1 1 4 hidden agenda 1 1 1 3 ignore signals 1 1 1 3 hope best 1 1 not responsible 1 1 open kaart 1 1 1 1 4 1 1 2 1 3 3 4 2 0 3 3 9
- 21. How can I learn
- It has got to HURT
- 22. It is ALWAYS your fault
- 23. Think harder
- 24. Force yourself to draw conclusions
- 25. Read
- 26. It has gotHURT
- 27. Not my fault...
- 28. It isALWAYSyour fault
- 29. ThinkDEEPER
- 30. Drawconclusions
- 31. Read
- 32. 37signals 1. Smaller = better 2. Fix: time, budget. Flex scope 3. What is the big idea? Ignore details 4. Make opiniated software 5. Brainstorm > sketch > coding 6. Interface first, Epicenter design, no functional specs 7. Less software 8. Half, not half assed products 9. Features; it does not matter
- 33. and you?
- What mistakes did you make?
- 34. How do you learn from them?
- 35. What did you learn from them?