GoConqr has a new look! Let us know what you think.

Sign up free

Flashcards

BABOK 3 - Techniques & Purposes

Giovanni Basso Análise de Negócios CBAP English 50 cards

Cards in this deck (50)

  1. 1Used to define the requirements, outcomes, or conditions that must be met in order for a solution to be considered acceptable to key stakeholders. Measures used to assess a set of requirements in order to choose between multiple solutions.Acceptance & Evaluation Criteria
  2. 2Used to record, track, and prioritize remaining work items.Backlog Management
  3. 3Used to manage performance in any business model, organizational structure, or business process.Balance Scorecard
  4. 4Conducted to improve organizational operations, increase customer satisfaction, and increase value to stakeholders.Benchmarking & Market Analysis
  5. 5A way to foster creative thinking about a problem. Its aim is to produce numerous new ideas, and to derive from them themes for further analysis.Brainstorming
  6. 6Provides a framework for scoping and planning by generating a shared understanding of outcomes, identifying alignment with strategy, and providing a scope and prioritization filter.Business Capability Analysis
  7. 7A justification for a course of action based on the benefits to be realized by using the proposed solution, as compared to the cost, effort, and other considerations to acquire and live with that solution.Business Cases
  8. 8Describes how an enterprise creates, delivers, and captures value for and from its customers.Business Model Canvas
  9. 9Used to identify, express, validate, refine, and organize the rules that shape day-to-day business behaviour and guide operational business decision making.Business Rule Analysis
  10. 10Encourages participants in an elicitation activity to collaborate in building a joint understanding of a problem or a solution.Collaborative Games
  11. 11Used to organize the business vocabulary needed to consistently and thoroughly communicate the knowledge of a domain.Concept Modelling
  12. 12Used to standardize a definition of a data element and enable a common interpretation of data elements.Data Dictionary
  13. 13Show where data comes from, which activities process the data, and if the output results are stored or utilized by another activity or external entity.Data Flow Diagrams
  14. 14Used to improve decision making by finding useful patterns and insights from data.Data Mining
  15. 15Describes the entities, classes or data objects relevant to a domain, the attributes that are used to describe them, and the relationships among them to provide a common set of semantics for analysis and implementation.Data Modelling
  16. 16Formally assesses a problem and possible decisions in order to determine the value of alternate outcomes under conditions of uncertainty.Decision Analysis
  17. 17Shows how repeatable business decisions are made.Decision Modelling
  18. 18Used to elicit business analysis information, including contextual understanding and requirements, by examining available materials that describe either the business environment or existing organizational assets.Document Analysis
  19. 19Used by business analysts and other stakeholders to forecast the cost and effort involved in pursuing a course of action.Estimation
  20. 20Used to understand the financial aspects of an investment, a solution, or a solution approach.Financial Analysis
  21. 21A means to elicit ideas and opinions about a specific product, service, or opportunity in an interactive group environment. The participants, guided by a moderator, share their impressions, preferences, and needs.Focus Grops
  22. 22Helps manage complexity and reduce uncertainty by breaking down processes, systems, functional areas, or deliverables into their simpler constituent parts and allowing each part to be analyzed independently.Functional Decomposition
  23. 23Defines key terms relevant to a business domain.Glossary
  24. 24Used to identify where, what, why, when, how, and for whom information is exchanged between solution components or across solution boundaries.Interface Analysis
  25. 25A systematic approach designed to elicit business analysis information from a person or group of people by talking to the interviewee(s), asking relevant questions, and documenting the responses. It can also be used for establishing relationships and building trust between business analysts and stakeholders in order to increase stakeholder involvement or build support for a proposed solution.Interviews
  26. 26Used to capture and assign responsibility for issues and stakeholder concerns that pose an impact to the solution.Item Tracking
  27. 27Used to compile and document successes, opportunities for improvement, failures, and recommendations for improving the performance of future projects or project phases.Lessons Learned
  28. 28Used to measure the performance of solutions, solution components, and other matters of interest to stakeholders.Metrics & KPIs
  29. 29Used to articulate and capture thoughts, ideas, and information.Mind Mapping
  30. 30Examines the requirements for a solution that define how well other requirements must perform. It specifies criteria that can be used to judge the operation of a system rather than specific behaviours of the system.Non-Functional Req. Analysis
  31. 31Used to elicit information by viewing and understanding activities and their context. It is used as a basis for identifying needs and opportunities, understanding a business process, setting performance standards, evaluating solution performance, or supporting training and development.Observation
  32. 32Used to describe the roles, responsibilities, and reporting structures that exist within an organization and to align those structures with the organization's goals.Organizational Modelling
  33. 33Provides a framework for business analysts to facilitate stakeholder decisions and to understand the relative importance of business analysis information.Prioritization
  34. 34Assesses a process for its efficiency and effectiveness, as well as its ability to identify opportunities for change.Process Analysis
  35. 35Used to show how work is carried out and is a foundation for process analysis.Process Modelling
  36. 36Used to elicit and validate stakeholder needs through an iterative process that creates a model or design of requirements. It is also used to optimize user experience, to evaluate design options, and as a basis for development of the final business solution.Prototyping
  37. 37Used to evaluate the content of a work product.Reviews
  38. 38Identifies areas of uncertainty that could negatively affect value, analyzes and evaluates those uncertainties, and develops and manages ways of dealing with the risks.Risk Analysis & Management
  39. 39Used to ensure coverage of activities by denoting responsibility, to identify roles, to discover missing roles, and to communicate results of a planned change.Roles & Permissions Matrix
  40. 40Used to identify and evaluate the underlying causes of a problem.Root Cause Analysis
  41. 41Define the nature of one or more limits or boundaries and place elements inside or outside those boundaries.Scope Modelling
  42. 42Used to model the logic of usage scenarios by showing the information passed between objects in the system through the execution of the scenario.Sequence Diagrams
  43. 43Assist the business analyst in analyzing stakeholders and their characteristics. This analysis is important in ensuring that the business analyst identifies all possible sources of requirements and that the stakeholder is fully understood so decisions made regarding stakeholder engagement, collaboration, and communication are the best choices for the stakeholder and for the success of the initiative.Stakeholder List, Map, or Personas
  44. 44Used to describe and analyze the different possible states of an entity within a system, how that entity changes from one state to another, and what can happen to the entity when it is in each state.State Modelling
  45. 45Used to elicit business analysis information — including information about customers, products, work practices, and attitudes — from agroup of people in a structured way and in a relatively short period of time.Survey or Questionnaire
  46. 46A simple yet effective tool used to evaluate an organization's strengths, weaknesses, opportunities, and threats to both internal and external conditions.SWOT Analysis
  47. 47Describes how a person or system interacts with the solution being modeled to achieve a goal.Use Cases & Scenarios
  48. 48A small, concise statement of functionality or quality needed to deliver value to a specific stakeholder.User Stories
  49. 49Assesses the ability of a vendor to meet commitments regarding the delivery and the consistent provision of a product or service.Vendor Assessment
  50. 50Bring stakeholders together in order to collaborate on achieving a predefined goal.Workshops

Information

Description
Front: the purpose of a business analysis technique. Back: the name of the technique.
Created by
Giovanni Basso
Views
53
Rating

More on Business analysis techniques and skills

Feedback

What is it about?

What do you think of the new look?

How do you like it?