I’ve been CBAP certified for more than a year and a half now and I’ve recently earned my PBA certification as a participant in the pilot phase that PMI launched earlier this year. Thus I’m one of the first batch of certified PBA (less than 170 worldwide) and currently the only one in Lebanon with any of the 2 certifications.
In this context, I’d like to share with you some insights about the 2 certifications with a comparison to help you choose the right certification for you.
To start with, the International Institute of Business Analysis (IIBA) has been around for more than 10 years and it works on the development, expansion and promotion of business analysis. While the Project Management Institute (PMI) has been around for more than 45 years and it works on the development, expansion and promotion of project management.
In this context, the 2 organizations are starting from a different perspective about Business Analysis, what it means, what it entails and the reason they developed their certification (IIBA’s CCBA and CBAP Vs PMI’s PBA).
For IIBA, business analysis is a full time job and has a more holistic vision about the role of a business analyst. For IIBA, the Business Analyst’s work is not limited to only projects, requirements management, communication and evaluation of the end result, but rather it takes more of an enterprise perspective and can even assist at the strategic level.
While PMI’s focus on business analysis is more of a hybrid role for the Project and Program Managers with a special focus on proper requirements elicitation/collection, analysis, scope design, mapping, tracking and communication of those requirements with the appropriate stakeholders. In this context, PMI’s perspective on Business Analysis is more of a Project and Program based work rather than Operational or Enterprise related work. This does make sense as PMI is concerned mostly with the success of project and programs rather than in starting a new profession by itself.
Therefore, both certification will not be contradicting but rather can complement each other in some places while they have completely different audience in other cases.
Below is a set of comparative bullet points.
- IIBA has been developing the Business Analysis Body of Knowledge over several years and are now in the 2nd edition of the BABOK with the 3rd due on April 2015.
- CBAP training and certification will cover numerous details, tools and techniques for those aiming for a career in business/solution/enterprise analysis.
- CBAP already has its name and is well respected among Business Analysis professionals.
- CBAP fits in excellently for people working in Consultancy, IT, Telecom, Hard and Software Development.
- For full time BA’s, CBAP provides a more comprehensive set of knowledge than it’s PMI’s counterpart.
- PMI has recently acquired 2 companies that have a wealth of knowledge about requirements management, project and product design, assessments and the like.
- PMI has a very big marketing department with massive outreach, global partners, training providers and a global network of chapters.
- PBA is more focused on Business Analysis work within Project and Program Management, with a special focus on requirements management, scope management and communication.
- Professionals certified by PMI (ACP, CAPM, PMP, PgMP, PfMP) will find it more natural and smooth to earn the PBA as it is aligned with PMI’s framework. For hybrid PM-BA work, it’s sufficient as the PM will not necessarily need all the info presented by IIBA.
I hope that helps and if you have any questions or suggestions, don’t hesitate to let me know.
Systems Thinking is based on the field of system dynamics, founded by MIT professor Jay Forrester in 1956. The idea behind systems thinking is to be used when analyzing change, interventions and solutions to consider how the component being under study is interacting with other components in the system.
So for example, if we’re trying to introduce new roles in the organization or solve a social issue or introduce new projects and initiatives in the community or organization…we need to consider how those interact with other parts of the system. Many of the traditional methods take a sequential approach to analyzing issues, systems think
This leads us to actually ask, what is a system? Well in a nutshell, a system is a group related, interdependent, bound and related components that interact together. So the computer you’re using is a system, organization you work in is a system, the city you’re in is a system, the country you’re in is a system. In this context, systems can be a “component” of a bigger system. Thus our world is constantly interconnected and has multiple influences from the broader system on the smaller ones, and vice versa.ing on the other hand focuses on the big picture and how are it’s components interacting thus a more complex and iterative approach.
For example, the company’s “system” is made up of:
- Policies & Procedures
- Human Capital
- Facilities & Equipment
So to introduce a change in one of those 3 elements, whether it’s team performance or overall cost reduction, there will be an impact on the other 2 elements and thus in many organizations instilling some change in one element will end up leading to un-expected changes in the other and thus the “original” problem would be resolved, but other problems would’ve popped up.
The key benefit of Systems Thinking is that it provides a better way for analysis and for solving most complex problems that are plaguing our world from governments to communities to business and so on.
Systems Thinking is being used in very wide spectrum of fields today and this proves that the people are becoming aware of it’s value. Some of the fields where it is being utilized are:
- Engineering & Construction
- Management & Consultancy
- Health & Medical Services
- Manufacturing & Industry
- Business Analysis
- Project Management
- Policy Making & Governance
- Community Development
- Computing & Information Technology
- Sustainable Development
In conclusion, with the increasing complexity of our world today it becoming a necessity to be able to see the “big picture” and understand the systems we are working with or else our proposed solutions and improvements will fail to reach the impact expected with long lasting sustainability.
In the following article I will try to extract the most notable lessons learned from my experience in the IT field for the past few years.
A quick overview for my dear readers who don’t know my background, I studied Computer Science(CMPS) at the American University of Beirut(AUB) while working at the Computing and Networking Services (CNS) on campus. Following my graduation I worked in IT development at a banking/financial institution while doing some free lance web-development and IT related consultancies.
Overall, I had my share of working on both hardware and software…and the lessons learned all fit in together and I will be pinpointing them as briefly as possible in the below lines:
- No problem is too complex. The key to success in this is to decompose the complexity of the issue into smaller manageable parts. Afterwards one only needs to resolve a group of simpler issues that fit in together.
- Automation is the key to ongoing growth and sustainability of many companies. This is due to the fact that any requested behavior can be mimicked and coded accordingly, with as many exceptions as needed, replacing the need for human interaction with machines.
- Technology is advancing faster than we expect. The rate at which technology is evolving allows for sophisticated solutions to be designed and implemented with growing speed and ease. What was nearly impossible 10 years ago can be developed in a week today.
- IT team leaders can make or break the company. One of the keys for successful IT teams is a team leader who knows how to leverage the expertise of the team, provide enough autonomy while still closely overseeing the work.
- Programming in multiple languages is becoming a must. Knowing one programming language …in our times…is no longer enough to keep with the pace of advancement and to develop the solutions the best fit the needs.
- GUI is king. Graphical user interface and packaging became as important as the actual functionality of the solutions requested as users demand the simplest and most intuitive tools they can have. People want eye-candy with minimal intellectual effort to use the applications.
In this context, and after checking the above with some of my friends and colleagues, the same lessons apply in most fields and I will definitely be taking those lessons with me in my consultancy and management work from now on.
I hope they help you in one way or another in your career…and I’m open for your comments and suggestions as always. 🙂