Requirements analysis is a key component of a requirements process. It involves organizing, prioritizing, modeling the requirements. Well-analyzed requirements are complete and unambiguous.
We ask the questions that people having been avoiding for years while they were trying to look smart. I read an article today from our respected colleague, Yaaqub Mohamed about the importance of data analysis as part of a good analyst’s tool belt. Well that is not exactly how he put it, but you get [...]
Reader Question: The organization I work for is expanding its Business Intelligence capabilities, introducing a new Enterprise Data Warehouse for management reporting. This is based on the concept of OLAP Data Cubes – permitting greater flexibility for user reporting. My question is – what’s the best approach for eliciting and documenting requirements for BI/Data Cubes? [...]
Working with stakeholders to prioritize requirements is an important part of the BA role. Often, prioritization can be a difficult exercise, with stakeholders asserting that every single requirement is a “must have”. When this happens, it can be a sign that insufficient attention has been paid to the project foundations. Prioritization should be based on [...]
In my previous article titled “How I became an agile business analyst” I talked about my passage from the world of good old fashioned ‘write it all up and get it signed off’ business analysis into the uncharted territories of agile. In this article I’m going to describe my first experience on an agile project. I [...]
Reader question: “How do people go about collecting report requirements from clients and trying their best to reduce overheads whilst still fulfilling the data needs? I know there has been a big drive recently for Green IT and how companies can reduce their carbon footprint, is this a tactic that should be used? In addition, [...]
As a seasoned Business Analyst you come to recognize that not all “requirements” are really requirements. Ideally discovery teams first diverge, taking differing positions, identifying all possibilities. Then after carefully examining numerous alternatives, they use a decision-making process to converge on a solution. In a face-to-face workshop you might group, rank, or prioritize ideas, but [...]
Do you consider all the implications of your projects? As business analysts, we are often most comfortable thinking about what happens if we’re “on spec.” After all, specifying a future state of affairs is a big part of what we do. Given that, do we think enough about what happens if our projects fail, succeed, [...]
When I decided to write about prioritizing requirements, I figured that there were enough articles out there….and very good ones at that…to not warrant yet another “how to” blurb. An aspect we don’t hear about quite so much is understanding the value of prioritization. As analysts, many of us work in an environment in which [...]
The business analyst in world of COTS projects The number COTS or Commercial-off-the-shelf-software options have increased exponentially in recent years. A sister of COTS, the “SaaS” or Software-as-a-Service where the commercial solutions are made available over the web, with no hosting or installation required, has made these solutions even easier to implement technically. This blog [...]
We all know exactly what “assumption” stands for and how false assumptions can make those first 3 letters stand out and beat you over the head. But do you take time to clarify your assumptions? And better yet, do you validate them? False assumptions lead us …. well we know where they lead us. But, [...]