Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Requirements Feasibility
Previous Previous
 
Next Next
New Post 8/20/2008 11:56 AM
User is offline Jim
15 posts
9th Level Poster


Requirements Feasibility 

Hello,

What is the Business Analyst's role in determining the feasibility of requirements elicited from business users?  I'm mostly interested in technical and operational feasibility. 

With respect to technical feasibility...When should we as BA's make the determination that a requirement is not technically feasible?  How should we go about backing up our determination? 

I was a deveIoper in my previous life and I am currently gathering requirements for a project where some of the business requirements seem like they will be extremely difficult to implement.  And even if they are technically feasible, they will make the system very complicated for the business user to operate and will introduce inefficiency into the process.  How can I go about determining the technical feasibility and how should I communicate the results to the business?

Thanks - Jim

 
New Post 8/20/2008 9:10 PM
User is offline David Wright
141 posts
www.iag.biz
7th Level Poster




Re: Requirements Feasibility 

As a BA and no longer a developer, you will have to start letting technical feasibility be determined by the people on the project who are the designers/developers. Its hard to let go of some things but, unless you keep yourself current as a developer as well as a BA (which doesn't sound easy), your technical knowledeg will get old fairly quickly and could actually be a detriment to your project if you don't get technical people to do this.

So, in general, a BA should not be expeccted to determine technical feasibility. My own pre-BA technical skills were in PL/1 and IMS, so I can't say that would be much help these days!

 jimbo1580 wrote

Hello,

What is the Business Analyst's role in determining the feasibility of requirements elicited from business users?  I'm mostly interested in technical and operational feasibility. 

With respect to technical feasibility...When should we as BA's make the determination that a requirement is not technically feasible?  How should we go about backing up our determination? 

I was a deveIoper in my previous life and I am currently gathering requirements for a project where some of the business requirements seem like they will be extremely difficult to implement.  And even if they are technically feasible, they will make the system very complicated for the business user to operate and will introduce inefficiency into the process.  How can I go about determining the technical feasibility and how should I communicate the results to the business?

Thanks - Jim


David Wright
 
New Post 8/21/2008 4:52 AM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: Requirements Feasibility 

[QUOTE]dwwright99 wrote

As a BA and no longer a developer, you will have to start letting technical feasibility be determined by the people on the project who are the designers/developers. Its hard to let go of some things but, unless you keep yourself current as a developer as well as a BA (which doesn't sound easy), your technical knowledeg will get old fairly quickly and could actually be a detriment to your project if you don't get technical people to do this.

So, in general, a BA should not be expeccted to determine technical feasibility. My own pre-BA technical skills were in PL/1 and IMS, so I can't say that would be much help these days!

[/quote]

 

David I disagree.

If you know something is not feasible you have a duty to the client to cut off that area of inquiry as soon as possible.  Otherwise you are consiously wasting time and money.

The caution is that your developer skills will fall out of date and you'll need to consult with current experts to validate your hunches.

Feasibility checks are well withing thye scope of the BA role - see the BABOK's process areas.  The chapter on enterprise analysis specifically covers this ground.

Additionally the enterprise architecture role (which has significant overlap with the BA profession) also looks at identifying contraints and guides to shortcut the efforts required for the feasibility question.

This goes to a value set Kevin Brenan of the IIBA asks - do BAs take a neutral stance to solution design or do they get involved as early as possible?

The answer is about the context - the individuals and the circumstances.  And it also involves layers.  Solutions come in iterations and requirements respond  well to incremental design of solutions.  It's a conversation.

 

Craig
www.betterprojects.net

 
New Post 8/21/2008 5:46 AM
User is offline Jim
15 posts
9th Level Poster


Re: Requirements Feasibility 

Thanks for your feedback guys.  I understand David's point because, while I do plan on keeping up on technology trends, I definitely don't see myself spending too much time on the details.

I also agree with Craig in that you have a responsibility to communicate opinions and validate them for the benefit of the project. 

So how do you suggest I approach requriements that I feel have a technical feasibility issue?  For example, on a recent project, the users explained a requirement that involved importing data from a client and updating our systems.  I asked about the format that the data was being sent to us in and how the update was to occur.  They said that the data could be in a variety of formats, with no defined layout (i.e. specific fields, data type, order) and there was not a consistent field in the data on which the file would be matched to our data in order to do the update.  They current do the updates by trial and error.  They look at the data, and mess with it until it works.  I feel that this is a feasibility issue.  I tried to sugest improving their process by standardizing communications with clients, but they do not accept the suggestions. 

How should I approach this?  I don't want to just say it can't be done because I am not the technical expert.  We have an internal IT team, but we are not sure if they are going to do the development or if we are going to outsource.  How should I validate my hunch and communicate back to the business?

Thanks!

 
New Post 8/21/2008 4:45 PM
User is offline David Wright
141 posts
www.iag.biz
7th Level Poster




Re: Requirements Feasibility 

Hmmm... if you absolutely know something is not feasible, sure, don't keep it to yourself. The question is, on what basis do you 'know'? As you say, "The caution is that your developer skills will fall out of date and you'll need to consult with current experts to validate your hunches.". That is pretty much all I was saying...but I will look at the BABOK again soon.

As for the BA and solution design, it is about the project. As the usual stats say, most projects are maintenance/enhancement of existing systems, so the design is in place. Of the rest of the projects to deliver new systems,  a lot of those end up buying packages, so no design there. Its been a few years since I did complete requirements for a new system to be developed, and it was not a big system. So, perhaps that colors my opinion on this topic, but I will stick with "what, not how" as my guide as a BA until the opportunity for new development appears.

Whenever I do get to do that, I do hope there is Business Architecture (everything in Zachman Row 2, I think) in place, so that you know you can deliver in iterations and the resulting pieces will fit together. I wax and wane on overall Enterprise Architecture. I think I like the concept, but don't have an opportunity to apply it. That's probably a bad thing in the long run, but I don't know if the answer is to try to apply EA more, or try to make EA more 'appliable"...probably somewhere in between.

 craigwbrown wrote

David I disagree.

If you know something is not feasible you have a duty to the client to cut off that area of inquiry as soon as possible.  Otherwise you are consiously wasting time and money.

The caution is that your developer skills will fall out of date and you'll need to consult with current experts to validate your hunches.

Feasibility checks are well withing thye scope of the BA role - see the BABOK's process areas.  The chapter on enterprise analysis specifically covers this ground.

Additionally the enterprise architecture role (which has significant overlap with the BA profession) also looks at identifying contraints and guides to shortcut the efforts required for the feasibility question.

This goes to a value set Kevin Brenan of the IIBA asks - do BAs take a neutral stance to solution design or do they get involved as early as possible?

The answer is about the context - the individuals and the circumstances.  And it also involves layers.  Solutions come in iterations and requirements respond  well to incremental design of solutions.  It's a conversation.

 

Craig
www.betterprojects.net


David Wright
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Requirements Feasibility

Community Blog - Latest Posts

Fabricio Laguna talks Business Analysis and AI
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...
Business Architecture, Ontology and More with Terry Roach
It's been a privilege meeting Terry Roach, a visionary in the field of enterprise architecture and business architecture. Terry's insights into the evolution of business models, the importance of ontology in architecture, and the potential of AI to shape our future were not only thought-provoking but also a reflection of his extensive exper...
Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC