Business analysis is a service related to the identification of business needs and determining solutions to business problems of the customer. Solutions often include a software-systems development component, but may also consist of process improvement, organizational change or strategic planning and policy development.
increase in the average on-time delivery
improvement in the average on-budget performance
more projects delivering right functionality for business
User Stories often start out the same way as Use Cases, each of which describes one way to use the system, is centered around a goal, is written from the perspective of a user, uses the natural language of the business, and - on its own - does not tell the whole story.
Functional decomposition is the process of resolving a functional relationship into its constituent parts in such a way that the original function can be reconstructed (i.e., recomposed) from those parts by function composition.
Backlog management is the process by which the product owner (often in collaboration with others) adds, adjusts, grooms, and prioritizes backlog items within the backlog to make sure the most valuble product is shipped to customers. An oversized product backlog is a problem.
The MoSCoW method is a prioritization technique used in management and business analysis to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement; it is also known as MoSCoW prioritization or MoSCoW analysis.
Interview technique allowing to elicit information from a person or group of people through a convertation with an interviewee, with questions and documented responses.
Brainstorming targets creative thinking about a problem in order to come up with a set of new ideas, options, and approaches. The approach taken to brainstorming is twofold: a creative and wide-open idea generation session followed by idea reduction activities.
Requirements workshops are structured meetings where a selected group of stakeholders works together to define or refine a set of project requirements. During a requirements workshop, specific requirements may also be presented to make everyone familiar with the solution scope and current requirements.
Decision analysis allows the business analyst to examine and model the consequences of different decisions before actually making or recommending a particular one. The business analyst’s goal is to make or recommend a well-informed decision. This is typically done using some form of mathematical modeling to assess possible outcomes. In many cases, decision analysis involves very complex models created using sophisticated software applications.
Put it simply, Root Cause analysis is a careful examination of a particular situation to discern the underlying reasons for a specific problem or variance. The Business Analysis Body Of Knowledge (BABOK) defines this as a “structured examination of the aspects of a situation to establish the root causes and resulting effects of the problem”. Depending upon the rigorousness of the examination conducted, it is possible to identify several layers of symptoms before reaching the underlying cause or causes of a particular situation.
Sequence diagrams are used to model the logic of usage scenarios, by showing the information passed between objects in the system through the execution of the scenario. The sequence diagram may be used in object-oriented analysis to validate class diagrams against use cases, or to show the timing of interactions between entities within the system scope.
Metrics/KPIs are high-level snapshots of an organization or a business process based on specific predefined measures. KPIs are typically captured and conveyed in a combination of reports, spreadsheets, or charts. In developing KPIs, a user or a developer defines target performance levels and then decides on the best way to represent variance from that target.
Other techniques used by our team include: Document Analysis, Focus Groups, Interface Analysis, Observation, Prototyping, Survey/Questionnaire etc.
