OK, from the previous episode we understood that there are a lot of stakeholders on your project. Now, there are two aspects that you need to find out about each of them. These are expectations and requirements.
Expectation it is something that a stakeholder wants to get from you, your project, or from its result. Expectations are not always aligned with the project objectives or requirements. It is even worse. Expectations may not be in line with realities of your work and the capacity of the project team. Moreover, they are not always obvious.
Here are some examples of expectations.
A stakeholder expects to get a promotion after successful delivery of the project.
A stakeholder expects to get exposure in front of top management by participating in the project.
A stakeholder wants to participate as little as possible in the project while all his requirements are met.
A requirement is a condition, capability or feature that helps to achieve the project objective.
For example, an application should support the latest version of the Android operating system. A website should have a capability to collect emails. A car should go from 0 to 100 kilometres in 6 seconds.
And here is the problem. As I said, requirements are not always aligned with expectations. While expectations might not be brought into a line with project objectives. Therefore, you need to ensure that all requirements requested by stakeholders are aligned with project goals.
Here is an example. A stakeholder wants to show off in front of top management. He intends to get a promotion. So he sets a requirement of a glorious design for a utility application to make a compelling presentation. Therefore, this requirement is aligned with his expectations, but not in line with the project objectives.
Know your stakeholders and their expectations.
And see you in the next episode.