Forums for the Business Analyst

  Modern Analyst Forums  Careers  Ask a Recruiter...  Inreview questions
Previous Previous
Next Next
New Post 1/2/2012 11:00 AM
User is offline Rustam
3 posts
No Ranking

Inreview questions 
Modified By Rustam  on 1/8/2012 12:18:58 PM)

Hello everyone!

What do you think about the answer I gave to question below?

What are your actions when you realize upon product build review that it implements some functionality not described in your requirements documents?
When I see some features which are not signed in documents I'll report about it to a project manager to decide hide these functionality till next build when I'll include it in requirements or to show this as some benefit for the customer.
I believe that conclusion will based on what kind of implementation it is: one time delivery of the product or regular improvement of the system.


New Post 1/9/2012 11:16 PM
User is offline Adrian M.
764 posts
3rd Level Poster

Re: Inreview questions 

Hi Rustam,

Another thing that you should do is determine why there is a discrepancy between the specification (requirements document) and the actual product as there could be many reasons:

  • Did the developer team add things which should not be there (bug)?
  • Are there features which are supposed to be there but are not in the spec (requirements document gap)?
  • Are these features which are in a specification/requirements document for a future release (release management issue)?

Identifying the root cause of the discrepancy is important as it is the right way to begin to solve the problem and to fix the root cause, ensuring this doesn't happen again in the future.

Hope this helps!


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
New Post 1/12/2012 8:53 AM
User is offline Rustam
3 posts
No Ranking

Re: Inreview questions 
Modified By Rustam  on 1/12/2012 11:56:08 AM)

Hi, Adrian, and thanks for your reply.

In my answer I presumed that it's only extra functionalities which of course not always right.  It can be essential in product or a bug. And my view on the case was one-way.

Thank you for your very helpful advice.



New Post 1/12/2012 9:54 AM
User is offline Rustam
3 posts
No Ranking

Re: Inreview questions 

We clarified more or less with the previous question.
I have another question and the answer to which I would like to see tips and comments

Some customer refuses to sign off requirements. What are you going to undertake?
In this situation I will contact with the customer and find out any obstacles. There are two possibilities: something wrong with requirements or person who has to sign it off.
If it is a right person and he or she has authority, proper involved in to the project, decisive and willing to let go the discovery stage of a project, I will explain unclear points in the document. I make the review requirements protocol in which
divide requirements on two parts: first can be approved by the customer and second on that client disagree. Maybe there will appear requirements which are not put in document but should be there which I put in the third part of the protocol.
If I have time, employ some discovery methods that foster an exhaustive approach. Brainstorming, requirements workshops, and other discovery methods that encourage lots of ideas and group creativity may help stakeholders, who generated requirements in the second part, to feel they are not overlooking anything important, they meet all goals of the project and signer agree with them. Improve the document on requirements which were changed in these activities and put new if necessary.
If I don't have time I show the review requirements protocol to my project manager to decide what should we do.
If it is a wrong person I have to find a right one.
Previous Previous
Next Next
  Modern Analyst Forums  Careers  Ask a Recruiter...  Inreview questions

Community Blog - Latest Posts

The software development industry requires productivity and performance to create a successful product and meet business objectives. That's why everyone in the software industry always looks for new ways to streamline their processes and create better software. Today's world is experiencing an increasing pervasiveness of artificial intellig...
In the dynamic landscape of business analysis, staying ahead of the curve is imperative for success. The role of a business analyst is pivotal in driving organizational growth and efficiency. To excel in this domain, one must harness the power of cutting-edge tools and adopt strategic approaches that streamline operations and enhance decision-makin...
Angular is a powerful open-source web application framework developed and maintained by Google. It is designed to simplify and streamline the process of building dynamic and interactive web applications.  Angular was first introduced in 2010 as "AngularJS" by Misko Hevery and Adam Abrons during their work on a project called "...



Copyright 2006-2023 by Modern Analyst Media LLC