Stakeholder Analysis is the process of identifying project stakeholders, how their needs may impact the project, and the contributions that the stakeholders will make to the requirements elicitation process.  Projects typically have a large number of stakeholders from many different areas of the organization.  Based on each stakeholder’s position and responsibilities, the level of their involvement and their importance to the project will vary.

Stakeholder Analysis is sometimes called a Stakeholder Involvement Plan or a Stakeholder Elicitation Plan.  Regardless of the name used, Stakeholder Analysis goes beyond identifying project stakeholders.  After all project stakeholders have been identified, it should be determined how involved each stakeholder should be in the requirements elicitation process.  The business analyst should document a number of factors for each stakeholder including:

• Importance – How important is the stakeholder in the requirements elicitation process?  Are they required in order to document all of the critical project requirements, or are they nice to have adding clarity to processes that may further refine requirements?  Answering these questions will help ensure that the project will meet its goals and objectives, and that critical requirements aren’t missed.
• Influence – How influential is the stakeholder to the project?  Even if they aren’t needed for the requirements elicitation, are they in a position of authority?  Does the stakeholder have the ability to dramatically alter the course of the project if they hear about and are unhappy with the current direction of the project?  Answers to these questions will ensure that the most influential stakeholders are updated on a regular basis with the project status.
• Level of Involvement – What level of involvement and how much time will be expected of each stakeholder?  Do they need to be fully allocated to the project?  Do they need to be in every requirements elicitation session?  Can they be involved in only key requirements elicitation sessions? Do they only need to attend a final requirements review session?  These questions help ensure that the necessary people are made available to the project for the right amount of time.
  
• Frequency of Involvement – How often will each stakeholder need to be involved; daily, every other day, once per week?  This information will help the business analyst plan and schedule the necessary meetings accordingly.
• Method of Involvement – What method will be used to involve each stakeholder?  Will they receive email-based status reports? Will they be involved in requirements gathering sessions?  Will they be asked to sit in one-on-one requirements interviews?  This information will aid in development of a communication plan and the appropriate selection of communication techniques.