This document discusses transitioning from a business analyst to a project manager. It begins by outlining the key differences between BAs and PMs, noting that PMs focus on activities like planning and risk management, while BAs recommend solutions. The document then shares lessons learned from the author's experience as a BA, including the importance of understanding both business and technology needs. It also discusses challenges of being a PM, such as managing stakeholders and communicating issues. Finally, it provides tips for transitioning to a PM role, like getting a coach, involving the team in planning, and properly managing issues and risks.

1. BUSINESS ANALYSIS &
PROJECT MANAGEMENT
Do BAs make good PMs?
Ranjan Kumar Jha, CBAP
Email: ranjanjha@gmail.com
4th April, BA Open, Pune

2. Agenda
1. Difference between Business Analyst and Project
Manager
2. What I learned as a BA
3. What I didn’t know as BA
4. What I Learned as a PM
5. How to transition from BA to PM?

3. Difference between Business Analyst and
Project Manager
• PM conducts ‘activities’ to meet the project requirements
• Planning
• Issue & Risk management
• Coordination, Execution and Reporting

4. Difference between Business Analyst and
Project Manager
• Business Analyst ‘recommends’ solution to enable
organization meets it goals
• Requirements Elicitation, Gathering, Analysis and Management
• Solutions assessment
• Liaison between stakeholders

5. What I learnt as BA
1. Success is in defining what the business need vs what they
want
2. Technology and business are now married – you have to
understand both
3. For the delivery team you’re the ‘client’ and for the client you
are the ‘vendor’
4. PM is your partner – help him to help you
5. One skill that can always be improved is the listening skill

6. What I didn’t know as BA
1. Conducting status meeting is equally boring for the PM - but
is a necessity
2. The PM has more stakeholders to manage – Leadership
teams, Steering committees, Internal Bosses, HR and
Finance
3. Project planning is not an easy task, resource planning is
even more difficult, financial planning is boring
4. Sometime it is more important to get things done and on time
– then to have it done perfectly

7. What I learned as PM
1. A stupid BA can ruin the project
2. Communication is the key, you cannot communicate enough
3. The trick is in managing the Issues and Risk – and
communicating them
4. No one likes the bad news – however it should travel faster
5. Project planning is not an one time activity – it should be
done every day

8. Transitioning From BA to PM
1. Get a coach – who can guide you through things
2. Get a good understanding of the scope, SOW
3. Know your team, they know the details, involve them in
planning and estimation
4. Avoid the temptation of getting in the details
1. Keep a macro view but be ready to get in details when required
5. Issues and Risk are your friends
1. Learn to identify, prioritize and manage them