Stakeholders 1
Stakeholders 2
100
This happy stakeholder willingly imparts her much sought after knowledge, but on an ad hoc basis, in a completely unstructured, Stream of Consciousness manner, leaving it to the BA to sort out the requirements from the musings.
Who is the Molly Bloom
100
This stakeholder starts on the offensive by default, needs to assert his knowledge/ superiority at every occasion, generally ending in demonstrating the exact opposite to a wary and weary audience, takes on jobs then denies responsibly.
Who is the "Chip on the Shoulder"?
200
This stakeholder knows his stuff inside out, how to explain it, answers specific questions with specific answers, and makes decisions
What is an All Star?
200
• Wants the change straightaway but not prepared to put in the effort to identify requirements • Questions (and reads?) little of the requirements document • Requests several changes contrary to approved requirements once in UAT
Who is the Prima Donna?
300
• Business SME / end user / not technical at all • Limited experience to SDLC/IT projects • Expects quality deliverable • Buy-in is key to the success of the project • Does not understand importance of accuracy / level of detail needed. Focus is on BAU activities rather than project. Performs only cursory review of requirements artefacts.•
Who is Disengaged?
300
• Agrees decisions need to be made but not prepared to make them • Wants further meetings to discuss items that already have consensus • Identifies new/additional stakeholders that “need” to be consulted before decisions can be made
Who is the Procrastinator?
400
• This stakeholder knows his stuff inside out, how to explain it, answers specific questions with specific answers, and makes decisions Focuses on the long term business value. Understands the inevitability of change, doesn't sweat the small stuff
Who is the Visionary
400
Points out "mistakes" that have little or no material impact on the requirements • Doesn't provide constructive feedback on the actual requirements
Who is "The Pendant"?
500
• Agrees with everything you say until 5 minutes before release to production • Insists that a large variety of documents are required 5 minutes before release and should be included ‘as standard’ in order to bypass our argument that they are not included in the RFC/SRS/PID and have never been mentioned before • Watches closely for even the tiniest mistake and calls it out to everyone as a serious quality issue, but rarely acknowledges efforts that go above and beyond the call of duty
Who is The Backstabber
500
Gets the red pain out when correcting your Homework – Spelling and Grammar is more important that the content The office is like a classroom – “settle down kids and keep quiet” Nothing is right unless I have told you its right
Who is the Schoolteacher?
M
e
n
u