Lecture on Business Analysis for IT Systems

Introduction

• Objective: Discuss the significance of business analysis, especially in IT systems.
• Scenarios: Examples of problems and opportunities faced by businesses today.
  • Traffic issues: Urban areas with excessive traffic.
  • Compliance issues: Large companies facing regulatory challenges.
  • Opportunity in resources: Utilizing empty parking lots for revenue.

Key Questions in Business Analysis

• What activities are needed to address problems or capitalize on opportunities?
• What knowledge is required about the domain, context, and methods?
• Stakeholder involvement: Who to consult for input?
• Solution alternatives: How to evaluate and select the best option?
• Success criteria: Revenue, market share, etc.

History of Business Analysis

• Emergence in the 1980s alongside decreased storage costs and increased use of technology.
• Initial failures due to projects exceeding time/budget and not delivering value.
• Need for structured communication between business and IT led to the development of business analysis.

Project Success Rates

• Standish Group Report: Classifies projects as successful, challenged, or failed.
  • Successful: Meet cost, time, and scope/quality constraints.
  • Challenged: Fail in at least one dimension.
  • Failed: Cancelled or unused.
• Statistics:
  • 30% of projects are successful.
  • More than 50% are challenged.
  • 20% fail.
• Larger projects have higher failure rates.

Case Study: Netherlands

• Dutch government loses 1 to 5 billion euros annually due to failing IT projects.
• Only 7% of large government projects succeed.

Factors Leading to Failure

1. Lack of user involvement.
2. Incomplete requirements and specifications.
3. Poorly defined outcomes.
4. Insufficient stakeholder communication.
5. Lack of executive support.
6. Unrealistic project expectations.

Importance of Business Analysis

• Early stage involvement is crucial for cost-effective problem-solving.
• Failure costs increase exponentially in later stages of system development.
  • Lifecycle Phases: Requirements analysis, design, coding, testing, and maintenance.
  • Cost increases from requirements phase to maintenance.
• Business analysis connects business problems with IT solutions.

Definition of Business Analysis

• Practice of enabling change by defining needs and recommending value-driven solutions.
• Focus on delivering value to stakeholders.

Conclusion

• Business analysis is vital in understanding and solving business problems with technology.
• Future videos will further explore definitions and applications.

End of Lecture