Do you have a clear idea of what success looks like as a business analyst? It’s not an easy question to answer.
Here are my thoughts for evaluating a business analyst’s success within an project based on my own BA manifesto:
- Does the project deliver the anticipated value? Does the project meet the objectives of the business case?
- Are the stakeholders aligned around the project concept? If you asked each of them individually about what is to be achieved, would you get the same or at least consistent answers?
- Are the stakeholders satisfied that the scope being delivered is the best possible solution to the problem they are trying to solve?
- Does the implementation team deliver on the requirements without a lot of wasted effort? Did they understand what needed to be accomplished?
- Is the test team able to validate that the final application met all the requirements or do they come across areas of ambiguity that need to be addressed?
- Are there big surprises at the end of the project? Do unexpected requirements come up? Every project will experience a bit of churn toward the end as you flesh out the final details, but missing a big piece of functionality or a critical business process is a sign that the BA failed.
- Is the business happy? Do they find value in what was delivered? (A no answer can have many root causes, but a yes answer is typically the sign of good business analysis work.)
At the end of the day, business analysts add value by bringing clarity to project outcomes and getting the business to own the solution. Just because this seems difficult to measure, doesn’t mean we shouldn’t measure it to the best of our abilities.
Learn How to Measure BA Performance
Adriana Beal has address this challenging topic in Measuring the Performance of Business Analysts, a practical guide to finding meaningful KPIs that can be measured without unnecessary overhead.