Requirements Gathering Workshops for Widely Distributed Teams
Requirements Gathering Workshops Go Virtual – For Real Defining business and stakeholder requirements is tough enough; adding the difficulty of having to deal with different locations and time zones can drive you up the wall. You might have tried web or virtual...Five Rules for Writing Effective User Stories
User stories are a great way of expressing stakeholder requirements. By following a few simple rules, they can become even more powerful.
Requirements Gathering Interviewing Techniques for Business Analysts
Maintaining a list of the questions you need answered is a simple but effective interviewing tool for business analysts.
Agile Business Analysis or Business Analysis for Agile?
Agile is currently a very popular term in the world of information technology or IT. Since the release of the Agile Manifesto and the proven viability of Agile Software Development Methodologies, every product or service supporting IT development strives for...Strategic, Tactical, and Operational Business Analysis
Strategic, Tactical, and Operational Business Analysis are three distinct levels within an organization. Although they are all called business analysis, there are significant differences in the breadth and depth of the tools and techniques necessary to support each.
Operational Business Analysis Is Done within the IT Project
Operational Business Analysis is heavily used at the application level by Agile teams, by developers performing business analysis activities, and by administrators of packaged soctware.
Strategic Business Analysis is Done at the Business Planning Level
Strategic Business Analysis (aka “Enterprise Analysis”) applies the tools of techniques germane to business analysis to an entire organization or any subset thereof. It is an essential step in intiating positive change within an organization.
Tactical Business Analysis is Done During Project Initiation
Tactical Business Analysis is applied within a project to ensure that the product is well defined and understood both by those who need the produce and by those who build/buy the product. In an Agile environment, it is used primarily during release, iteration, and sprint planning sessions.







