Vendor’s role in involving customer top management while requirement gathering phase - Quality Assurance and Project Management

Quality Assurance and Project Management

May 18 2009   10:00AM GMT

Vendor’s role in involving customer top management while requirement gathering phase



Posted by: Jaideep
Software vendor, Project Management, Software Project, Software Project Lifecycle, business study, requirement gathering, customer, customer expectations, software product, top management, project stakeholders, process owner, end user, software development, project completion, user level requirement, top level requirement

The most critical stage in software project lifecycle is business study and requirement gathering. Vendor has to be very cautious and careful in understanding all levels expectations from the product they are going to build for the customer. Skipping top level at this stage could be disastrous for both. As a vendor, if you don’t involve customer top management while gathering requirements – you are inviting a mishap!

Customer top Management involvement is very critical during the business study and requirement gathering phase of a software project. The expectations of top management shall invariably be different as compared to other stakeholders of the software project at customer end. Assuming that the requirements gathering from process owners or end users will be sufficient for developing software will be a misconception. A detailed discussion for capturing requirement and understanding top management perception is critically important to lead to a successful completion of the project.

At the Vendor end – the Project Manager has to ensure that besides capturing user level requirements, it is essential to highlight the benefits to the top management being proposed for them from the product. It is not desirable but mandatory to freeze top level expectations at business study and requirement gathering stage.

Comment on this Post


You must be logged-in to post a comment. Log-in/Register

Mayes9  |   May 19 2009   5:41AM GMT

In some cases that is a good, strategic role for them to take. The project is started with no … Requirements gathering is nothing but understanding the customer “NEED”. … To evaluate the vendors, he gives some minimal information

mayes


 

Mayes9  |   May 19 2009   5:42AM GMT

Requirements Management Best Practices. Tactics for success; Role of the … Discovery Phase- Business Analysis & High-level Design … Building a requirements matrix; Vendor selection package rating

mayes
<a href="http://careerdevelopmentuk.com" rel="nofollow">careers</a>


 

Jaideep  |   May 19 2009   7:18AM GMT

for 1st comment:
Hello Mayes, I think it is critical in all cases. In my opinion a project need to start only once the requirements have been gathered in detail by understanding customer, their business, their processes, their user’s requirements, and on top of that the top management requirements without which the development will be incomplete and bring in confusion at a later stage.
~jaideep