At the start of the project, the team did not address the risk associated with the assumption that a satisfactory software implementation based on a modification of the UDP protocol was feasible. The team did not discuss this risk with the client and thereby missed the opportunity to set the client's expectation for how the project should proceed if the planned solution was found not to be feasible.

Initially, the team thought that it would have flexibility in determining the solution, and the client expressed a similar expectation. But the client's expectations changed as the project progressed because the client did not see evidence of a software implementation as quickly as he expected. The team became aware of the client's expectations …show more content…
The client's perception of the team's accomplishments may not match reality. As managing stakeholder expectations involves setting, monitoring, and influencing stakeholder expectations. Stakeholders are not likely to be satisfied if their perceptions are less than their expectations.

To resolve the problems, the team will need to explain the facts in an objective and unemotional way to the client and to provide options that would require the client to make transparent exactly what he originally wanted to accomplish with the project and what he would like to do now. The state of the ongoing communications will likely help make or break this project.

The team might recommend that it help Julian define and prioritize communication scenarios that would clarify the performance and reliability requirements. The team would use these scenarios to determine whether their current implementation satisfies these more specific requirements and possibly to compare their implementation to the implementation that Julian created. The objective would be to determine whether the current implementation will be acceptable, possibly with some