The Stakeholder All-Skate
Regardless of the methodology our teams use, we tend to focus our analysis efforts on the users of a system or process, and the functionality they need in order to accomplish those tasks. However, there are numerous other interested parties who will be impacted by the new system; eliciting and understanding their needs contribute to the overall success of the project. Stakeholders can contribute requirements, assumptions, or constraints.
BAs are in a great position to develop a broad, holistic understanding of the context in which the project will be developed and implemented. Understanding these “outlying” stakeholders’ perspectives and how they will be impacted enables BAs to add much more value to the project, increasing its chances of success. If the project was planned without considering these other stakeholders, the BA can communicate to the impact and risk analysis that oversight represents. Join me for ideas to identify these other stakeholders and their concerns!
This presentation is based on my article published in the IIBA’s Best Practices for Better Business Analysis, December 15, 2014.
Terry Wiegmann, IIBA Columbus Chapter
Terry was the founding president of the Columbus IIBA Chapter, and has served on various professional organization boards including Columbus ATDD, Columbus Requirements SIG, Central Ohio Agile Association and US Agile Coach Camp.