Contents Overview 1 Team Goals for Success 2 The MSF Team Model 5 Principles of a Successful Team 16 Review 21 Module 4: MSF Team Model Information in this document is subject to change without notice. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Complying with all applicable copyright laws is the responsibility of the user. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. If, however, your only means of access is electronic, permission to print one copy is hereby granted. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.  1999 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, MS, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Other product and company names mentioned herein may be the trademarks of their respective owners. MOC Project Advisor: Janet Wilson MOC Project Lead: Sharon Salavaria Program Manager/MSF Project Manager: Sharon Limbocker Program Manager/Technical Consultant: Dolph Santello Instructional Designer: Marilyn McCune (Independent) Product Manager: Jim Wilson Product Manager: Jerry Dyer Graphic Artist: Andrea Heuston (Artitudes Layout & Design) Editing Manger: Lynette Skinner Editors: Marilyn McCune (Independent) and Wendy Cleary (S&T Onsite) Production Support: Ed Casper (S&T Consulting) Manufacturing Manager: Bo Galford Lead Product Manager: Development Services: Elaine Nuerenberg Lead Product Manager: Mary Larson Group Product Manager: Robert Stewart Module 4: MSF Team Model iii Instructor Notes Module 4: MSF Team Model This module provides students with an introduction to the Microsoft Solutions Framework (MSF) Team Model, including the team goals for success, team roles of the model, how to scale the model for small or large projects, principles of a successful team, and how to apply the model to different types of projects. At the end of this module, students will be able to:  Describe the six team goals for a successful project.  Name the six roles of the MSF Team Model.  Define feature team and function team, and describe the function of each.  Describe the fundamentals of good teaming by defining team of peers, shared product vision, product mindset, zero-defect mindset, customer- focused mindset, and willingness to learn, as they apply to successful teaming.  Describe what happens to the MSF Team Model when it is applied to an enterprise architecture (EA) project, an application development (AD) project, and an infrastructure deployment (ID) project. Materials and Preparation This section provides you with the materials and preparation needed to teach this module. Materials To teach this module, you need the following materials:  Microsoft® PowerPoint® file 1639a_04.ppt  Module 4, “MSF Team Model”  A flip chart or white board Preparation To prepare for this module, you should: • Read all the materials for this module. Presentation: 60 Minutes Activity: 15 Minutes iv Module 4: MSF Team Model Instructions for Activity A: Designing a Dream House This activity is designed to reinforce what students have just learned about MSF Team Model roles and responsibilities. In this activity, the instructor creates three teams of four students. Assign the following roles to each team: product manager, program manager, programmer, and customer. Each team is assigned the task of designing the customer’s dream house. In each team, the customer sits apart from the others and is unable to overhear and participate in the discussion. Only the product manager has contact with the customer.  The first team has no contact with the customer.  The product manager in the second team can meet with the customer once.  The third team uses the versioning process, so the product manager can meet with the customer after each design revision. The teams have five minutes to complete the task. There is a penalty for each minute over five minutes. At the end of five minutes, each team presents the house design to the class. The customer gives rates the design on a scale of 1 to 10. One point is deducted for each minute over five minutes. Because the third team had several interactions with the customer, their design should be closest to the customer’s expectations. Estimated time to complete this activity: 15 minutes Objective • Following is the learning objective for this activity: The student will be able to describe the fundamentals of good teaming, including a team of peers, shared product vision, product mindset, zero- defect mindset, customer-focused mindset, and willingness to learn. Setup There are no special setup requirements for this activity. Module 4: MSF Team Model v Module Strategy Use the following strategy to present this module:  Team Goals for Success This section presents the team goals for success as identified by MSF. Topics in this section include: • The Six Team Goals for Success • Understanding the Goals  The MSF Team Model This section presents the six team roles of the MSF Team Model, and the relationship between each team role and their corresponding project goal. Topics in this section include: • Hierarchical Teams and the Team Model • Product Management Role • Program Management Role • Development Role • Testing Role • User Education Role • Logistics Management Role • Team and Goal Alignment  Principles of a Successful Team The section presents the principles that underlie the Team Model, the basics of scaling the Team Model for small or large projects, and team role key responsibilities when the Team Model is applied to different project types. Topics in this section include: • Scaling the MSF Team Model • Applying the MSF Team Model vi Module 4: MSF Team Model Background on Scaling the MSF Team Model Scaling for Small Projects Although the Team Model consists of six roles, a team does not always require a minimum of six people. The key is that all six roles must be represented on every team and that some roles—particularly development—should not be combined with anything else. When scaling teams for small projects, keep in mind the following issues:  Individual team members can have multiple roles within a project.  Team members responsible for multiple roles should make it clear which role or roles they represent when they speak or offer guidance.  Teams can function with fewer than six people.  Be sure that all perspectives are represented.  Avoid conflicts of interest. Not combining Program Managers and Product Managers is just an example of avoiding conflicts of interest. Product management wants to satisfy the customer, whereas program management wants to ship on time and within budget.  Do not distract the developers. Developers are the builders and should not be distracted from their main task by having to take on the tasks of another role on the team. For example, adding additional responsibilities from outside development to the development team is likely to slip the development schedule.  There are no absolutes, however. Ultimately, success in combining roles depends on the skills of individuals. Scaling for Large Projects: Feature Teams The MSF Team Model advocates breaking large teams (more than ten people) into small, multidisciplinary feature teams and breaking complex or cumbersome roles into a smaller, focused feature teams. Referring to the slide, feature teams are small teams that work in parallel, making certain to synchronize their efforts frequently. The logic behind feature teams includes the following:  Feature team members are drawn from four of the six roles that make up the Team Model. That is because product management and logistics management tend to focus more at the product level than at the feature level.  Each team is responsible for all aspects of the feature to which it has been assigned.  Feature teams are empowered and accountable because their members have access to the people that they need for making good decisions.  Treating large teams as a collection of small teams offers the benefits enjoyed by smaller teams, such as lower process and communications overhead and greater flexibility. Module 4: MSF Team Model vii Scaling for Large Projects: Function Teams Function teams are teams that exist within a role and are formed when tasks within a role are large enough to require dedicated resources. Function teams are effectively the opposite of feature teams. They are created when a team or project is so large that it requires grouping people within a role into teams based on their function. When you create a function team, consider the following:  Function teams are made up of people fulfilling different aspects of the team role that they represent. More than one person per role does not make a function team. It is the delineation of those people by their tasks that makes a function team.  A product management function team might have one person focusing on product planning, whereas another does marketing and yet another does public relations.  A development function team might group developers by the service layer that they work on—for example, user, business, or data. This could occur within a feature team. Module 4: MSF Team Model 1 Overview  Team Goals for Success  The MSF Team Model  Principles of a Successful Team  Scaling the MSF Team Model  Applying the MSF Team Model At the end of this module, you will be able to:  Describe the six team goals for a successful project.  Name the six roles of the Microsoft Solutions Framework (MSF) Team Model.  Describe the fundamentals of good teaming by defining team of peers, shared product vision, product mindset, zero-defect mindset, customer- focused mindset, and willingness to learn, as they apply to successful teaming. • Describe scaling the Team Model for small and large projects. Define feature team and function team. • Describe what happens to the Team Model when it is applied to an enterprise architecture (EA) project, an application development (AD) project, and an infrastructure deployment (ID) project. Slide Objective To provide an overview of the module topics and objectives. Lead-in In this module, you will learn about team goals for success, principles of a successful team, and the MSF Team Model. 2 Module 4: MSF Team Model    Team Goals for Success  The Six Team Goals for Success  Understanding the Goals There are six team goals for success that underlie the MSF Team Model satisfied customers, delivery within project constraints, delivery to specification, release after addressing all known issues, enhanced user performance, and smooth deployment and ongoing management. Slide Objective To introduce the topics presented in this section. Lead-in The team goals for success underlie the MSF Team Model. [...]... conditioning, and chilled water) Module 4: MSF Team Model 21 Review Slide Objective To reinforce module objectives by reviewing key points Lead-in The review questions cover some of the key concepts taught in the module Team Goals for Success The MSF Team Model Principles of a Successful Team Scaling the MSF Team Model Applying the MSF Team Model 1 What are the team goals for success? The team goals for success... equate to equally valued roles The relationship of goal and role is the basis for the idea of a team of peers, which is the heart of the Team Model for application development Module 4: MSF Team Model The MSF Team Model Slide Objective To present the Team Model roles Lead-in The MSF Team Model includes six team roles that are independent, interdependent, and multidisciplinary Program Management Product... teams Function teams are effectively the opposite of feature teams They are created when a team or project is so large that it requires grouping people within a role into teams based on their function Module 4: MSF Team Model Applying the MSF Team Model Slide Objective To outline this topic Lead-in Just like the MSF Process Model, the MSF Team Model can be applied to any type or size of project Product... same 5 6 Module 4: MSF Team Model Hierarchical Teams and the Team Model Slide Objective To show the Team Model in relation to a hierarchical model Project Manager Lead-in The Team Model is not intended to replace a traditional organizational chart; it is intended to coexist with hierarchical structures and, by doing so, to overcome issues related to hierarchical structures Key Points The Team Model is.. .Module 4: MSF Team Model 3 The Six Team Goals for Success Slide Objective To present the six team goals for success that form the basis of the Team Model Lead-in The Team Model is built on principles that include the six team goals for success, which become the responsibilities of the Team Model roles Satisfied Customers Delivery within Project... enable teams to make mid-course corrections to avoid repeating mistakes and to create best practices out of the things that went well Capturing and sharing best practices are fundamental to ongoing improvement and continuing success 18 Module 4: MSF Team Model Scaling the MSF Team Model Slide Objective To introduce the topics presented in this section Lead-in One of the key benefits of the MSF Team Model. .. High process overhead To overcome some of the issues inherent in hierarchical team structures, the MSF Team Model can be integrated to provide: Shared team goals for success Clear roles and responsibilities Team of peers Direct communication Team and project goal alignment Flexibility and scalability Module 4: MSF Team Model 7 Product Management Role Slide Objective To present the generic responsibilities... Model roles Module 4: MSF Team Model 15 Activity A: Designing a Dream House Slide Objective To introduce the activity Lead-in In this activity, you will apply what you have just learned about the six roles of the MSF Team Model This activity is designed to reinforce what you have just learned about MSF Team Model roles and responsibilities In this activity, the instructor creates three teams of four... Projects: Feature Teams Scaling for Large Projects: Function Teams The MSF Team Model provides a project team with flexibility because it is scalable The model can be applied to small or large projects Scaling for small projects Although the Team Model consists of six roles, a team does not always require a minimum of six people The key is that all six roles must be represented on every team and that some... product management 2 What are the six roles of the Team Model? The six roles of the Team Model are product management, program management, development, testing, user education, and logistics management 22 Module 4: MSF Team Model 3 What is one principle of a successful team, and why is it important? Shared project vision is important because it provides a team with a uniform sense of purpose, resolves . include: • Scaling the MSF Team Model • Applying the MSF Team Model vi Module 4: MSF Team Model Background on Scaling the MSF Team Model Scaling for. Module 4: MSF Team Model 1 Overview  Team Goals for Success  The MSF Team Model  Principles of a Successful Team  Scaling the MSF Team Model 