Skip to main content

Can projects do without Business Analysts?

My  last 2 gigs were a bit different to the usual ones from a team composition point of view. The bit that was different was that there weren't any Business Analysts on the team. My initial concerns were who would gather requirements? Who would analyse stories? Who would negotiate scope with the business? Who would be involved in Scope Management? Who would be our proxy customer?

The above questions got me concerned, but it wasn't as bad as i thought it to be. The customer was co-located with the team and we had easy access to validate our understanding on business rules, scope, sign-offs etc.

Our team composed of an IM, Devs and Testers. The IM was managing scope with the customer and getting the priorities. The team would then sit with the business to understand what the requirements were and we would create Epics and then further break them down into smaller chunks of workable stories. A thing to note here is that all roles would put their BA hat on and identify gaps if any while breaking down the stories. The business was open about design and the way the functionality would work and not crib about things, like specific error messages, or look and feel. A lot of that was left to the team to decide on what would work best for the product.

We would have shoulder checks with the testers and then at times also validate with the business if what we were building did meet their expectations or not. What could have been done better was to involve the business more often during shoulder checks in-order to further reduce the feedback loop.

In this case, the team themselves were proxy customers for themselves and would in a way validate on behalf of the business if what was being built was fit for purpose or not. As mentioned earlier, regular feedback from business helped keep us in check.

But, would this model work for all projects? Perhaps not. Gigs which require hardcore analysis require specialist BAs who focus on analysing the requirements. Building an Insurance portal which has so many business rules would require some detailed analysis which would require a dedicated role to just focus on ensuring the analysis is spot on. I totally believe in the value a Business Analyst would bring to the project. But it would be interesting to work on a project where the domain is complex, but there is no BA on the project.

Comments

Popular posts from this blog

How does one decide what to automate?

A question that has been troubling me for years is how much to automate. We all like to achieve maximum coverage and build a robust safety net where possible in order to give us confidence about the system under test. Given there is ample time i would like to automate almost everything, but in the real world, this isn't possible. This is when we introduced the concept of Value and Cost for a test scenario. Every test scenario would be assigned either of these attributes. Lets call the attribute automation classification High Value - Low Cost High Value - High Cost Low Value - Low Cost Low Value - High Cost What this translates into is we are associating business value and cost to automate to every scenario. So, when a test scenario is of high business value and the cost to automate it is low, then this becomes our ideal automation candidate. You would like to start automating all test scenarios that fit into the High Value - Low Cost category first. See picture below If tim...

Motivation of tester types

In my testing career span of close to 7 years, i have come across various testers. Every tester has unique skill sets and things that motivate them. Based on the various tasks a tester has to do on a daily basis or during a project, I would like to categorise these testers into 3 types Manual tester Automated tester Hybrid tester Manual testers are mainly non-technical and are focussed more on testing applications manually. These types of testers have good domain knowledge. Automated testers are technical testers who mainly deal with tools to help them test applications. They are given a set of test scenarios and all they need to do is automate these scenarios. Hybrid testers are like superman. They are expected to do whatever is thrown at them and it is these types of testers that are in demand these days. Now the interesting aspect is what motivates these testers in their day jobs. Lets take a look at this in the form of a graph where x-axis represents the various activit...

BDD is over-rated

Over the past few years, I have tried to justify the use of a BDD (Behavioral Driven Development)  framework to express my tests, but not once have been able to say BDD has helped me address a  problem which writing tests the non BDD way would not have addressed. I do understand the value BDD brings to the table, but in most projects that I have implemented BDD on, we have tried to provide a solution (BDD) to a problem that does not exist. Let me try and explain. Lets look at the key benefits of expressing tests the BDD way (There could be more) Collaboration between Business and Development Ubiquitous Domain Language Focus on the behavior of the application Now, more often than not unless your business is co-located with the team, collaboration is not the easiest. The value BDD brings here, is the business validating our understanding by reading our tests expressed in the Given When Then format (BDD) and providing feedback, as BDD expresses the behavior of the syst...