BA General Flashcards
Q1. What would be few Key Qualities of a Business Analyst?
The BA must have confidence on his or her ability to provide solution for a complex problem, and ability to deal with all level of stakeholders. To gain these confidences the BA must have:
Business knowledge: The Business Analyst must have solid knowledge about the business domain that includes its products, customers, competitor, organisation structure, organisation process asset, goals and objectives, and organisation culture.
IT knowledge: The Business Analyst should understand what the company information systems can and cannot do. The person does not need to have a deep technical knowledge but should have some understanding of network, operating systems, hardware capabilities, database concepts, and the System Development Life Cycle and project methodology.
Interpersonal and communication skills: Since the person needs to effectively communicate with all level of stakeholders, the Business Analyst should be a great communicator and diligent team member, which include verbal, written communication as well as presentation skills.
Data collecting skills: The Business Analyst should know what data the company currently have, source of those data, business value of those data to analyse those data in order to make effective business analysis decisions.
Analytical and problem solving skills: The Business Analyst must have the ability analyse the feasibility of requirements in terms of business requirement, stakeholder requirement, solution scope, effort, time, and costs.
Ability to understand and document business processes: The Business Analyst should be able to recognize, analyse and map processes, model and improve business process and anticipate future state.
Q. What is Business Analysis? How Business analysis help business?
Business analysis is the set of tasks and techniques require to perform in liaison with stakeholders in order to understand the strategy, process and operation of an organisation and recommend solutions that enable the organisation to achieve its goal.
Business analysis ensures the organisation achieves the best values for its investment as it analyses different alternatives for an initiative and recommend the optimal solution with some tangible data. Business analysis streamlines organisation business processes to make the organisation more efficient in everything it does by performing brainstorming, Lesson Learned process, SWOT, Root cause analysis, KPI etc. Business analysis facilitates communication among business stakeholder and technical stakeholder through requirement gathering and translating business and stakeholder requirements into system requirements.
Q. How do you estimate development cost?
For an accurate estimation often I use WBS where project scopes are broken into smaller and smaller tasks. But for WBS you need lot of information readily available to you which is not always practical when estimation is needed for a business case. For business cases estimate, techniques such as Net present value, Average Rate of return, Cost –befit analysis, Payback period can be used. Then again it all depends on type of project or initiative. In addition to that there are few market standard estimating techniques available, these are Analogous estimation, parametric estimation, rolling wave, historic analysis.
Q4. How do you usually go about solving a problem?
My first step would be identifying the source of the problem or business opportunity that solution I need to find. To do that, I need to identify stakeholders who will be affected by the solution, analysing the problem, studding relevant documents and engaging discussion with stakeholders.
The second step would be coming up with as many solutions as I can, and organising a brainstorming session with appropriate stakeholders to come up with more solutions to the problem.
The third step involves eliminating some of the solutions and ranking others based on IT infrastructure, complexity, usability, sustainability, futuristic, risk, size, time and cost and suitable resource.
The fourth steps would be communicating top two or three solutions with key stakeholders with relevant information to seek their opinion about those solutions.
Q5.How do you organize and plan for major projects?
Almost every project I managed I had to prepare various plans for start to end of the project. Each plan included a set of procedures require to support that plan. These procedures will be governed by the organisation project management standard and project management methodology, also, size of the project and client type.
For instance, when I managed NAB project, there was a project manager form NAB end I was the project manager from client end. For that project I had to prepare:
- Communication plan
- Risk management plan
- Scheduling plan
- Change management plan
- QA Plan
- Resources management plan
- System development plan
- System acceptance plan
The communication plan included, how both parties will communicate, frequency of communion, method and location. The scheduling plan included project milestones and deliverables for each milestone, estimated time frame. And how WBS will be prepared, monitor and measured.
The change management plan included what constitutes a change, bug or new development. How changes will be assessed, scheduled and implemented including both parties responsibilities on this regard. The quality assurance plan included how the system’s usability, reliability and performance will be measured as well as each party’s responsibilities such as UAT.
The system development plan included, technology and platform, resources management, which team would be responsible for what deliverables. releases, data migration, staging etc.
The system acceptance plan included a set of documents needed to be signed off, the process of singing of those documents.
Q. How do you deal with difficult stakeholders?
To deal with difficult Stakeholders I practice active listing and try to put myself into the other person shoes, and I never feel hesitate to say sorry. I engage with constructive discussion, I talk with logic, respect, examples, and avoid provocation.
There will always be a reason why stakeholder is difficult. This could be stakeholder seeing a requirement in different perspective due to past expertise. Reason could be stakeholder assumption that the solution should have a certain capability that is outside the scope of an approved requirement. Conflict also can arise due to conflicting priority. The key to manage difficult stakeholder is, understanding of the underlying reason that made the person difficult. Once that reason is established, it can be addressed by proper dialog and discussion, preparing a prototype or by conducting research or, getting third party involve if required.
Q. Give an example of an occasion when you used logic to solve a problem.
Soon after joining XYZ in 2010, I noticed that there were lot of confusions and disagreements among BA and Development teams about the development cost and time estimation. Because XYZ charges its customers for development, inaccurate estimations were having adverse effects on various sections of XYX as well as it customers.
As such, I took an initiative to design and document a Decision Support System that can be used to accurately estimate the cost and afford will require developing a new feature. The solution required inclusion of some additional fields in the project management system to capture some Meta data about tasks, for example is the task is related to report writing, degree of complexity etc. Also a user interface for the user to input some data related the development that needs to be estimated. System then compares the new task with historical data from the past projects and provides estimations for best case scenario, most like outcome and worst case scenario.
To start I prepared a conceptual model using spreadsheet and gave a demo to some key stakeholders. Although they were not fully convinced whether the approach will work but approved an in-house development for the system. Once developed, the first six months the system was not much useful due to lack of quality data, but after that it started to produce some meaningful estimation. It presents the system is must use for entire organisation when comes to estimating a development cost. It is efficient and quite accurate. The system has been and will provide a wonderful service to the organisation for many years to come
Q8. When you worked on multiple projects how did you prioritize?
I normally arrive at work around quarter past 7, I spend first hour reading email and organising my activities for the day. Early in the morning the office will be nice and quiet, free from any distraction which I need to plan for a productive day.
Along with Outlook task and project management system. I maintain a separate spreadsheet that contains my tasks list with priority in terms of business need, release plan, risk, time, agreement with stakeholders, relationship with other task and dependency. Also when a team requires my work that task would have higher priory then individual’s requirement. I closely monitor and update the spreadsheet to synchronise its list with my outlook tasks and project management WBS. I also communicate with my manager or affected stakeholder when a task priority changes. I closely monitor projects related activities and use my experience and judgement and commitment to prioritise task.
Q. How do you handle meeting a tight deadline?
Meeting strict or tight deadlines are quite frequent at my current work. This is not because of my manager but more often the commitments that I would have with external clients. To meet tight deadline I have a simple approach that work for me.
First I plan, in which I break down my tasks for each working hour and define an anticipated output for that hour. This helps me to estimate the time and effort will require to meet the given deadline. After that I work intensely; avoid anything that will hamper my progress. I try to remain calm as much as possible and monitor my progress hourly bases. If I see I am behind, I will work extra hours to catch up with my plan. Try to not leave today’s task for tomorrow.
So my secret to meet tight deadline is stay focus, work intensely, monitor progress, and work longer hours if required.
Q. Describe a situation when you were unable to deliver one of your requirements documents on time. What did you do?
I would inform the recipient as early as possible about the delay with some creditable reasons of curse. I will apologise for the inconvenient. I will inform the person about the new delivery date.
Q. Tell us about a time when you needed to gain approval for one of your business requirements documents but a stakeholder kept on delaying or postponing meeting with you.
This happened to me number of occasions. For this type of situations, I follow a simple process. If I find the stakeholder has valid reasons then I wait as long as I can, but when I feel other may be affected due to the delay, I send an email to the stakeholder explaining what affect the project or team will have due to delaying the approval. If I don’t hear from the stakeholder within a day, I send another email advising that if I don’t receive the approval by certain time or day, I would consider the requirement is approved by the stakeholder. And the last email works like a magic.
Q. As a business analyst, describe your ideal project environment.
I prefer a project environment where policy, processes and methodologies are well defined and followed. Also encourages project members to suggest room for improvement. I prefer a hardworking but balance environment, where all members are fully aware of what the project expects from them. I prefer an environment which fosters collaboration through human interactions as well as technology.
Q13. Describe a time when you introduced a new idea or process into a project or department and how it improved the process or situation.
Once I joined XYZ, I noticed both the development and QA teams often miss the organisation standard for development, particularly standards related to user interfaces. These were causing inconstant looks and behavers within the system. I realised that the reason behind this issue is, some don’t have the full understanding of the development standard as it is a rather large document, and other simply don’t take the standard seriously.
I also realised that if somehow the developers and Quality assurance personals are obliged to go through with the standard document frequently then the problem could be reduced if not eliminated. As such, I designed a web based checklist which includes 28 items to summarise the current development standard for the development and QA team to complete and submit each time they update their task status completed in project management system.
I put the proposal and checklist to the product manager and some key stakeholders, after three months of negotiation the proposal was implemented just for the QA team and a matrix has been setup to monitor improvement of development team in this regards. Outcome that matrix will define whether the development team will also require to submit the checklist or not.
Q14. Describe a time when you had to facilitate a requirements gathering activity where your stakeholders were not located in the same city. If you haven’t done this before, describe to us how you will deal with this type of situation.
Most of XYZ clients head offices are located outside Sydney. Therefore I often require to travel interstate to gather requirements. It is also common that stakeholders from the same client are located in multiple cities. In situation like this, I set up a discussion group in our online project management system where I will give relevant stakeholders access to add or update requirement, ideas and concerns. Any addition or modification will send notification emails to all stakeholders in the group. I use this as a vehicle to collaborate and communicate with stakeholders fairly effectively, particularly when stakeholders are located in different geographical locations.
In addition, I use tele conference, share my screen with stakeholders using remote support system for clarification and confirmation, I travel frequently to run workshop or where I feel face to face meeting is required.
Q. What steps do you take to come up with innovative solution?
My first step would be identifying the source of the problem or business opportunity that solution I need to find. To do that, I need to identify stakeholders who will be affected by the solution, analysing the problem, studding relevant documents and engaging discussion with stakeholders.
The second step would be coming up with as many solutions as I can, and organising a brainstorming session with appropriate stakeholders to come up with more solutions to the problem.
The third step involves eliminating some of the solutions and ranking others based on IT infrastructure, complexity, usability, sustainability, futuristic, risk, size, time and cost and suitable resource.
The fourth steps would be communicating top two or three solutions with key stakeholders with relevant information to seek their opinion about those solutions.
The fifth step would evaluate stakeholders’ opinions and suggestions and recommend the best one.