21 Stakeholders

Managers, developers, testers, users
Nobody LIKES to hear about problems with their (beloved) software.
Stakeholder: direct interest in the project
customer wants to pay less
upper managers and owners want more money
project managers care about good, fast, and cheap
developers might want it easy to write, well written, or done 'their' way
quality assurance cares about...you guessed
assesors care about legal issues
support personnel care about uptime, ease, quality
(There are probably more)

Some stakeholders are more equal than others.
An owner, as someone who holds the entire future of the project in their hands, is a STAKEHOLDER.

Report and communicate:
different groups have different interests, priorities, even vocabularies.
Explain things as consequences of things they care about
Remember the further away from your job they are, the less they need the details of your job.
Also, the less they may realize the significance of something that is obvious to you.

College administrators see that the budget must be cut.
Professors realize that cutting faculty is cutting why the University exists (and attracts students).
A single professor knows how to teach a specific course
A student focusses on getting their homework done

RedYellowGreen (for subsystems)
green-on time, within budget
yellow-some issues, relatively minor
red-major problem, needs attention!

Status reports:for a tester
what working on, what ready, what needed

Be careful about managing expectations.
Better to complete sooner than you said, than later than you said.
DO NOT WAIT TO REPORT PROBLEMS

Not everyone needs to attend every meeting
Meetings can be great for common understanding and developing consensus.

Resolve ambiguity: usually, talk to stakeholders(You do not MAKE the requirements)

There are ethical obligations and professional standards
report problems, even if told to ignore?
Whistleblower?
 
treat people with respect