Projects may fail to deliver the true needs of its users. Why? Because the project team may not have elicited the requirements from the users. In this article, let's explore why project managers need business analysts (i.e. BAs), the benefits, and how to add BAs to your organization.
The Standish Group says three of the biggest factors that lead to failed and challenged projects are:
- Lack of user input
- Incomplete requirements
- Changing requirements
We should plan and respond to these risks. How can we do this? We should add skilled requirements analysts to our project teams.
When Do Project Managers Need a Business Analyst?
The role of the project manager is to achieve the project's goals or objectives. So, who performs the business analysis tasks for the projects? Well, that depends.
For small projects, the project manager may assume many roles including but not be limited to:
- Project manager
- Requirements analyst
- Facilitator and scribe
- Chief bottle washer (just kidding)
For larger projects, project managers must find ways to complete project tasks through others. They must not fall into the trap of doing everything themselves, especially things one is not skilled in. Wise project managers recruit team members with the necessary skills and talents.
Business analysts bring a wide range of business analysis skills including requirements engineering skills:
Notice how these skills directly relate to the top reasons for failed or challenged projects:
- Help to ensure appropriate user and stakeholder input into the requirements process.
- Drive an efficient process to define and validate requirements reducing the potential of missed or partial requirements.
- Help to specify requirements upfront and reduce changes later when it is more expensive.
The project manager will have increased difficulty in achieving the project's objectives when requirements are not properly defined and understood.
The Benefits of Business Analysis
I have benefited immensely from the business analyst's expertise in the following ways:
- Defining high-level business requirements (i.e., goals or objectives)
- Defining user-level requirements (i.e., mapping of business processes)
- Defining detailed software requirements (i.e., functional and non-functional requirements)
- Defining requirements traceability
- Defining business rules
- Business modeling (e.g., prototypes, context diagrams, user stories)
- Managing requirements backlog
- Testing or providing assistance to the Quality Assurance team
- Estimating return on investment for projects
Adding Business Analysts to Your Organization
Introducing business analysis into your project teams may be a significant change. Be sure to define and clarify the roles of your team members.
It is helpful to clarify the reporting relationship between the project manager and the business analyst. Will the business analyst report to the project manager? Will the business analyst and the project manager have a peer-to-peer relationship?
Whatever you decide, map out the roles and reporting relationship in a RASI or RASIC diagram or a responsibility chart. This greatly reduces the potential for conflict.
Consider one last point when introducing business analysts to your teams—determine the pace of change. I favor a gradual change while educating stakeholders on reasons for the change. If you surprise your stakeholders with unexpected change, they may resist the change and undermind your efforts.
Boosting the Project Manager's Business Analysis Skills
For some projects, the project manager may have to perform the business analysis role. However, many project managers lack business analysis skills. Fortunately, there are ways to boost your skills.
The International Institute of Business Analysis (IIBA) offers the CBAP (Certified Business Analysis Professional) certification. The Project Management Institute (PMI) has also created the new PMI-PBA (Professional in Business Analysis) certification to equip project managers with stronger business analysis skills.
Which is better? Both are excellent. The CBAP is broader than the PMI-PBA and includes strategic and enterprise business analysis activities. The PMI-PBA focuses on requirements management in the context of projects and programs.
Project Risk Coach Tips
Sign up for the weekly Project Risk Coach blog posts and receive the Project Management Plan Checklist. This will allow you to deliver projects with fewer problems and greater value.
"Intelligent leadership, creative communication and depth of technical skill all describe Harry Hall." –John Bartuska, Director of HR–ONUG Communications