Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Gathering Requirements when nothing is changing in an upgrade
Previous Previous
 
Next Next
New Post 11/30/2018 5:48 AM
User is offline Fizzy 01
2 posts
No Ranking


Gathering Requirements when nothing is changing in an upgrade 

Hello Forum, 

I am a business analyst on a project that has to do with upgrading a software to a new version. The new version has capabilities to connect to the cloud, and mobile app. However, the customer said they have no plans to use any of these features and do not want it configured. They are simply migrating to a new version because the manufacturer told them they will stop supporting the older version. Aside from this, everything worked well in the older version and they will like to keep things the way it is.

I tried to elicit requirements from the stakeholders and asked probing questions but got nothing.  It appears there is no requirement to gather but I might be wrong, can you please tell me what to do as a business analyst in this case?

What requirements do I gather when nothing is intended to change?

Please advise

 
New Post 12/1/2018 1:17 AM
User is offline Mahendra B
1 posts
No Ranking


Re: Gathering Requirements when nothing is changing in an upgrade 

Hi,

I can relate to  your confusion. I had something similar with my earlier customer sometime last year. The customer was upgrading to latest version of Tibco JasperSoft only for the reason that the version in use at present would be no more supported. But once we upgraded to latest Tibco JasperSoft, the product stopped supporting the Java jdk version which was in use. And then, we also needed to upgrade Java jdk and the product worked well as expected.

So, in a nutshell, you may need to check the inter-dependency & impact between the new version and any other application the product may be already using. Generally, a software application is a complex mix of many application working together. So, inter-application support and dependency should be checked.

I agree that the above example is not exactly of business / functional requirements per se, but I believe that a BA must check & catch such holes, if possible.

Just my two cents. Thank you & good luck!

 
New Post 12/14/2018 7:13 AM
User is offline Fizzy 01
2 posts
No Ranking


Re: Gathering Requirements when nothing is changing in an upgrade 

Thanks fro your response Mahendra B

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Gathering Requirements when nothing is changing in an upgrade

Community Blog - Latest Posts

Dan Tasker
Dan Tasker
  In Part 1 of this series it was stated that the overall objective of these articles is to improve the quality of requirements produced by business analysts. Following the adage that “Context is Everything” it established that a number of different contexts...
4 Responses
Alice Bolingeryn
Alice Bolingeryn
Clearly, the most important step in getting a job is being selected for an interview, and a key part in that process is having a resume that stands out from others.   For many people, creating a good enough resume is an obstacle in achieving this, and so one way to address this problem may be to get a professional to create one for you. J...
0 Responses
Arash
Arash
It may sound routine, but the importance of operational decisions cannot be underestimated. After all, not a day goes by without even the smallest business making dozens, if not hundreds of operational decisions that may affect the bottom line. Elevate these to large scale companies and we are talking thousands, if not millions of actions that impa...
0 Responses




Latest Articles

Three Modes of Business Analysis Consulting
Jun 16, 2019
0 Comments
A business analysis consultant might perform three types of roles when working with clients: expert, pair-of-hands, and collaborator. Each of these re...
Copyright 2006-2019 by Modern Analyst Media LLC