Wondering if you even NEED a Business Analyst?

You do. Here is why.

Adding a missed requirement or feature in the business analysis stage will cost you one person's time.

Adding a missed requirement or feature during the development stage will cost you the development team's time, a project manager's time, and "retrofitting" costs.

Adding a missed requirement or feature during the testing phase will cost you the development team's time, a project manager's time, the test team's time, and the time of some users.

Adding a missed requirement or feature in the field will cost you the development team's time, a project manager's time, the test team's time, the marketing team's time, the sales team's time, and the time of some (now very annoyed) customers. Statistics show that making changes and additions this late is 18-22 times more expensive than figuring out the issue early with the help of a good BA.

That's why you need a BA. But what makes a BA a standout in the herd? The next series of posts will focus on specific qualities you should look for.