Stakeholders & requirements
Radim Göth
Introduction
• Always ask for requirements.
• Always ask why. (Five whys)
• Requirements are incomplete, sometimes incorrect and always
changing.
• Otherwise, software development would be to easy.
Stakeholders
• A stakeholder is either an individual, group or organization who is
impacted by the outcome of a project. They have an interest in the
success of the project, and can be within or outside the organization
that is sponsoring the project.
https://www.projectmanager.com/blog/what-is-a-stakeholder
• Example: Mobile banking
• Customers, bankers, marketing, sales…
• Exercise:
• Define stakeholders of is.muni.cz (5 min.)
Stakeholder analysis
• Brainstorm stakeholders.
• Divide them into four categories.
• Set a communication with each
group.
• Do not forget on your
stakeholders during the product
backlog prioritization.
• Keep the key stakeholders
satisfied.
Power
Interest
Keep satisfied
Monitor Keep informed
Manage closely
Stakeholders which are usually forgotten
• Government
• law, restrictions, standards,…
• Developers
• software architecture, automated test, ease of deployment,…
• Operators / customer support
• monitoring, troubleshooting, documentation,…
• Executive sponsors
• People that often not directly using it, but paying for it.
Requirements
• Functional
• Non-functional
• Maybe they are both just different form of qualities.