It has been two years playing the role of a B.A. and I still remember the start of it. My biggest concern was, ‘where do I start’? I was not sure exactly what I was expected to do. The B.A. role has been around for some time. The only change is that prior to giving this role an actual title there were members from the technical side would adopt this role. Gradually the understanding of specialization in this area surfaced and the role of a B.A. came into shape. The demand for people with this specialization have been ever so increasing.
A lot of people assume that the B.A. role simply just is bridging the gap between the Business and Technical team. First rule of being a B.A., never assume. Assumption is the route to all disasters in a project. Nevertheless, bridging the gap is a key function. A B.A. role is never definitive. It varies in every organization.
I believe you need to determine a framework to work in. A lot of the B.A.’s would use the term scope. Now I don’t mean to limit yourself completely but you got to set boundaries. You don’t want to have too much on your plate. You don’t want more than you can chew on. The firm has their reasons for employing you. You need to be sure what that is and the kind of work that you are intended to do to get there.
The Business Goals need to be clearly identified and documented. Documentation is key. We’ll get into detail about that later. For now, I would like to emphasize on how important it is to familiarize yourself with the Business Goals and to know the people involved in determining these goals. This right here is your starting point. It’s imperative to also comprehend reason for these goals. It would give you a better sense of what the Business is aiming for and at the same time gives you a chance to dig a little deeper than what’s seen on the surface.
Start digging! Let’s get to the root of this!
Until next time.