What Does a Technical Business analyst do?

Feb 17, 2019

1113 Views

0 Comments

The function of a technical business analyst is to bridge between business and technical teams. This can be undertaken in various forms. First, the bridging can be done by translating business requirements into technical artifacts. The analyst must be able to assess the business and note the basic r...

Do Business Analysts Need to Know SQL????

While many business analysts may be able to get by without ever writing a single line of code, the ability to write and interpret SQL queries can greatly increase your effectivenes...

Simple Steps for Managing the Day-To-Day of Digital Projects

No matter what type of project you’re working on, how big your team is, or what your specific processes are like, you can apply these 5 steps to help you manage the day-to-da...

Upcoming Live Webinars

Webinar: Stop Gathering Requirements

Webinar: Design Thinking for Business Analysts

Webinar: Understanding your Supply Chain Process

Webinar: The BA’s friend or foe? How to fit Requirements Engineering into Agility

Webinar: Agile Business Analysis

Community Blog - Latest Posts

Ekaterina Barabash

What is common between ‘agile’ methodologies and emotional intelligence (EQ)?

I address my thoughts to those who are in IT management for whom the terms such as quality of project implementation development and profitability indicators of the company are important. And it is also addressed to business analysts whose daily routine is the process of communication with Customer. A little about myself first. The last 8...

1 Responses

Dan Tasker

Requirements in Context Part 1 - Just Know It!

I have long been a believer in the saying “Context is everything.” As a business analyst dealing with business users, understanding the context of the topic of discussion is essential. In thinking about what constitutes quality requirements it occurred to me that there are a number of additional contexts that play a role. Examples inclu...

2 Responses

Alexey Kiselev

Acceptance Criteria. Bridge from your User Stories to Code and Test Cases

We are writing User Stories to fix the scope and describe - what our application should do when implemented.User Stories are great, because the are: Short, Defining Roles, A great connection of the requirement itself and a business need. User Story declared as a high level definition of the requirement, but it could be used to s...

0 Responses

MA Blog - Selected Posts

April 09 Editor’s Note: Should the BA care about BPM and SOA?
Yep! OK… this could have been a really short editor’s note but I’ll wait to practice word frugality for my Twitter po... Read More...

BA ABCs: “B” is for BPMN
#2 in the series: “B” is for BPMN This blog continues a series on BA tools, based on my book “The Business Analyst’s Handbook”. In each blog, I move ... Read More...

Agile Development: What we can learn from property developers – or what they’ve learned from us
Readers of this blog (both of you; I know you’re out there!) may have gathered by now that I’m a big fan of mixing it up: art/science/business/philoso... Read More...

Templates & Aides

Templates & Aides: find and share business analysis templates as well as other useful aides (cheat sheets, posters, reference guides) in our Templates & Aides repository. Here are some examples:
* Requirements Template
* Use Case Template
* BPMN Cheat Sheet