Corporate Education Group

How to Get Stakeholders to Read Your Requirements Specifications

CEG offers Corporate Training and Consulting, as well as traditional and virtual instructor-led courses in management and leadership, project management, business analysis, business process management, agile/scrum, and lean six sigma.

Issue link: https://info.corpedgroup.com/i/1209591

Contents of this Issue

Navigation

Page 0 of 3

300 Brickstone Square • Suite 201 • Andover, MA 01810 USA • 1.800.288.7246 • +1.978.649.8200 • info@corpedgroup.com Y OU'VE HELD THE INTERVIEWS, read the documentation, done your analysis, asked a ton of questions, and even received some answers. As the requirements delivery deadline looms, you need to get your project stakeholders to read and approve your requirements specifications. Now your real problems start. Your project stakeholders are too busy. Or worse, they don't answer your requests. Or maybe they prefer to have a meeting. And there's never enough time at the meeting. And the requirements keep changing. Why is it so difficult to get people to read a requirements specification document? You would think that something so important would have the full attention of your key stakeholders. Yet time after time, in company after company and industry after industry, business analysts complain that getting their stakeholders to read and approve their requirements specifications is unexpectedly difficult. Requirements from the Stakeholder's Perspective Why is this happening, and what can you, as a business analyst, do about it? Let's look at it from the project stakeholders' point of view. They told you the requirements, and you wrote them down. Then How to Get Stakeholders to Read Your Requirements Specifications B U S I N E S S A N A LY S I S

Articles in this issue

Links on this page

view archives of Corporate Education Group - How to Get Stakeholders to Read Your Requirements Specifications