Raspberry Pi 5: Challenges and Solutions in Bringing up an OpenGL/Vulkan Driv...
3 rules to live by
1. 3 Rules to Live By
A BA’s Guide to Better Developer
Relationships
Presenter: Tamara Copple, Business Analyst
2. Objectives
If I am successful, you should leave with at least one new idea or technique
for improving relations with your developers.
BABOK areas covered: Chapter 9 - Underlying Competencies
● 9.3 - Business Knowledge
● 9.4 - Communication Skills
● 9.5 - Interaction Skills
3. “A mentor is someone whose hindsight
can become your foresight.”
~ Chinese Fortune Cookie, March 2018
5. Lesson 1: Do your Homework
BABOK Section 9.3.3 and 9.3.4
➢ Professional Infancy:
○ Research first, then
ask for help.
○ Show your work.
6. Lesson 1: Do your Homework
BABOK Section 9.3
Professional Infancy:
“As a business analyst on an IT project, it is important to have a general
understanding of software systems. Basic knowledge of servers, databases, and
client side technology, augmented with solid logical, systems-thinking will do.
Combining both will lead to more effective communication with the implementation
team.” ~ Laura Brandenburg
Interpretation: Being a little technical never hurts. Know your tech stack.
7. Lesson 1: Do your Homework
BABOK Section 9.4.4 & 9.5.3.3
Professional Infancy:
Get to know your developers.
8. Lesson 2: Know Your Business
BABOK 9.3.4
Professional Infancy:
○ Know your product; become the SME.
“Even if you aren’t afraid to put your devs in front of the client, they
have other responsibilities. You need to be able to answer business
stakeholders’ questions and not depend on us to bail you out in a
meeting.” ~Mark the Mentor, circa 2002
9. Lesson 2: Know Your Business
BABOK 9.3.2
Professional Infancy:
○ Modern BA’s are expected to know
everything from daily operations
minutia to industry trends.
10. Lesson 3: Manage Expectations
BABOK 9.4
Professional Infancy:
○ Overcommitment is the #1 complaint heard from devs about their
PMs and BAs - includes talking when you have no idea what you
are talking about.
○ Not understanding the business and not talking to the business is
#2.
11. Lesson 3: Manage Expectations
BABOK 9.5.3.3
Professional Infancy:
○ “Before you feel guilty about not meeting expectations, you should
probably figure out what they are.” ~ Tiffany Dufu
○ Developers have more business knowledge than we sometimes
give them credit for but we need to give them context.
13. Objectives Recap
If I am successful, you should leave with at least one new idea or technique
for improving relations with your developers.
BABOK areas covered: Chapter 9 - Underlying Competencies
● 9.3 - Business Knowledge
● 9.4.4.3 - Communication Skills Non-Verbal Communication
Effectiveness Measures
● 9.5.3.3 - Interaction Skills -Teamwork Effectiveness Measures
14. Beyond BABOK - Recommended Reading
➢ White paper: Business Analysis - Positioning for Success
➢ Blog: How the IIBA has Evolved Over the Last 15 Years
➢ Blog: Sharing Business Context With Your Team
➢ Blog: Why BA roles sometimes require technical skills
➢ Drop the Ball - Tiffany Dufu
➢ How to Have a Good Day - Caroline Webb
➢ The Five Dysfunctions of a Team - Patrick Lencioni
tamara.copple@gmail.com | linkedin.com/in/tamaracopple
Editor's Notes
DST - Professional Infancy in a Warterfall
Devs should never be client facing
You will forever be the SME
You will support the product long after you have moved on to other areas of the company
Devs don’t know the business (especially not the way the BA should)
Then: Mark’s advice was, “always demonstrate what you’ve done to answer the question for yourself before you talk to your developer. At a minimum it shows that you respect their time enough not to ask them to find answers for you that you were perfectly capable of getting for yourself. At best, if you eliminate the easy answers, it’s worth the company’s money for the developer to look into it further. ” To this day it irritates the heck out of me not to have access to a SQL database where I can just run a quick report. How many policies do we have where ____ is in play? for example.
Anecdote: Meeting on Friday? Better bring beer. Dev says he doesn’t like having to jump headspace from problem A to problem B. It disrupts his productivity, introducing delays.
Become a SME about your developers too.
Familiarize yourself with your team’s software stack.
Get to know your industry.
Regularly seek out opportunities to observe “business as usual.”