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 Source: IEEE, September 2005 5-15% of projects abandoned after money is spent

7. not UML is not the problem

8. not Formal verification is not the problem

9. not Coding is not the problem

10. not Debugging is not the problem

11. not Deployment is not the problem

12. good All of these are good

13. software 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: lululemon athletica http://www.flickr.com/photos/lululemonathletica/5197327623/

18. What else remains?

19. People 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

26. Bringing Developers Into an Ecosystem Mail Bugs Code Release 1Release 2Release 3 Mail Bugs Code Bugs Mail Code Bugs Code Socio Technical Accelerated Tech Social Technical 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. Enterprise Teams Organization Profit, Internal Rate of Return Project deliverables, cost and schedule Delivery of business value through the optimal use of resources Staff member/ Developer Work item, artifact completion commits to Development tools: IDEs, debuggers, performance tools Team tools: version control, bug and work item tracking tools, project management tools Financial modeling: Business intelligence Business Thinking Technical Thinking Portfolio and risk management: Measure, plan, and optimize a portfolio of development projects Coordination and Commitments

31. Financier: Uncertainty and Risk Communication around discrete variables is difficult Directly model risk using a triangular distribution Use monte carlo simulations to determine the range of outcomes ExpectedHighLow0

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 80 th 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