Hello there!
I worked as a Java developer for around 8 years and as soon as (after 2 years of start)I looked into the business,the process and the functionalities I started getting a flare for the business and its processes ,analysing and writing the use cases.Even then it took more than 2 years to move to a full fledged business analyst role but the flare for it was always alive somewhere inside me reason being while working as a developer I kept getting involved in the elicitation and requirement analysis ,client interaction,writing use cases,getting involved in drawing UML diagrams,writing functional specifications and BRD documents and all the activities which kept alive ..The BA inside me.
Now once I have moved to the field this idea of writing about my interviews and experiences crossed my mind and here I am..So the motto behind starting this blog is to keep you informed with any good idea,Interview questions I come for Business analyst and business analysis field.
My first interview was with a small product company...remember when its a small company they have lots of expectation from you so they will try to ask you everything possible.
1.How do you prioritize your requirement? Or what is the basis of prioritising your requirement?
Ans :
Typical factors that influence prioritization:
Typical factors that influence prioritization:
1.Benefit
II.Penalty
III.Cost
IV.Risk
V.Dependencies
VI.Time Sensitivity
VII.Stability
VIII.Regulatory or Policy compliance
2.What is an Epic?
It just means “big user story.” Epics generally take more than one or two sprints to develop and test. They are usually broad in scope, short on details, and will commonly need to be split into multiple, smaller stories before the team can work on them.
3.What is Service level agreement?
Ans :Agreement between the service provider and the customer:
A service level agreement (SLA) is a contract between a service provider (either internal or external) and the end user that defines the level of service expected from the service provider. SLAs are output-based in that their purpose is specifically to define what the customer will receive. SLAs do not define how the service itself is provided or delivered. The SLA an Internet Service Provider (ISP) will provide its customers is a basic example of an SLA from an external service provider. The metrics that define levels of service for an ISP should aim to guarantee:
I.A description of the service being provided – maintenance of areas such as network connectivity, domain name servers, dynamic host configuration protocol servers
II.Reliability – when the service is available (percentage uptime) and the limits outages can be expected to stay within
III.Responsiveness – the punctuality of services to be performed in response to requests and scheduled service dates
Procedure for reporting problems - who can be contacted, how problems will be reported, procedure for escalation, and what other steps are taken to resolve the problem efficiently
IV.Monitoring and reporting service level – who will monitor performance, what data will be collected and how often as well as how much access the customer is given to performance statistics
V.Consequences for not meeting service obligations – may include credit or reimbursement to customers, or enabling the customer to terminate the relationship.
VI.Escape clauses or constraints – circumstances under which the level of service promised does not apply. An example could be an exemption from meeting uptime requirements in circumstance that floods, fires or other hazardous situations damage the ISP’s equipment.
Though the exact metrics for each SLA vary depending on the service provider, the areas covered are uniform: volume and quality of work (including precision and accuracy), speed, responsiveness, and efficiency. In covering these areas, the document aims to establish a mutual understanding of services, areas prioritized, responsibilities, guarantees, and warranties provided by the service provider.
The level of service definitions should be specific and measureable in each area. This allows the quality of service to be benchmarked and, if stipulated by the agreement, rewarded or penalized accordingly. An SLA will commonly use technical definitions that quantify the level of service such as mean time between failures (MTBF) or mean time to recovery, response, or resolution (MTTR), which specifies a “target” (average) or “minimum” value for service level performance.
SLAs are also very popular among internal departments in larger organizations. For example, the use of a SLA by an IT helpdesk with other departments (the customer) allows their performance to be defined and benchmarked. The use of SLAs is also common in outsourcing, cloud computing, and other areas where the responsibility of an organization is transferred out to another supplier.
4.What is pareto principle?
Ans : The Pareto principle is a principle, named after economist Vilfredo Pareto, that specifies an unequal relationship between inputs and outputs. The principle states that 20% of the invested input is responsible for 80% of the results obtained. Put another way, 80% of consequences stem from 20% of the causes; this is also referred to as the "Pareto rule" or the "80/20 rule."!--break--This principle serves as a general reminder that the relationship between inputs and outputs is not balanced. For instance, the efforts of 20% of a corporation's staff could drive 80% of the firm's profits. In terms of personal time management, 80% of your work-related output could come from only 20% of your time at work. In Pareto's case, he used the rule to explain how 80% of the wealth is controlled by 20% of the country's population.
5.What estimation techniques you follow in your organization?
Ans :
1.Delphi :Expert judgment and history ,Estimation is shared with expert and corrections are done based on the feedback,Average of 3 estimations are taken
2.Pert(Optimistic +pessimistic+4 most likely value)/6
