Test your basic knowledge |

BABOK Task Descriptions

Instructions:
  • Answer 32 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. To define requirements for capabilities needed to transition from an existing solution to a new solution.






2. Create and maintain relationships between business objectives - requirements - other team deliverables - and solution components to support business analysis or other activities.






3. This ensures that requirements specifications & models meet the necessary standard of quality to allow them to be used effectively to guide further work.






4. Meet with stakeholder(s) to elicit information regarding their needs.






5. Understand which models are appropriate for the business domain & solution scope. Identify model interrelationships & dependencies






6. Ensure all needed resources are organized and scheduled for conducting the elicitation activities.






7. Assess whether the organization is ready to make effective use of a new solution.






8. To analyze expressed stakeholder desires &/or the current state of the organization using a combination of textual statements - matrices - diagrams & formal models






9. To manage the performance of business analysis activities to ensure that they are executed as effectively as possible.






10. To identify new capabilities required by the enterprise to meet the business need.






11. To determine the most viable solution approach to meet the business need in enough detail to allow for definition of solution scope and prepare the business case.






12. To manage knowledge of requirements following their implementation.






13. Identify factors other than requirements that may affect which solutions are viable.






14. This to done to solutions in order to determine how closely they meet stakeholder and solution requirements.






15. To determine if an organization can justify the investment required to deliver a proposed solution.






16. Validate that the stated requirements expressed by the stakeholder match the stakeholder's understanding of the problem and the stakeholder's needs.






17. Allocate stakeholder and solution requirements among solution components and releases in order to maximize the possible business value given the options and alternatives generated by the design team.






18. Covers the id of stakeholders who may be affected by a proposed initiative or who share a common business need - id appropriate stakeholders for the project or project phase - & determining stakeholder influence &/or authority regarding the approval






19. To define which new capabilities a project or iteration will deliver.






20. Evaluate functioning solutions to understand the value they deliver and identify opportunities for improvement.






21. The purpose of this is to ensure that all reqs support the delivery of value to the biz - fulfill its goals & objectives - & meet a stakeholder need.






22. Ranking of requirements ensures that analysis and implementation efforts focus on the most critical requirements. Non-negiotiable Demands - Unrealistic tradeoffs






23. This ensures that a solution meets the business need and determine the most appropriate response to identified defects.






24. Determine the activities that must be performed & the deliverables that must be produced - estimate the effort required to perform that work - & id the mgmt tools required to measure the progress of those activities &deliverables.






25. To select and structure a set of requirements in an appropriate fashion to ensure that the requirements are effectively communicated to - understood by - and usable by a stakeholder group or groups.






26. Describes the proposed structure & schedule for communications regarding BA activities. Record & organize the activities to provide a basis for setting expectations for BA work - meetings - walkthroughs - & other communications.






27. Describes how to select an approach to performing BA - which stakeholders need to be involved in the decision - who will be consulted regarding & informed of the approach - & the rationale for using it.






28. This is essential for bringing stakeholders to a common understanding of requirements.






29. Obtain and maintain consensus among key stakeholders regarding the overall solution scope and the requirements that will be implemented.






30. Define the process that will be used to approve requirements for implementation and manage changes to the solution or requirements scope.






31. Record the information provided by stakeholders for use in analysis.






32. Identify and define why a change to organizational systems or capabilities is required.