Zero Touch Provisioning Deployment Feature Team Guide
Using This Guide
This guide is intended to be used as a part of the Microsoft® Solution Accelerator for Business Desktop Deployment (BDD). The focus of this document is on guiding a specialist team through the installation and configuration of Zero Touch Provisioning (ZTP). Deploying ZTP is part of the larger desktop deployment project and must be managed as such. This means that decisions made during the installation of ZTP must align with the overall project goals and that the deliverables must be well integrated into the total desktop deployment project. On This Page
Setting Up the TeamThe specialist team responsible for ensuring the success of ZTP installation is the Zero Touch Provisioning feature team. A feature team is a cross-organizational team responsible for solving a defined problem. Within the BDD project, the ZTP feature team is one of several feature teams that work with a lead team on the project. 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. However, for the approach to work, it is vitally important that the teams synchronize their efforts and maintain active communication with each other and the Project Management team. This is particularly important in complex projects, where there is a danger that a feature team may focus on its portion of the project to the exclusion of the role it plays in the overall project. CommunicationThe team’s ability to communicate and cooperate both internally among team members and externally with other feature or function teams and project stakeholders is key to successful project implementation. Within the team, each role is considered equally important, and decisions are made jointly. Across teams, and between individual feature teams and the Project Management team (defined as the lead team in this document), the process is more formalized, with well-defined pathways of communication. This formality does not prevent informal communication between teams, which is encouraged, but it does ensure that important 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, it is important that all communications with stakeholders be routed through the Project Management team. This process ensures that management is always aware of the state of the customer relationship, and it helps enhance customer satisfaction in the deployment process. Additional Guidance on the MSF Team ModelFor additional guidance on the MSF Team Model, see the MSF Team Model white paper at http://www.microsoft.com/technet/itsolutions/msf/default.mspx.
|
In This Article
|
