CBAP exam prep Application Tips

cbap ccba exam prepGet yourself ready to be eligible for the IIBA-CBAP Exam !
Read our CBAP exam prep Application Tips here below.

Thanks to for providing this valuable content

How to declare business analysis hours ?

  • Declare at least 30% more hours than needed
  • DO NOT declare project management hours
  • DO NOT select the red marked categories below because they represent PROJECT WORK

Business Analysis Planning & Monitoring

  • Planned business analysis approach
  • Conducted stakeholder analysis
  • Planned business analysis activities
  • Estimated requirements activities (e.g., milestones, work units, level of effort, duration,)
  • Planned business analysis communication
  • Planned requirements management process
  • Determined what requirement attributes need to be captured
  • Planned, monitored and reported on business analysis performance
  • Measured and reported on requirements activity
  • Identified and documented project team roles and responsibilities
  • Identified project risks
  • Determined SDLC approach for project
  • Created the project plan
  • Conducted resource planning
  • Conducted project team meetings
  • Conducted BA team performance reviews
  • Managed team of BAs (i.e. accountable for conducting regular one on one meetings, assessing individual’s ongoing skills and performance, negotiating compensation increases, determining areas for improvement and professional development needs, approving vacation time, overtime, etc.)
  • Planned operational support activities based on business analysis deliverables


  • Prepared for requirements elicitation
  • Conducted elicitation activities
  • Facilitated requirements workshop
  • Documented the results of elicitation activities
  • Validated elicitation results

Requirements Management & Communication

  • Managed solution and requirements scope (e.g., baseline, structure, impacts, change management and approval process
  • Obtained sign-off
  • Managed requirements change
  • Managed and resolved requirements conflicts
  • Established requirements baseline
  • Structured requirements for traceability
  • Determined appropriate format to present requirements
  • Created a requirements package
  • Conducted a presentation of the requirements to stakeholders
  • Communicated requirements
  • Adjusted project scope based on changes to requirements
  • Conducted design walkthroughs
  • Prepared and conducted project progress presentation for senior management

Enterprise Analysis

  • Define the business needs
  • Identify business problem or opportunity
  • Determined gap(s) in capabilities to meet the business needs
  • Determined solution approach
  • Conducted feasibility studies for solution options
  • Identified potential high level solutions
  • Defined solution scope
  • Developed a business case
  • Documented system/application architecture
  • Determined project scope
  • Selected and prioritized projects
  • Launched a new project
  • Created the project charter

Requirements Analysis

  • Determined priority and relative importance of requirements
  • Organized requirements so that they are understood by all stakeholders
  • Documented dependencies and interrelationships between requirements
  • Specified and modeled requirements
  • Created and documented as-is models
  • Determined requirement assumptions and constraints
  • Verified requirements
  • Conducted structured walkthroughs
  • Validated requirements
  • Traced requirements back to the business case
  • Delivered use cases
  • Determined work that needs to be done in the project based on requirements
  • Evaluated risk associated with implementing certain requirements
  • Created training materials
  • Created user guides/manuals
  • Created and documented solution design
  • Created service level agreements

Solution Assessment & Validation

  • Assessed business value delivered by proposed solutions
  • Allocated requirements among releases and/or solution components
  • Determined organizational readiness to effectively operate the new solution
  • Defined transition requirements to move to the new solution
  • Validated a solution
  • Defined acceptance criteria for the solution
  • Assessed business impact of defects and issues
  • Evaluated the quality of the solution
  • Identified opportunities for improvement post-implementation
  • Created the test strategy and test plan
  • Created the test cases
  • Executed test cases
  • Tracked and managed the defects
  • Managed the quality assurance/testing process and resources
  • Obtained user acceptance testing signoff
  • Created the implementation plan
  • Managed the solution selection committee
  • Delivered training
  • Evaluated technology options

Thanks to for providing this valuable content

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.