The identification of stakeholders is a key step even in traditional project management. Following the agile manifesto, conversation with the individual and interaction will be prioritized over documentation in order to have a more efficient and closer collaboration.

But in this conversation, do all stakeholders have the same roles and does their opinion count so much when it comes to defining the EPICS and their priorities and splitting up into User Stories? For example, does the CFO’s opinion on EPICS of a bank reconciliation finance application have the same weight as that of an HR stakeholder?

In this case, the stakeholders register should provide key information about them:

  • Name, email, telephone.
  • Department
  • Title / Role / Role in the project.
  • Influence, in this aspect can help us a matrix of influence and interest to draw considerations: we need to meet their expectations, key player, less important, just show consideration.
  • Expectations: reflect if you have any key request, red line marked.
  • Notes: how to backup if you are not there, who can help convince you, problems setting meetings / best time of day.

An incorrect identification of stakeholders can make the definition of EPICS, priorities and then the breakdown into User Stories fail later, because no expectations of key players or leaders of the organization have been handled.