bdavis@e2consultinginc.com's blog
Apples, Oranges and Analysis
There’s an irony in Business Analysis. While recruiting, screening, hiring, and even teaching others for and about the role of a Business Analyst, we demand and filter for the technical and academic skills. Yet, once they are hired and in the role, we insist that the job being done is too volatile and uses too many soft skills to be measured. That these factors alone deem the measurement and benchmarking of requirements activities, progress, performance, quality and even effectiveness can’t be accurately pinpointed and evaluated.
Read More on my blog: www.requirementstoolkit.com/pubblog
The Golden Rules Of Requirements
While there are many differing opinions about how you achieve requirements success, on thing is certain, each of those opinions is based on a set of basic principles and a set of “rules” to follow.
But this is where they usually stop. It’s not so much what the rules are, but rather, how they are implemented. I think most experienced Business Analysts can agree that the basic rules are: Identify and define the objectives, define the requirements, document them, verify the requirements against the objectives and validate the requirements.
- 2 comments
- 400 reads
Why Domain Knowledge Is a Hot Button And A Typical Requirement For A Business Analysis Candidate
We've all seen ads on LinkedIn and other sites looking for Business Analysts with specific domain knowledge. In fact many industries are notorious for being exclusive about the candidates having a specific amount of tenure domain as a Business Analyst.
For a long time, when this question pops up on LinkedIn discussion boards I pop in and assert that it is because the recruiter or hiring firm doesn't really understand the value proposition that a skilled Business Analyst brings to the table. To be honest, this is only about half true.
