Welcome to our Chapter!  Our mission is to engage and support our members and community partners through educational events, mentorship, and networking opportunities. We promote ongoing professional development and certification specific to the standards and practices of Business Analysis.

                                                       Welcome to IIBA Research Triangle Park - Raleigh Chapter
IIBA RTP Raleigh Chapter is a vibrant community of Business Analysts from Raleigh, Durham and Chapel Hill as well as Western and Eastern areas of North Carolina offering networking opportunities as well as professional and career development for BA’s.  Our Chapter is run by volunteers who dedicate their time and efforts for the BA community.  It is led by an elected Board of Directors and has several committees which support the activities of the Chapter.  If you are a BA living in this area we strongly encourage you to become an active member of our Chapter and get involved.
Membership
Upcoming Events

October 2026

S
M
T
W
T
F
S
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Home Page Stories
Eight Reasons to Join IIBA and Why
Our VP Membership Dawn Kibler shares her 8 reasons for joining and participating IIBA.  She augments with WHY it Matters, including why joining is especially valuable if you want to stay current, connect with peers, and move into more senior roles.
Read more...
Analyst Catalyst Blog
Stakeholder-Informed vs. Validated: A Marketplace Case Study
Stakeholder feedback can identify genuine needs, but it doesn’t always reveal which needs will drive action. This case study explores how behavioural evidence led us to reassess acquisition priorities, feature context, and the assumptions behind our next experiment.
Your AI Can't Fix a Process You Haven't Looked At
On this episode of Business Analysis Live, Oge Nwachukwu explains why AI applied to a broken process just makes the brokenness happen faster.
AI-Assisted Prototyping: Turning Requirements Into Interaction
Comprehensive requirements documentation doesn't automatically create shared understanding. When stakeholders can interact with a working representation of the proposed solution while requirements are still being shaped, ambiguity surfaces earlier (and cheaper).