Don't blame the developers!

1. Don't blame the developers! External stakeholders and the tangled web of complex software development. Patrick Wagstrom IBM TJ Watson Research Center

2. Hey! You Got People in My Software! Patrick Wagstrom IBM TJ Watson Research Center

3. 62% of IT projects fail to meet their schedule Source: Dynamic Markets survey, 2008

4. CityTime in NYC has exploded from $68m to $700m Source: Wall Street Journal, 2011/06/21

5. > $1 trillion annual IT investment 5-15% of projects abandoned after money is spent Source: IEEE, September 2005

7. UML is not the problem

8. Formal verification is not the problem

9. Coding is not the problem

10. Debugging is not the problem

11. Deployment is not the problem

12. All of these are good

13. But they focus on the software

14. Image: http://en.wikipedia.org/wiki/Iliotibial_tract

15. Photo: http://www.flickr.com/photos/meddygarnet/3392686660/

16. Photo: http://www.flickr.com/photos/familymwr/5112318513/

17. Photo: lululemonathletica http://www.flickr.com/photos/lululemonathletica/5197327623/

18. What else remains?

19. People are the primary determinant of success on IT projects

20. Who is involved in enterprise software development?

21. Just a few Stakeholders… • Customer • Developers • Architects • Testers • Brand Executives • Legal • Marketing • Product Managers • Sales • Services • Strategy • Support • Partner Companies From Williams et. al. 2010. “Supporting Enterprise Stakeholders in Software Projects”

22. Photo: US Fish & Wildlife Service http://www.flickr.com/photos/usfwspacific/5565696408/

23. Ecosystems

24. Varied forms of Ecosystems

25. Varied forms of Ecosystems

26. Bringing Developers Into an Ecosystem Release 1 Release 2 Release 3 Bugs Code Mail Socio Technical Code Mail Bugs Accelerated Mail Code Bugs TechSocial Code Bugs Technical Code Source Only

27. Finding of Progression Paths - Project

28. Finding of Progression Paths - Ecosystem

29. Photo: David Watkins http://www.flickr.com/photos/dvids/4987579486/

30. Business Thinking Technical Thinking Coordination and Commitments Profit, Internal Rate of Return Enterprise commits to Financial modeling: Business intelligence Delivery of business value through the optimal use of resources Portfolio and risk management: Measure, plan, and optimize a portfolio of development projects Organization commits to Team tools: version control, bug and work item tracking tools, project management tools Project deliverables, cost and schedule Teams commits to Work item, artifact completion Staff member/ Developer Development tools: IDEs, debuggers, performance tools commits to

31. Financier: Uncertainty and Risk • Communication around discrete variables is difficult • Directly model risk using a triangular distribution • Use montecarlo simulations to determine the range of outcomes 0 Low Expected High

32. Ships as Investment Analyst with IBM Rational Focal Point 6.5

33. Seminal: Actionable Insight for Software Support • Support is a major component of enterprise software • Dashboards provide information, but are difficult to use • We seek to create a system that provides • Dashboard like analytics • High interactivity for exploration • Insight into what is next • Make it usable and comprehensible

35. Why 80th Percentile? • We’re concerned about operationally relevant metrics • Processes optimized for efficiency in the head • Tail are often strange issues that don’t reflect on organization • 80% percentile differentiates head from tail

37. patrick@wagstrom.net http://wagstrom.net/ @pridkett