Business Analysis Blog
Seven Critical Roles for Gathering Business and Stakeholder Requirements
Many different roles are involved in delivering working IT soluitons. From the business community to the IT community, the players may wear many different hats throughout the project. It is important that each hat is a good fit to ensure project success.
A Developer’s Need for Unambiguous User Requirements
To be effective, business and stakeholder requirements need to contain minimal ambiguity and subjectiveiy. Misunderstood requiremetns are one of the major cuases of IT project failures.
How Process Models Clarify Requirements
Confucius (or another one of the early Chinese geniuses) is credited with saying that a picture is worth a thousand words.
Does IT Need User Requirements or Are We Wasting Our Time?
Are user requirements really necessary? You probably did not define the requirements for most of the software you use on a daily basis, so why bother?
To Be a BA or to Buy a BA
Will Shakespeare has nothing on the intrepid business analyst.
A Process View for Defining Requirements for an IT project
Requirements for Defining Requirements What are your requirements for your requirements definition process? Are they clearly defined? If not, why not? Should your requirements definition process be any different from any other business process? We don’t think so, so...
JAD, JAR, JRP – Agile Approaches for Requirements Gathering Workshops
Time-boxed requirements discovery sessions have been around since 1979 under a variety of acronyms. They are as germane to the challenge of enhancing communicaiton between IT and the business community today as when they were first conceived.
Requirements Decomposition is a Tool of Communication
Decomposing business and stakeholder requirements identifies functions and data the people need to do their job and that information technology can support.
How to Clarify IT Requirements to Ensure a Common Understanding
Business analysis is about much more than just writing requirement. Unless the requirement is understood by the developers and the subject matter experts the same way, it will lead to problems.
’Good’ vs ’Bad’ Business Requirements
Examples of good versus bad business requirements anno 2006
We created the BA-EXPERTS Business Analysis blog to offer traditional, state-of-the-practice, and evolving tips, techniques and insights. Our all-consuming goal is to improve your business analysis outcomes whether your IT group speaks Agile, Waterfall, or Iterative SDM. Our target audience is “the one wearing the Business Analysis hat”, whether you have the title “Business Analyst” or not.
Business Analysis Around the World
Our objective is to keep each of these business analysis “insight” messages short and to the point with information that you can use (or, in some cases, be amused). Our pledge to you is that the contents of the posts will be more than just our opinions. We will base the majority of our articles on the results of extensive research by one of the best content researchers in the business, Angela Hathaway (who can find anything on the web, so if you lost your keys or your wallet…).
Business Analysis Made Easy
In addition, we aim to keep you apprised of what is happening in the world of Business Analysis, System Analysis, Business System Analysis, Requirements Analysis and whatever else organizations decide to call this vital function. Our blog posts will help you in your never-ending search for truth, wisdom and the perfect requirement. (We suspect that finding truth and wisdom will be the easier quest, but we, like you, will never stop trying).







