Answer.

Proper management of stakeholder expectations increases the likelihood of project success and minimizes conflicts. Key practices:

• Clear, timely, and regular communication: organizing meetings, demos, and clearly documenting agreements.
• Documentation of requirements and assumptions: using signed specifications, backlogs, acceptance criteria, and change logs.
• Visualization of solutions: prototypes, mockups, process diagrams, to help the client understand what the outcome will be.
• Change management: transparent regulation of any additions and amendments to requirements through change requests, analyzing the impact on timelines and budgets.

Key features:

• Demonstrating intermediate results strengthens trust.
• Flexible response to changes while maintaining strict process documentation.
• Continuous learning and informing stakeholders (clarifying limitations, opportunities, compromises).

Trick Questions.

Should a business analyst always agree with client requirements and include them in the project?

No, often requirements may contradict business goals, budgets, or team capabilities. The analyst should justify their decisions and explain the consequences.

Is an approved requirements document final and unchangeable?

No, the lifecycle of requirements entails changes. It is important to clearly document the process of their incorporation and agreement with the client.

Is verbal communication sufficient for managing expectations?

No, verbal agreements can be forgotten. Documentation in files, emails, reports is a necessary condition for managing expectations.

Typical Mistakes and Anti-Patterns

• Ignoring feedback from the client until release.
• Lack of a transparent change management process.
• Overpromising.
• Failing to consider technical/business constraints.

Real-life Example

Negative Case: The analyst did not show the client intermediate results and did not document change requests. As a result, the final product did not meet expectations.

• Pros: minimal time spent on demonstrations.
• Cons: frequent changes at a late stage, conflict, and loss of the client.

Positive Case: The analyst organizes regular demos, shows prototypes, documents and approves all changes. The final product meets the client’s expectations.

• Pros: satisfied client, predictable outcome.
• Cons: higher time costs for communication and documentation preparation.