Setting Up the Team
Within the Microsoft® Deployment Solution Accelerator project, the Security feature team is one of several feature teams that work with a project management team to accomplish specific tasks and ensure that current security measures are implemented at all stages of the work. A feature team is a cross-organizational team responsible for solving a defined problem. Microsoft Deployment is the next version of Business Desktop Deployment (BDD) 2007.
Note In this document, Windows applies to the Windows Vista®, Windows® XP Professional, Windows XP Tablet PC Edition, Windows Server® 2008, and Windows Server 2003 operating systems unless otherwise noted.
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 in parallel on many tasks, with the application of specialized expertise where needed. A great advantage of this approach is an enhanced ability to manage large projects by executing many tasks simultaneously.
For the approach to work, however, it is vitally important that the teams synchronize their efforts and maintain active communication among themselves and the project management team. This is particularly important during complex projects, when a feature team may focus on its portion of the project to the exclusion of the role it plays in the overall project.
On This Page
.gif){kind=icon}
Communication
Additional Guidance on Team Models
Communication
Key to successful project implementation is the team’s ability to cooperate and communicate both internally with its own members and externally with other feature or function teams within the project and project stakeholders.
Within the team, each role is considered to have equal importance, even though the roles may vary. Important team decisions are characterized by joint decision-making. For communication across teams and between individual feature teams and the project management team (defined as the lead team in this document), the process is more formal, with well-defined pathways. This formality does not prevent informal communication among the teams (in fact, informal interaction is encouraged), but it does ensure that important communications are well documented, occur at the right levels, 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 the product manager on the lead team 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 in the deployment process is enhanced.
Additional Guidance on Team Models
For additional guidance on the MSF Team Model, see the white paper, “MSF Team Model,” at https://www.microsoft.com/technet/itsolutions/msf. Additional information about the Microsoft Operations Framework (MOF) is available at https://www.microsoft.com/mof.
Download
Get the Microsoft Deployment Solution Accelerator
Update Notifications
Sign up to learn about updates and new releases
Feedback