Quality Assurance and Project Management

Jul 26 2011   6:07PM GMT

Sixteen Blogs On Identificaiton Of Customer Requirements

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Customer Requirements need to be wisely analyzed before committing its fulfilment to customer. Many a times a commitment which has not been properly analyzed and assessed impacts to a large extent on completion of project.

It may also happen that a requirement stated by customer at a later stage may appear to be quite genuine for business purposes and logically need to be covered in product development. Project Team need to properly analyze and though accept the requirement but need to clearly tell the customer management its impact and risk if any.

The requirement raised by customer may already be catered to in the product built for the purpose but not exactly in the manner defined or expected by customer. If the impact analysis draws out a bigger risk of changes to be done at that stage of product to cater to customer requirements as it is, customer management need to be convinced about the functionality and features already present in the product.

Sometimes architectural issues may disallow to cater to customer requirements.

It is wise to build a functionality altogether different as a complete sub-product, if requirements need call for that; instead of fiddeling with the main product.

It is unwise to accept all requirements of customer and keep making changes in the product thereby changing its stable stage to unstable one.

It is better therefore to adhere to and adopt some best practices to manage Change Requirements.

Many a times it has been seen that a change in key users or one of the key management person tend to call for changes in the stable running product in the organization, which may turn out to be quite harmful.

Project Manager and Project Management Office need to convince top management of customer in case of some unnecessary requirements raised by one of the influentinal person in the organization who might have joined organization recently so as to impose his/her importance.

Changes once accepted, not only impact on product’s stability or the software environment but also many times has serious effect on performance of the product and its hardware requriements may change.

In fact requirements raised by customer must be mapped properly with their existing business model and its impact on software application running in the organization for that purpose.

An ecosystem to manage change requirements and a standard metrics system thus becomes prime important to manage the show.

A well defined system in place not only helps in streamlining the process but also helps in benchmarking with other systems being followed in other organizations.

Involvement or engagement of customer in formulation of systems is always beneficial for both parties.

These processes once defined must be adhered to and also need to be examined from time to time for the purpose of optimization.

Defining of processes is not difficult if compared to the later part which is adherence of those processes.

 Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: