Modern software development approaches like Agile support a strong collaboration between all member of the software development team, software testers and business analysts included. Even if you don’t use a method like Behavior-Driven Development or Specification by Example, checking the fact that you will be able to actually test your requirements is a good thing. In his article, Richard Ellison share some best practices to reviewing requirements for testability from the point of view of a software tester.

A lot has been said and written about user stories and their role in an agile context. But what are people actually writing as user stories? It doesn’t matter if you are agile or traditional in your approach, poorly written requirements are one of the major causes of project failure. This is where the Business Analyst comes to the fore.

This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.

How do you know what to build of your customer wants a “secure solution with a good amount of flexibility and user friendliness”? You don’t! Force the customer to be more specific!

In this blog post, James Christie starts from the fact that perfect requirements don’t exist to discuss the idea that the quality of requirements is directly influenced by the time and money you invest in crafting them.

Wondering how to step up your business analyst career, and take on responsibilities of your appointed tasks with professionalism, enthusiasm and efficiency? Learn what makes a good business analyst, a GREAT business analyst, with pointers and guidance from an industry professional.

In this article, Trent Wong discusses how well the Business Analyst’s role is defined in organization. He starts by saying that the Business Analyst is a key success factor for software development projects. You need him to getting the requirements list properly, effectively communicating them to management and translating the requirements so the developers can build the application.

We can all agree that the Business Analyst collaborates with business stakeholders throughout the organization to ensure high quality, on-time deliverables and seamless communication. A key element of a Business Analyst’s proficiency is being aware of the array of techniques, tools, and deliverables that are available and selecting the ones that are appropriate to a particular problem.

There is no business analyst role in the Scrum Agile project management framework. Based on this fact and some perceptions about Agile, Roland Hesz tries to answer the questions “Do we need a business analyst on an agile project? Are there Agile business analysts?”.

Business is coming under increasing pressure to adopt agile practices to reduce costs and deliver more quickly. Agile Analysis describes your requirements and associated features using stories. Typically for use with agile development but it supports structured methods too giving a common analysis method throughout the organization.