DownloadProduct Fact Sheet

Subscribe via E-mail

Your email:

About our Blog

The Enfocus Solutions Blog is focused on helping organizations improve their requirements development and managemeent practices. We focus on four key areas:
  • Delivering Business Value through Better Requirements
  • Best Practices for Requirements Management
  • Requirements for Business Process Improvement
  • Requirements Development for Emerging Technologies

 Our blog authors are:

Click on the names above to see articles by blog author or click on the link below to learn more about our blog authors.

Add to Google Reader or Homepage

Requirement Videos

See our new video channel on YouTube.  Learn about requriements engineering from industry expert, Karl Wiegers.

Posts by Month

Requirements 101

Requirements Management & Business Process Improvement Blog

Current Articles | RSS Feed RSS Feed

Your Two Greatest Requirements Gathering Skills

  
  
  
  
  
  
Whether you are a Project Manager, Business Analyst, Technical Writer, Business Process Analyst, or Requirements Analyst, there are real skills required to manage the relationship with the stakeholders involved in software development projects. There is more to including stakeholders than gathering information for processes and requirements. I think the most important of these are:

Relationship Building

  • Your ability to convince others to work together towards a common goal (agreeing on requirements or processes) is invaluable.
  • You act as both a guide and specialist on the subject of requirements gathering, you engage others in the process without taking over.
  • You convince others to work with you as a team, continuing to deliver and receive current, actionable feedback to support continuous growth of the project, while ensuring that the project requirements remain in-scope. (Review out-of-scope needs later).
  • You are not only a problem solver but also have the ability to influence others to share in the problem solving and therefore take an active stake in the outcome.

Communication

  • You actively listen to the stakeholders to understand their perspective and ensure continuous and complete understanding regardless of communication method or audience.
  • You realize that the stakeholder’s terminology is different from what an IT department uses so a first step may be to make sure you understand the vocabulary the stakeholder is using. (You realize it is your job to understand them, not the other way around.)
  • You know to translate for the developers and then translate for the stakeholders the information from the developers, so that the information can flow both ways. (Many times this is where the process flows will really come in handy)
These are only two of an even greater set of skills required to maintain a relationship with the stakeholders throughout the project to make the best use of the stakeholders and the requirements so that the project as a whole is a success. However, you already knew that because even though you may have not had it pointed out to you before, but part of what makes you good at this type of work is that you have these skills naturally.

 4W5T7NYUBPKC

Comments

Very informative, interesting, and looking forward to the next blog!
Posted @ Thursday, December 01, 2011 11:49 PM by Lois
An interesting idea. Now if the software will accomplish the stated goals I think you have a winner. Not only communications but understanding between the supplier and the supplied is essential to efficient / profitable business.
Posted @ Saturday, December 03, 2011 1:19 PM by Baron
Comments have been closed for this article.