I have been the software developer for nearly four years. In my first six or seven months, I work closely with the BA (shortcut for Business Analyst) to know the whole context for client project. Then I work without BA after the client re-structure. I almost forget what happens when your team has one BA role and have no idea what should BA do in daily work.

In my new project, I get the chance to work as the BA role for weeks. Then I start to compile my notes and try to give the newbee who wants to become a BA or want to learn the BA skills.

Firstly, Let’s learn the definition of BA:

Someone who seek the business value, understand the domain knot, explore how to solve problems and facilitate the growth of understanding among the team.

Secondly, never too late to prepare, don’t be afraid of trying new skill set, even if you has just been told you need to work as BA tomorrow. Have a try to search in BA community and read the related articles, like what does user stories mean, how to write Accpetance Criteria. At least you understand and know BA skills better.

Then, ask the formal one who works with the client before, be familiar with client workstyle, preference and dislike.

Next, have one well-organized user interview agenda before face-to-face meeting. Try to learn client jargons and know the specific shortcut meanings. Write down the agenda if possible. Adding self-introduction at the top of agenda if you are new here. In the beginning, let client know what is the propose for this interview or catch-up. Make sure you understand their needs and expectations, coz you need to transform stakeholder needs and expectations into customer requirements later for your team.

Meanwhile, if you already understand the business value and process, in order to clarify everything for your team, having the question list is the best way to let everyone in the same page. You can even type the answers or output during the interview. This is not the waste of time, coz when typing the words, client can correct you if anything is wrong.

Last one, draw diagrams according to different persona’s user journey, and this is quite straight forward. This is also a good way to figure out the requirement map. By the way, tools like draw.io or axure are good choices.

If you still find very hard to begin, you can start with:

  • Asking WHY questions
  • Establish common language
  • Be the “user”

Keep asking understandable questions and build connections among business, users and techies.