Pedro Gama discusses the challenges of delivering software in unpredictable real worlds. He notes that according to the Standish Group Report, only 45% of delivered software functionalities are ever used, while 13% are often not delivered. Gama argues that attempting to control everything through extensive documentation and planning does not work because it requires freezing the business. Instead, he advocates for embracing failure by delivering software frequently, every 3 weeks, and contracting "code breakers" to find issues early. This allows organizations to improve continuously and deliver useful software that meets 0% defects and 100% usability goals.

1. Delivering software in unpredictable (real) worlds Pedro GamaTEDxEDGESPortimão, Oct 1st, 2010

2. Is building softwarea risky business?

3. *picture from http://alibiblog.wordpress.com/category/software-development/

4. Always 7% Rarely 19% Often 13% Never 45% Sometimes 16% Usage ratio of delivered functionalities Source: The Standish Group Report, 2008

5. Always 7% Rarely 19% Often 13% Never 45% Sometimes 16% Usage ratio of delivered functionalities Source: The Standish Group Report, 2008

6. How to build usablesoftware?

7. you can try Control

8. Lots of documentation, plans and charts *picture from http://www.disambiguity.com/wheres-the-gantt-gone and http://www.information-management-architect.com/documentation-standards.html

9. But you have to freeze business! *picture from http://www.airconinstallation.com/ratesandservices.htm

10. you can also try Failure

11. Fail often, quickly and agressively Until success… as expected

12. effective Failure is very hard to achieve

13. “Everything is running smoothly… releaseconfirmed7 months from now. “Don’t worry, we’re getting there… everything is already 90% complete” “I know we are 7 weeks late, but we will make up for that in a month.”

14. commit to Failure

15. Do you release each 3-week? Deliver to yourself at a daily basis Use state-of-the-art technology for early warnings Contract professional“code breakers” Embrace failure in your organization

16. noFailure is the risky status

17. beBOLD

18. 0-defects 100%-usability Define your Everest *picture from http://www.frontrange.ca/Magazine/Nepal/gokyo/gokyo.html

19. keep Improving *picture from http://media.photobucket.com/image/everest+route/dm7799/EverestRoute.jpg

20. and beGLOBAL

21. forget borders… embracethe Community *picture from http://maps.google.com

22. Deliver Useful Software. Every 3 weeks. Always.