Business Analysis Defined

Learn what BA is, when to do it in Agile and Waterfall SDM, and what techniques are in use.

By: Thomas Hathaway, Angela Hathaway

Narrated by: Virtual Voice

Length: 1 hr and 12 mins

Publisher's summary

A Buddhist proverb warns, “Be mindful of intention. Intention is the seed that creates our future.” In a very real sense, this statement expresses the reason for business analysis. This discipline is all about choosing and defining a desired future for your business (expressed in business analysis terms, “requirements”). Business Analysis comes in three flavors: Strategic, Tactical and Operational Business Analysis. At the enterprise or unit level, strategic business analysis identifies, defines, scopes, and prioritizes projects and initiatives in line with organizational goals, objectives, and strategies. To be effective, this business process relies on sound business analysis tools and techniques. Tactical business analysis starts when the organization initiates a project or initiative that will result in change for some subset of the organization. The purpose of tactical business analysis is effective communication between those affected by the change (typically the business community) and those responsible for instigating the change (typically the IT group). When and where this communication takes place and how you express the results depends on the System Development Methodology (SDM) the project follows. During software development and maintenance, operational business analysis ensures that an evolving IT solution meets the changing needs of the business community. This is the level most concerned with the business use of information technology. If the software product is a purchased package, this level deals with analyzing how to manipulate the configuration to achieve the stakeholder requirements. Otherwise, operational business analysis decomposes User Stories (during a Sprint in the Agile world) or Stakeholder Requirements (in a traditional SDM) to identify Solution and Transition Requirements. This book provides insight into this fast-growing field by: - Explaining strategic, tactical, and operational business analysis - Providing surveys of what Business Analysts do - Defining what business analysis techniques people use most often - Describing what “requirements” are and what different types of IT requirements exist - Sharing the authors’ experience on how Waterfall, Iterative, Agile, and Experimental (aka “Chaotic”) Software Development methodologies impact the business analysis activities WHO SHOULD READ THIS BOOK? Although the field of Business Analysis offers great career opportunities for those seeking employment, some level of business analysis skill is essential for any adult in the business world today. This book is for anyone interested in or involved in defining the requirements for future IT applications. THIS BOOK IS PART OF A SERIES Although this book has value on its own, “Business Analysis Defined” is the first book in the series "Business Analysis Fundamentals - Simply Put!". This series gives you a basic understanding of many core concepts in business analysis. It also teaches how to do the most common business analysis activities. Each book has value on its own. It either provides an overview or teaches specific business analysis techniques. We do not expect everyone reading the series to become a professional business analyst, but it is a great first step. The world sorely needs good business analysts. Get your start with the series today! Book 1: Business Analysis Defined Book 2: How to Write Effective Requirements for IT - Simply Put! Book 3: Requirements Elicitation Techniques - Simply Put! Book 4: Data Flow Diagrams - Simply Put! Book 5: Functional and Non-Functional Requirements - Simply Put! Book 6: Requirements Elicitation Interviews and Workshops — Simply Put!