Determining the Scope of the Deployment

Lync Server 2013 contains such a wealth of features that planning a deployment, even a limited one, can seem quite daunting at first. This section provides some guidance to assist with the process and assist administrators in creating a well-thought-out and well-structured implementation plan.

Rather than forging ahead with no plan or goals and simply building new servers, loading application software, and inserting them into an existing network environment, you should implement a more organized process to control the risks involved and define in detail what the end state will look like.

The first steps involve getting a better sense of the scope of the project—in essence, writing the executive summary of the design document. The scope should define from a high level what the project consists of and why the organization is devoting time, energy, and resources to its completion.

Creating this scope of work requires an understanding of the different goals of the organization, as well as the pieces of the puzzle that need to fit together to meet the company’s stated goals for the project. For Lync Server 2013, this means understanding how the various parts of the business will use the new functionality to improve collaboration and real-time communication. Different groups will focus on different aspects, such as IM with federated partners, or on leveraging video conferencing for departmental meetings. Understanding the needs of the various groups is key to a successful deployment.