B2T Training

Applying for the CBAP (IIBA BA certification) is a bit daunting. The application process requires that you show that you really do have more than 5 years business analysis experience. This is very important because we, as a profession, want the certification to be meaningful and strong. We know that simply memorizing a bunch of BA terms and techniques does not make a person a Business Analyst. It is our experience that makes us what we are.

So, be aware that the application itself is more important than the CBAP exam in determining your eligibility for certification. Below are some hints for developing an application that accurately describes your experience.

1. Be careful documenting your PM work. Although many of us have done PM work, that work does not count towards your BA experience. Be sure to describe planning activities that you have done as requirements planning, stakeholder analysis, scoping the area of study, or scoping the requirements elicitation process.

2. Be careful documenting your QA work. Although many of us have done QA work, that work does not count towards your BA experience. Be sure to describe testing activities that you have done as identifying test cases that assess business requirements met, tracing test cases back to business requirements, reviewing QA test plans, cases, scripts for adherence to business requirements, reviewing test results for adherence to business requirements.

3. Don't forget about usability work. Many of our organizations have just started using the word usability but most of us have been doing it for years. Whenever you have helped your team design a screen that is more intuitive for its users you are designing usability.

4. Don't be afraid of Enterprise Analysis. You have probably done more Enterprise Analysis than you realize. If you have discussed possible project ideas with your business stakeholders and helped them determine if the project was a good idea (feasibility, alignment with business goals and architecture), you have experience in Enterprise Analysis.

5. Don't detail descriptions of specific projects. Although fascinating to you and your project team, the IIBA application reviewers don't need to know details about the application that you worked on. Describe projects with short, clear names that an outside reviewer would understand. For example: instead of saying: "The DEFSSC project interfaced the INCC system with the EFT outlink." Say something like: "The project involved linking the existing customer purchase system with an outside credit card processing service."

6. Do give specific examples of the types of requirements that you have elicited, analyzed, documented, communicated, and helped to implement. This should be the core of your application. Example: I developed a detailed business model of the payroll processing area by: interviewing 10 business stakeholders; developing a workflow model including over 15 diagrams; presenting the workflow model to the stakeholders; revising the model based on feedback; and obtaining approval of the recommended workflow changes.

7. Do document all of the work you have done in the last 10 years. Showing more than the required 7500 hours allows for a few items to be rejected but your application to be accepted. Document everything that you can.

8. Do enjoy the writing! How often do you get to brag about your accomplishments? Don't dread the writing, enjoy it! Good Luck, Barb