Let me start by saying this: You can't manage by metrics.
But metrics are important tools that help you understand how you are performing today. Measuring things can help you understand how you are performing against past performance, against expectations or competitors. They can help you find defects and bottlenecks. They can also help you understand the system you are operating in better.
And you should measure different things at different times. My philosophy behind measurements is that you are collecting data so you can perform experiments to test improvement ideas. Once an idea has been developed and tested, it is time to change the measures.
So, what metrics can we apply to the activities that business analysts do? What background data can you collect that helps you develop hypotheses and test them?
I have a couple of ideas that might be useful at once time or another. I'll post them in a few days. In the meantime, do you have any suggestions?
21 September 2011
Subscribe to:
Post Comments (Atom)
Popular Posts
-
I have been having a bit of a discussion over at the IIBA blog with Kevin (VP BOK) and Julian (Chief architect.) It’s migrated over to ...
-
Due to popular demand I have aggregated some information on User Stories and created a simple template. If you feel this would be useful to...
-
Better Projects Templates I am uploading a couple of project document templates to Google Docs. As I add more I'll post them up here. You...
-
You've heard many reasons why project fail. Here is a discussion hosted by BCS on why projects work. The discussion covers four dimensio...
-
The Precedence Diagramming Method ( PDM ) was developed in the early 1960s by H.B. Zachry in cooperation with IBM. It has largely repla...
-
In the below video some of the #10yrsagile participants discuss the role of the Business Analyst. A question for you; Do you agree or di...
-
This is a guest post by Jeff Hobbs. Jeff is a project manager at ActiveState Software who provide pm and collaboration software. Email, ...
-
In one of the Carnivals of Business Analysts the theme was “ Requirements Analysis ." I searched the web far and wide and came up with a n...
-
The definition of a stakeholder is controversial. For example, project team members are generally not considered stakeholders, but in virtua...
-
I have written about the V-Model across several posts. The V model is a testing focused expansion of the software development lifecycle. In ...

We can collate the stake holder expectations from the project and mark them against the BA. At the end of the project or in the middle of the project we can review it on a scale of 1 to 5(being good)
ReplyDeleteIf it is less then the BA mananger can take steps to make the performance to 1