Translate

terça-feira, 16 de outubro de 2018

The 10 Commandments for the Business Analyst

Business analysts use to have more contact with companies employees and sectors (the company they work for and clients company as well) than any other role. This happens because they're part of both IT and business teams.

The manner the business analyst interact with each of these people or sectors is a critical fact if he wants to establish solid relationships with them.


  1 - Be gentle

It is good to know things, but no matter how many books you have read or even wrote if people realize that it's hard to deal with you they'll start to avoid you. If you're in a contract, in the best scenario this will result, on not renewing of it. If you're an employee you can find yourself doing project secondary tasks that don't demand contact with people. Either way independently of your position the result is not good. So make an effort and be gentle with people.  

 2 - Listen

If you're a good analyst you have a lot of ideas and many stories to tell. The challenge is to limit the sharing of your professional experience and expand more time listening to what people say. It is hard to swallow this pill, but you may not be as interesting as you think you are and not everyone will be willing to listen to your stories of war. You won't learn anything if you're talking all the time, so put your ego aside and start listening. 

 3 - Remember their names

Have you ever been introduced to someone and forgot his name immediately? You're not alone! As a business analyst, you have contact with so many people, with so many names to be remembered that at some time you'll start not to save this information. However, there are some techniques that you can use to remember the names such as repeating the person name as you are introduced, for example, "Hello Mark" or "Hi Vanessa". 


 4 - Do a research about the client's company

To get equipped with some knowledge about the company you're starting a contact will demonstrate to your client that you are interested and also will allow you to use an approach that fits the client's company's culture. Here are some important facts to be considered in the research:


4.1 - Company's size and a total of employees.
4.2 - Culture, structure, and mission of the company.
4.3 - Company's history.
4.4 - Company's competitors.
4.5 - Conditions of work.
4.6 - Main product, services or programs.
4.7 - Location of parent company and subsidiaries.
4.8 - Roles descriptions.
4.9 - Dress code. 


5 - Make the client ideas your ideas

As a business analyst, you're hired to use the experience that you've gained along the past years to propose creative and innovative solutions. Your goal is to contribute to the project's success, this is your essence. We all know that you're not pleading a promotion, but your client might be. If the project is successful there is a great chance of your client get a promotion or at least a recognition, and that's because your delivery was good, because you delivered value.

Despite this, try to be humble and let the people who hired you to get all the credit for your good job. This will be noticed, your client will like and you will be rewarded with respect. 




6 - Deliver more than what's expected

Your client let his expectations very clear to you and obviously you'll prioritize them on your MVP, but this doesn't mean that you should deliver only what's expected by the client. To transcend the clients expectative will always promote that "wow!". Think out of the box avoiding the status quo, ask yourself if there is a better way to execute tasks and have in mind what's best for the client's interests and surely you'll transcend his expectations.


7 - Make new friends at the client's office

Despite the administrative employers don't get the biggest salaries on the company, they have a key role in the project's success. Naturally, their the first person on the client's company to answer your phone call. They're responsible to schedule meetings, document signatures and etc.

They're the communication link with the company's executives and they may harm you if they want to. If you treat them with respect they'll be more engaged in making things happen for you. If you treat them bad you might experience some difficulties delivering tasks that pass through them.




8 - Be a friend of a not like-minded client

Certainly, in a project, you'll find a person that is very hard to deal with. This is the kind of person that irritates you when not cooperative when disagreeing of everything that you do, when is not friendly and etc. If this hasn't happened to you yet stay calm, it's just a matter of time. And if this already happened, it will happen again, so it's a good idea to get prepared.

The first step is to understand the line that when crossed makes the difficult person a difficult person. That person might be feeling insecure in your position, he or she might be thinking that his or her co-workers don't treat him or her well or this person might even have some personal issues. You don't wanna be one more threat on this person's life. Try not to put this person on meetings or chats where she or he will feel threatened and choose wisely the topics to discuss with him or her. Your goal is to make this person feel valued.




9 - Check all documentation before send it

We're all writers that need to understand and that needs to be understood. Any documentation you produce will become a direct representation of the quality of your work.

With the orthographic corrector, there is no apology for orthographic mistakes and a poor grammar might get the reader confused and generate ambiguity.




 10 - Sometimes the good enough is perfect!

Until now all we've talked is how to be the best in what we do when acting as a business analyst. We've talked about less talking and more listening, remember people's names, about being humble, about dealing with difficult people, about rite documents e so on.

But, sometimes there is nothing wrong with taking a rest of all this perfection and be satisfied with what you are. I'm not talking about being negligent, but to achieve a balance between what's wanted and what's possible.

A perfect documentation that never finishes, for example, will never be more efficient than an 80% quality documentation already delivered which the remaining 20% might not be worth the effort to finish.

segunda-feira, 15 de outubro de 2018

Wanna migrate from analyst to project manager?

 

How to successfully make the transition from analyst to project manager?

 

 

Not all project managers want to be in this position forever. Sometimes some of them may want to have a better and more technical interaction with the teams, as the analyst does.

The same way, there are some analysts that don't want to be an analyst forever. They might want to achieve a new level of responsibility in project managing dealing more with clients and less with the team, considering that the analysts are the pivot to a good relationship between project participants.

If you are considering moving from analyst to project manager, here are 5 points that I believe you gonna have to dedicate more energy in order to successfully achieve your goal. 

Training and certification

If an analyst is decided to make the full transition to project management a good start would be proper training and certification. Acquire a PMP (Project Management Professional) certification is the best way.

The candidate must have a certain experience to make the test, but there are places where you can study and get this certification in five days.
 

Learning the system

Yes, there will be software involved. We are in 2018 and you don't want to manage a project with more than 100 hours without using more than a simple sheet. Independently of your favorite tool, the ones that your friends are going to recommend or the ones that your client will tell you to use, just use it. Generally, they are very similar to each other and you might be able to input tasks with due dates, the dependency between tasks and resources associated with tasks and costs. Once you're doing that you're almost ready. 

Learn to see the big picture

As an analyst, you probably are used to seeing tasks, requirements, business processes and diagrams in a more detailed level. As a project manager, you have to consider this details, but you are going to have to get used to seeing things from above, to get the big picture.

This means to analyze in a higher level the tasks impacts, the tasks progress, resources, and dependency. You'll need to know how this affects the project right now, a week from now, a month from now, how it affects the team, how it affects the client and how it affects other projects.
 

Make decisions

The analysts are always making decisions - probably as much as the project manager or even more. The decisions generally are different, with the analyst focusing on technical issues, next steps for the development and specification, backlog definition and problem-solving. The project manager usually is focused on taking high-level decisions such as distribute tasks, change resources, dates and etc.

Having this in mind the analyst that is making this transition must feel comfortable with some situations where he's gonna have to make decisions faster and with less information, without the presence of the team, the client or any other stakeholder that can provide crucial data.
 

Communicate and facilitate

The analyst making this transition to project manager must be a great communicator in his current position. Disseminate information is not enough. You gonna have to be a great listener. You'll need to understand what's being communicated, what's behind it and what's beyond. The product expected from a meeting must be previously communicated to the ones invited so they can get prepared. 

Summing up

Project managers and analysts, they're both leaders. Both have to be excellent communicators, facilitators team leaders, decision-makers and also must know how to deal with a client in different manners. Each role gets you well prepared to migrate to the other. Maybe the migration from analyst to project manager will be easier because of the analyst's technical background, which is not mandatory to a project manager but it might be handy in some situations.