【正文】 e project as a product ? Why it is important ? Focuses the team on execution rather than process ? Enables the team to use product development techniques ? Increases team identity and accountability ZeroDefect Mindset ? What it means ? Committing to quality ? Performing work at the highest possible level of quality ? Focusing on achieving the quality bar set by the team ? Why it is important ? Increases product stability ? Increases schedule predictability ? Improves accountability CustomerFocused Mindset ? What it means ? Committing to understanding and solving the business problem ? Focusing on the alignment of business and technology ? Involving the customer throughout the process ? Why it is important ? Increases focus on customer needs, which improves ability to solve the business problem ? Focuses innovation on solving the business problem Willingness to Learn ? What it means ? Committing to improvement through gathering and sharing knowledge ? Institutionalizing learning through such techniques as reviews and postmortems ? Why it is important ? Allows team members to benefit from mistakes ? Helps team members to repeat successes ? Mandates time for the team to learn Lesson 4:Scaling the Team Model How to scale the team model to acmodate projects of varying sizes Scaling for Small Projects Program Management Development Testing Logistics Management User Education Product Management Program Management Development Testing Logistics Management User Education Product Management No N Possible P Unlikely U P P P P P P P P P P U U U U U U U U N N N N N N N N N N N N Product Management Example: Combined Roles Program Management Development Testing Logistics Management User Education Scaling for Large Projects ? Divide large teams into smaller teams, which have ? Lower process overhead ? Lower management overhead ? Lower munication overhead ? Faster implementation ? Create feature teams—multidisciplinary subteams anized around product feature sets ? Create function teams—unidisciplinary subteams anized by functional role Example: Feature Teams Development Testing User Education Program Management Development Testing User Education Program Management Development Testing User Education Program Management Program Management Development Testing Logistics Management User Education Product Management Lead Team UI Team Printing Team Core Team Example: Function Team Group Product Management Evangelism Public Relations Marketing Product Planning Product Management Agenda ? Overview ? Team Model ? Risk Management ? Process ? Vision approved milestone ? Project plan approved milestone ? Scope plete milestone ? Release milestone Lesson 2:Risk Management Overview The MSF approach to risk management Retired Risks Risk Assessment Document Top 10 3. Plan 5. Control 2. Analyze 1. Identify Risk Statements 4. Track Risk Management Process The ongoing deliverable of this process is a living risk assessment document Agenda ? Overview ? Team Model ? Risk Management ? Process ? Vision approved milestone ? Project plan approved milestone ? Scope plete milestone ? Release milestone Lesson 1:Process Model for Application Development A highlevel overview of the MSF process model for application development Process Models ? Life cycle models establish the order for project activities ? Two models are popular ? The waterfall model ? The spiral (or rapid application development) model ?MSF’s process model for application development bines the benefits of both ? Milestonebased process ? Flexible and iterative process Process Model for Application Development Vision Approved Project Plan Approved Scope Complete Release MilestoneDriven Accountability Milestone Vision approved Project plan approved Scope plete Release Primary driver Product management Program management Development and user education Testing and logistics management Principles of a Successful Process ? Creating living documents ? Using versioned releases ? Making project tradeoffs Features Benefits of Versioned Releases ? Force closure on project issues ? Set clear and motivational goals with all team members ? Manage the uncertainty and change in project scope ? Encourage continuous and incremental feature delivery ? Enable shorter time to market Making Project Tradeoffs Features Project Tradeoff Matrix Constrain Optimize Accept Schedule Features Resources Features Agenda ? Overview ? Team Model ? Risk Management ? Process ? Vision approved milestone ? Project plan approved milestone ? Scope plete milestone ? Release milestone Envisioning Phase Achieving the vision approved milestone Envisioning Creating a highlevel view of the project’s goals and constraints ? Serves as an early form of planning ? Helps the team pull different perspectives into a mon understanding ? Provides the basis for future planning ? Captures what the customer and key stakeholders deem essential for success Defining the Scope Features Envisioning Vision Approved Milestone Project Plan Approved Release Vision Approved Scope Complete Signals agreement on ? The reason for the project ? The expected oute ? Project feasibility ? Project goals and constraints ? Opportunities and risks ? Project structure Testing strategies。 acceptance criteria。 solution concept。 development options。 support implications User performance needs and implications Role Focus