This is a presentation I gave to the Roles class at Neumont University on May 1, 2008

1. iRise Presentation for Neumont University May 1, 2008

2. A rigorous 237½ step process for the systemic discovery and definition of non-functional requirements for safety-intensive systems based on statistical methods and empirical observation Neumont University

3. A rigorous 237½ step process for the systemic discovery and definition of non-functional requirements for safety-intensive systems based on statistical methods and empirical observation Neumont University

4. Why being a BA is Fun *and* Important… Business Analysis for Fun and Profit Neumont University

5. Developers are being off-shored, be a BA… Business Analysis for Fun and Profit Neumont University

6. Business Analysis, Requirements and Simulation Business Analysis for Fun and Profit Neumont University

7. The skills you need to displace stodgy old BAs already in the workforce… Business Analysis for Fun and Profit Neumont University

8. Be a BA Business Analysis for Fun and Profit Neumont University

9. Tom Humbarger Senior Strategic Projects Manager [ thumbarger @irise.com ]

13. Different interpretations Marketing Sales IT Finance Manufacturing Engineering

14. What the customer needs

15. Defects cause challenges Requirements 56% Code 7% Other 10% Design 27% - This data from James Martin Over 50% of software defects are attributed to requirement errors

16. Defects cause rework Code 1% Other 4% Design 13% Requirements 82% - This data from Dean Leffingwell Over 80% of rework effort is spent on requirements related defects

17. Requirements Management Impact - This data from I. Hooks 0 5 10 15 20 25 200 180 160 140 120 100 80 60 40 20 0 Percentage of Cost Overrun Requirements Process Costs as Percentage of Total Project Cost 0- 5% on Requirements Process Results in 80-200% Overrun 8-14% on Requirements Process Results in 0- 60% Overrun Value of Investment in Requirements Process Development Project

18. What did Archimedes say? - This data from Boehm: Software Engineering Economics Requirements Analysis & Design Coding Development Testing Acceptance Testing Product Quality Production

19. The Quality Lever - This data from Boehm: Software Engineering Economics Requirements Analysis & Design Coding Development Testing Acceptance Testing Product Quality Production 40-100x 30-70x 15-40x 10x 3-6x 1x

21. The Business Analysts

22. The User Experience Professionals

23. The Product Managers

24. The “Business Designers?”

28. WYSIWYG

29. WYSIWIS

30. DWIM

31. Business

32. IT

33. Business IT

34. IT

35. Business IT

36. Grokking

38. Grokking Not a whole lot of grokking going on…

39. What causes this lack of grokking? Ambiguity Uncertainty Rap music Creationism (aka BUFD) Timelines Tooling/Support Culture Creeping elegance Banana problem Misunderstanding Unclear Expectations “ That’s how it’s always been”

40. Requirements

46. Here’s a pretty orange requirement. I’ll take it back to The office. Tim Lister - Keynote Agile Development Conference 2004

47. I think I may have a requirements management problem…

53. Or the alternative…budgeting for goons

56. … until they see it… That’s not *exactly* what I had in mind…

57. IKIWISI

58. Or maybe…it’s not until they try it…

59. IKIWITI

62. Requirements Processes

63. Wiegers’ Requirements Taxonomy ( www.processimpact.com )

64. Volere Requirements Process ( www.volere.co.uk )

65. BA BOK Knowledge Areas ( www.theiiba.org ) Requirements Planning & Management Requirements Gathering Requirements Implementation Requirements Analysis & Documentation Requirements Communications Enterprise Analysis Fundamentals

66. iRise G-A-V Framework ( www.irise.com )

67. iRise G-A-V Framework - Gathering

68. Requirements Documentation

74. Density doesn’t equal fidelity.

75. Comprehension can’t be calculated in words per square inch.

76. Understanding isn’t measured in lbs. per feature.

79. Are we thinking outside the box?

80. Visualize

81. Sharing a mental model isn’t easy… unless you make it easy for people to see the what they mean.

82. What industries use visualization?

83. Architects visualize success

84. Boeing visualizes success

85. GM visualizes success

86. What is visualization?

87. Visualizations are just models of reality

92. So, why not visualize software?

93. Viola - CAD for software!

97. Are we outside the box yet?

99. iRise Vision “ By 2020 all business software will be visualized prior to development, the same way that visualization is a common practice in the design of every car, airplane and semiconductor today “

100. Kinesthetic

101. Variable Fidelity

102. Immersive

103. Compelling

104. Very low fidelity…

105. Low fidelity

106. Medium fidelity Drug Dose Drug ABC Drug DEF 100 mg 200 mg Route Freq Indication Last Dose Comment Current Medication List ------ ------ ------ ------ ------ ------ ------ ------ ------ ------ Add Delete Modify Save No Change Cancel Consistent function with other EMR design, e.g. allergy documentation User will be able to make all changes then Save Last Updated: Date/time Updated By: Name/Title Show Brand (Generic) name When possible.

107. High fidelity

108. Or the alternative…

109. Ultra-high fidelity

111. "Few things are harder to put up with than the annoyance of a good example.” - Mark Twain

112. Finally…another mission statement

115. Business Analyst from Salary.com Business Systems Analyst I Reviews, analyzes, and evaluates business systems and user needs. Formulates systems to parallel overall business strategies. May require an associate's degree in a related area and 0-2 years of experience in the field or in a related area. Has knowledge of commonly-used concepts, practices, and procedures within a particular field. Relies on instructions and pre-established guidelines to perform the functions of the job. Works under immediate supervision. Primary job functions do not typically require exercising independent judgment. Typically reports to a manager.

116. SW Engineer from Salary.com Entry Level Software Engineer Designs, modifies, develops, writes and implements software programming applications. Supports and/or installs software applications/operating systems. Participates in the testing process through test review and analysis, test witnessing and certification of software. Requires a bachelor's degree in a related area and 0-2 years of experience in the field or in a related area. Has knowledge of commonly-used concepts, practices, and procedures within a particular field. Relies on instructions and pre-established guidelines to perform the functions of the job. Works under immediate supervision. Primary job functions do not typically require exercising independent judgment. Typically reports to a manager.

118. www.mycatalyze.org

119. http://www.facebook.com/group.php?gid=18509427840

123. In closing…always remember… Quidquid latine dictum sit, altum sonatur. - Whatever is said in Latin sounds profound.

124. Business IT

125. Business IT

126. Questions? Tom Humbarger [email_address] [email_address]

127. Thank you!