#1
2nd January 2016, 11:39 AM
| |||
| |||
Certifications for Business Analyst
I want to get information about the Business Analyst Certification means PMI Professional in Business Analysis Prerequisites as well as Exam Content Outline. So here can you provide me information about it?
|
#2
2nd January 2016, 11:42 AM
| |||
| |||
Re: Certifications for Business Analyst
I would like to tell you about the Business Analyst Certification mean PMI Professional in Business Analysis Prerequisites as well as Exam Content Outline as you want. Prerequisites Secondary degree (high school diploma, associate’s degree or the global equivalent) 7,500 hours of business analysis experience 2,000 hours working on project teams 35 contact hours of education in business analysis Or Bachelor’s degree or the global equivalent 4,500 hours of business analysis experience 2,000 hours working on project teams 35 contact hours of education in business analysis Exam Content Outline Domain Percentage of Items on Test Domain 1. Needs Assessment 18% Domain 2. Planning 22% Domain 3. Analysis 35% Domain 4. Traceability and Monitoring 15% Domain 5. Evaluation 10% KNOWLEDGE AND SKILLS 1. Analytic tools and techniques (for example, decomposition, progressive elaboration, dependency analysis, gap analysis, impact analysis, risk analysis, and assessment) 2. Backlog management 3. Business rule analysis tools and techniques (for example, decision table, decision tree, rule catalog) 4. Change control tools and techniques 5. Collaboration tools and techniques 6. Communication skills, techniques, and tools (for example, technical writing, business writing, working with virtual teams, presentation skills, verbal and nonverbal communication) 7. Conflict management and resolution tools and techniques 8. Contingency planning 9. Data analysis tools and techniques (for example, data model, data dictionary, state diagram) 10. Decision making tools and techniques (for example, Delphi technique, multi-voting, consensus building, options analysis) 11. Development methodologies (for example, agile, iterative, incremental, waterfall) 12. Documentation management tools and techniques 13. Elements of a requirements management plan 14. Elicitation tools and techniques (for example, brainstorming, focus groups, interviewing techniques, workshop facilitation, observation, document analysis, research, surveys, and questionnaires) 15. Estimating tools and techniques (for example, estimation poker, quadrant analysis, averaging) 16. Facilitation tools and techniques 17. Interface analysis (for example, prototyping, storyboarding, interoperability) 18. Leadership principles and skills 19.Lessons learned and retrospectives 20.Measurement tools and techniques (for example, Planguage, service level agreement) 21.Negotiation tools and techniques 22.Organization assessment (for example, organizational readiness) 23.Planning tools and techniques (for example, strategic and tactical) 24.Political and cultural awareness 27.Process analysis tools and techniques (for example, user stories, use cases, process model, data flow diagrams, dependency graphs, events) 28.Project methodologies (such as waterfall, agile, iterative, lean) and how they impact requirements and business analysis practices 29.Quality management 30.Reporting tools and techniques 31.Requirements traceability tools and techniques 32.Requirements types (for example, business, stakeholder, solution, transition, project, and quality) 33.Root cause analysis (for example, Ishikawa/fishbone, 5 Whys) 34. Scheduling tools and techniques 35.Stakeholder analysis (for example, personas, role definition [RACI], job analysis, skills assessment) 36.Systems thinking 37.Validation tools and techniques (for example, acceptance criteria [for example, given-when-then] User Acceptance Testing) 38.Valuation tools and techniques (for example, cost-benefit analysis, force field analysis, Kano model, net promoter score, purpose alignment model, SWOT analysis, value stream map) 39.Verification methods and techniques (for example, inspection, test, walk-through, desk checking, peer review) 40.Version control tools and techniques |
|