The document provides an overview of the past, present, and future of the business analysis profession. It discusses how business analysis has evolved from a loosely defined role focused primarily on software requirements to a professional discipline. It outlines the Business Analysis Body of Knowledge (BABOK) which defines the tasks, skills, and techniques of business analysis. The document also notes that while business analysis is increasingly recognized as important, capabilities still need improvement, and discusses how the role of business analysts is expanding and specializing in response to growing business complexity and new technologies.
27. Projects: Riddled with Complexity A Legacy of Complexity Complex business environment Multiple, inflexible systems functioning together Unproven technology Multiple products from diverse vendors Complex project teams Political sensitivity Complex organizational structure Coupled with Constantly Emerging New Trends IT Alignment Adaptive approaches Agile development Incremental delivery Complexity-reducing design techniques Limit interrelationships of system components Solution design tools New technologies SOA, BPM, Web 2.0, SaaS Requirements Mgt, Auto Test Tools 24
28. IT Project Performance Nearly 2/3 of IT projects fail or are challenged What Measure is Missing? Source: The Standish Group Project Resolution History 25
29. What the Experts Say Meta Group Research “Communication challenges between business teams and technologists are chronic - we estimate that 60%-80% of project failures can be attributed directly to poor requirements gathering, analysis, and management.” Forrester Research “Poorly defined applications have led to a persistent miscommunication between business and IT that largely contributes to a 66% project failure rate for these applications, costing U.S. businesses at least $30B every year.” James Martin “56% of defects can be attributed to requirements, and 82% of the effort to fix defects.” > 41% of new development resources are consumed on unnecessary or poorly specified requirements Source: Keith Ellis, Business Analysis Benchmark Study, The Impact of Business Requirements on the Success of Technology Projects, IAG Consulting, 2008 26
30. Root Cause: Quality of BA Work Poor Requirements Questionable Strategic Alignment Inadequate Business Case Deficient Practices System vs. Business Specs Business Benefits not Measured Business Need Not Met Lost Opportunity Inadequate Tools Ineffective Prioritization and Resource Allocation Inadequate Business Involvement Inadequate Focus on Business 27
51. Competitive and developing markets have a critical need for highly experienced generalists and specialists in the competency domain (e.g., strategic, marketplace analysis)
56. Specialist BAs Will Be In Demand More companies will move to stages 3, 4, and beyond Generalist, project-oriented BA will remain but not be alone Top talent will gravitate to successful companies Other roles than these will likely emerge 45
For many organizations, strategy is an emergent phenomenonThey may not have a well defined set of goalsWhat they do may have little to do with those goals
Rework and abandoned systems$75B per yearFailed state DMV projects$45-67MCONFIRM rental car project$165MAutomating insurance policy processing$50MEuroDisney$4BFBI’s Virtual Case Mgt.$170M
The 20th century view is alive and well today—call it “naïve agile”Many (NOT all) Agilists assume that business value is what the users ask forIn practice users often ask for things that deliver zero or negative business value
Need for BAs = f(maturity, size, diversity)
BAs need to move away from thinking of themselves as IT folks
IIBA Research shows dozens of analysis techniques and notations in common useExpect to see drop as people standardize on tools