Zero Touch Installation Deployment Feature Team Guide
Using This Guide
This guide is intended to be used as a part of Microsoft® Solution Accelerator for Business Desktop Deployment (BDD) and is designed to guide a specialist team through Solution Accelerator for BDD deployment tasks and checkpoints. The goal is to ensure that the deployment is managed as a specific initiative of the specialist team within the scope of a larger deployment project. This approach is used to make certain that the decisions taken within this initiative align with the overall project goals and that the deliverables are well integrated into the total migration project. Setting Up the TeamThe specialist team responsible for ensuring the success of this initiative is the Deployment feature team. A feature team is a cross-organizational team responsible for solving a defined problem. Within the Solution Accelerator for BDD project, the Deployment feature team is one of several feature teams that work with a lead team. Feature teams are an important component of the Microsoft Solutions Framework (MSF) Team Model. The ability to split a large and complex project into smaller sets of related tasks allows work to be performed on many tasks in parallel, with the application of specialized expertise where needed. A great advantage of this approach is an enhanced ability to manage large projects with many simultaneous tasks. For the approach to work, however, it is vitally important that the teams synchronize their efforts and maintain active communications among the feature teams and with the project management team. Such communication is particularly important in complex projects, where a feature team may focus on its portion of the project to the unintentional and undesirable exclusion of the role that team members play in the overall project. CommunicationKey to successful project implementation is each feature team member’s ability to cooperate and communicate internally, on the one hand, and with other feature or function teams within the project and project stakeholders on the other. Within the team, each role has equal importance, even though the roles may vary. Important team decisions are characterized by joint decision-making. Across teams and from individual feature teams to the project management team (defined as the lead team in this document), the process is more formal, with well-defined pathways of communication. This formality does not prevent informal communication between the teams, which is encouraged, but does ensure that significant communications are well documented, occur at the appropriate level, and are directed to the appropriate team members. An important consideration for feature teams is communicating with the project stakeholders, which typically include various entities within the customer organization. To avoid confusion, incomplete or conflicting messages, or misunderstood expectations, the lead team must act as the official project voice to the stakeholders. In this way, management is always aware of the state of the customer relationship, and customer satisfaction during the deployment process is enhanced. Additional Guidance on Team ModelsFor additional guidance on team models, see MSF Team Model in the Additional Resources section of this guide.
|
In This Article
|
