微软项目管理.pptx

《微软项目管理.pptx》由会员分享，可在线阅读，更多相关《微软项目管理.pptx（114页珍藏版）》请在得力文库 - 分享文档赚钱的网站上搜索。

1、微微软项软项目管理目管理AgendanOverviewnTeam ModelnRisk ManagementnProcess nVision approved milestonenProject plan approved milestonenScope complete milestonenRelease milestoneProject Failure RatesApplication Development ProjectsChallengedSucceeded Failed28%28%46%46%26%26%“When projects fail,its rarely technica

2、l.”Jim Johnson,The Standish GroupRoot Causes of FailurenSeparation of goal and functionnSeparation of business and technologynLack of common language and processnFailure to communicate and act as a teamnProcesses that are inflexible to changeAgendanOverviewnTeam ModelnRisk ManagementnProcess nVision

3、 approved milestonenProject plan approved milestonenScope complete milestonenRelease milestoneLesson 2:Team Model for Application DevelopmentA high-level overview of the team model roles and responsibilities in an application development projectTeam Goals for SuccessnSatisfied customersnDelivery wit

4、hin project constraintsnDelivery to specifications that are based on user requirementsnRelease after addressing all known issuesnEnhanced user performancenSmooth deployment and ongoing managementTeam of PeersnIs a team whose members relate as equalsnHas specific roles and responsibilities for each m

5、embernEmpowers individuals in their rolesnHolds members accountable for the success of their rolesnDrives consensus-based decision-making nGives all team members a stake in the success of the project ProgramProgramManagementManagementDevelopmentDevelopmentTestingTestingLogisticsLogisticsManagementMa

6、nagementUserUserEducationEducationProductProductManagementManagementTeam Model for Application DevelopmentCommunicationProduct Management RolenActs as customer advocate to the teamnActs as team advocate to the customernDrives shared project visionnManages customer expectationsnDevelops,maintains,and

7、 executes the business casenDrives feature identification and prioritizationnDevelops,maintains,and executes the communications planProductProductManagementManagementProgram Management RolenDrives the overall processnManages resource allocationnManages the project schedule and reports project status

8、nManages the product scope and specificationnFacilitates team communication and negotiationnDrives overall critical trade-off decisionsProgramProgramManagementManagementDevelopment RolenBuilds and tests features to meet the specification and customer expectationsnParticipates in designnEstimates tim

9、e and effort to complete each featurenServes the team as a technology consultantDevelopmentDevelopmentTestingTestingTesting RolenDevelops testing strategy,plans,and scriptsnManages the build processnConducts tests to accurately determine the status of product developmentnParticipates in setting the

10、quality barUser Education RolenActs as team advocate to the end usernActs as end-user advocate to the teamnParticipates in defining user requirementsnParticipates in designing featuresnDesigns and develops user support systemsnDrives the usability processUserUserEducationEducationLogisticsLogisticsM

11、anagementManagementLogistics Management RolenActs as team advocate to operations nActs as operations advocate to the teamnPlans and manages product deploymentnParticipates in design,focusing on manageability,supportability,and deployabilitynSupports the product during beta testingnTrains operations

12、and help desk personnel for product releaseTeam and Goal AlignmentTeam roleProduct managementProgram management DevelopmentTestingUser educationLogistics managementGoalSatisfied customersDelivery within project constraintsDelivery to product specificationsRelease after addressing all known issuesEnh

13、anced user performanceSmooth product deploymentNot a Traditional Organizational ChartTestingDeveloperProjectManagerLogisticsDeveloperAnalystUser EducationCoordination with External TeamsTechnology FocusBusiness FocusEnd UsersBusinessArchitectsandPlannersCustomerTechnology Architectsand Steering Comm

14、itteesOperations and SupportGroupsEndUsersProject TeamUserEducationDevelopmentTestingLogisticsManagementProductManagementProgramManagementLesson 3:Underlying Team Model PrinciplesSome of the principles and practices that make the team model successfulPrinciples of a Successful TeamnShared project vi

15、sionnProduct mindsetnZero-defect mindsetnCustomer-focused mindset nWillingness to learnnWhat it meansnClearly understanding project goals and objectivesnUnderstanding and buying into a vision that is held by all team members and the customernWhy it is importantnProvides the team a uniform sense of p

16、urposenResolves conflicting and contradictory visionsnClarifies project goals and objectivesnEnsures that team members are working toward the same goalShared Project VisionProduct MindsetnWhat it meansnTreating all work as part of a projectnTreating the final deliverable of the project as a productn

17、Why it is importantnFocuses the team on execution rather than processnEnables the team to use product development techniquesnIncreases team identity and accountabilityZero-Defect MindsetnWhat it meansnCommitting to qualitynPerforming work at the highest possible level of qualitynFocusing on achievin

18、g the quality bar set by the teamnWhy it is importantnIncreases product stabilitynIncreases schedule predictabilitynImproves accountabilityCustomer-Focused MindsetnWhat it meansnCommitting to understanding and solving the business problemnFocusing on the alignment of business and technologynInvolvin

19、g the customer throughout the processnWhy it is importantnIncreases focus on customer needs,which improves ability to solve the business problemnFocuses innovation on solving the business problemWillingness to LearnnWhat it meansnCommitting to improvement through gathering and sharing knowledgenInst

20、itutionalizing learning through such techniques as reviews and postmortems nWhy it is importantnAllows team members to benefit from mistakesnHelps team members to repeat successesnMandates time for the team to learnLesson 4:Scaling the Team ModelHow to scale the team model to accommodate projects of

21、 varying sizesScaling for Small ProjectsProgramProgramManagementManagementDevelopmentDevelopmentTestingTestingLogisticsLogisticsManagementManagementUserUserEducationEducationProductProductManagementManagementProgramProgramManagementManagementDevelopmentDevelopmentTestingTestingLogisticsLogisticsMana

22、gementManagementUserUserEducationEducationProductProductManagementManagementNoNPossiblePUnlikelyUPPPPPPPPPPUUUUUUUUNNNNNNNNNNNNProductProductManagementManagementExample:Combined RolesProgramProgramManagementManagementDevelopmentDevelopmentTestingTestingLogisticsLogisticsManagementManagementUserUserE

23、ducationEducationScaling for Large ProjectsnDivide large teams into smaller teams,which have nLower process overheadnLower management overheadnLower communication overhead nFaster implementationnCreate feature teamsmultidisciplinary subteams organized around product feature setsnCreate function team

24、sunidisciplinary subteams organized by functional roleExample:Feature Teams DevelopmentDevelopmentTestingTestingUserUserEducationEducationProgramProgramManagementManagementDevelopmentDevelopmentTestingTestingUserUserEducationEducationProgramProgramManagementManagementDevelopmentDevelopmentTestingTes

25、tingUserUserEducationEducationProgramProgramManagementManagementProgramProgramManagementManagementDevelopmentDevelopmentTestingTestingLogisticsLogisticsManagementManagementUserUserEducationEducationProductProductManagementManagementLeadTeamUITeamPrinting TeamCoreTeamExample:Function TeamGroup Produc

26、tManagementEvangelismPublicRelationsMarketingProduct PlanningProductProductManagementManagementAgendanOverviewnTeam ModelnRisk ManagementnProcess nVision approved milestonenProject plan approved milestonenScope complete milestonenRelease milestoneLesson 2:Risk Management OverviewThe MSF approach to

27、risk managementRetired RisksRisk Assessment DocumentTop 103.Plan 5.Control2.Analyze1.IdentifyRiskStatements4.TrackRisk Management ProcessThe ongoing deliverable of this The ongoing deliverable of this process is a living risk assessment process is a living risk assessment documentdocumentAgendanOver

28、viewnTeam ModelnRisk ManagementnProcess nVision approved milestonenProject plan approved milestonenScope complete milestonenRelease milestoneLesson 1:Process Model for Application DevelopmentA high-level overview of the MSF process model for application developmentProcess Models nLife cycle models e

29、stablish the order for project activitiesnTwo models are popularnThe waterfall modelnThe spiral(or rapid application development)modelnMSFs process model for application development combines the benefits of bothnMilestone-based processnFlexible and iterative processProcess Model for Application Deve

30、lopmentIENVSOGINNIPLANIGNNDEVLOPIGENSTABILZNGIIVision Vision ApprovedApprovedProject PlanProject PlanApprovedApprovedScope Scope CompleteCompleteReleaseReleaseMilestone-Driven AccountabilityMilestoneVision approvedProject plan approvedScope completeReleasePrimary driverProduct managementProgram mana

31、gementDevelopment and user educationTesting andlogistics managementPrinciples of a Successful ProcessnCreating living documents nUsing versioned releasesnMaking project trade-offsResourcesResourcesFeaturesFeaturesScheduleScheduleBenefits of Versioned ReleasesnForce closure on project issuesnSet clea

32、r and motivational goals with all team membersnManage the uncertainty and change in project scopenEncourage continuous and incremental feature deliverynEnable shorter time to marketMaking Project Trade-offsResourcesResourcesFeaturesFeaturesScheduleScheduleProject Trade-off MatrixConstrainConstrainOp

33、timizeOptimizeAcceptAcceptScheduleScheduleFeaturesFeaturesResourcesResourcesResourcesResourcesFeaturesFeaturesScheduleScheduleAgendanOverviewnTeam ModelnRisk ManagementnProcess nVision approved milestonenProject plan approved milestonenScope complete milestonenRelease milestoneEnvisioning PhaseAchie

34、ving the vision approved milestoneEnvisioningCreating a high-level view of the projects goals and constraints nServes as an early form of planningnHelps the team pull different perspectives into a common understandingnProvides the basis for future planning nCaptures what the customer and key stakeho

35、lders deem essential for successDefining the ScopeResourcesResourcesFeaturesFeaturesScheduleScheduleEnvisioningEnvisioningVision Approved MilestoneIENVSOGINNIPLANIGNNDEVLOPIGENSTABILZNGIIProject PlanProject PlanApprovedApprovedReleaseReleaseVision Vision ApprovedApprovedScope Scope CompleteCompleteS

36、ignals agreement onnThe reason for the projectnThe expected outcomenProject feasibilitynProject goals and constraintsnOpportunities and risksnProject structureTesting strategies;acceptance criteria;implications Team Focus During EnvisioningProduct managementProgram managementDevelopmentUser educatio

37、nTestingLogistics managementVision documentDesign goals;solution concept;project structurePrototypes;development options;implicationsDeployment implications;support implicationsUser performance needs and implicationsRoleFocusSuggested Interim MilestonesRisk Assessment Document DraftedVision Document

38、 DraftedVision Vision ApprovedApprovednAre visible at the team level nProvide an opportunity for team members to synchronize their worknProvide an opportunity for team members to assess project progress and statusCore Team FormedDeliverablePurpose+Vision document+Risk assessment document+Project str

39、ucture document+Describes what you want to do and how you plan to do it+Describes the risks the project entailsDescribes the projects organizational structureDeliverables for Vision ApprovedOwner+Product management+Program managementProgram managementContentPurpose+Problem statement+Vision statement

40、+Solution concept+User profilesBusiness goals+Design goals+Why you want to do it+What you want the product to be+What you will do+Who will use the productWhat you want to accomplish+How you plan to accomplish itContents of the Vision DocumentRisk Assessment DocumentAssessing preliminary project risk

41、s and planning their managementnIs created during the five-step risk management processnIs the initial assessment of project risknLays the groundwork for ongoing risk managementnProvides a basis for scheduling and decision-makingProject Structure DocumentDescribing the projects organizational struct

42、ure and project management processnLists information on team members nIncludes team logistical information nDescribes team processes nActs as a repository for project documentation templatesAgendanOverviewnTeam ModelnRisk ManagementnProcess nVision approved milestonenProject plan approved milestonen

43、Scope complete milestonenRelease milestoneLesson 1:Planning PhaseAchieving the project plan approved milestoneImportance of PlanningRepair Cost of Design Defects by Phase10080604020EnvisioningPlanningDevelopingStabilizingFurther Defining the ScopeResourcesResourcesFeaturesFeaturesScheduleSchedulePla

44、nningPlanningProject Plan Approved MilestoneIENVSOGINNIPLANIGNNDEVLOPIGENLSTABIZNGIIVision Vision ApprovedApprovedProject PlanProject PlanApprovedApprovedScope Scope CompleteCompleteReleaseReleaseSignals agreement onnProject trade-off strategynProject risksnWhat will be builtnWhen it will be builtnH

45、ow it will be builtnWho will build itTeam Focus During PlanningProduct managementProgram managementDevelopmentUser educationTestingLogistics managementRoleFocusDesign;communications plan and scheduleDesign;functional specification;master project plan and master project scheduleDesign;development pla

46、n and schedule;proof of concept developmentDesign evaluation;testing plan and scheduleDesign evaluation;logistics plan and scheduleDesign;user performance support;user education plan and scheduleSuggested Interim MilestonesFunctional Specification DraftedProject PlanProject PlanApprovedApprovedMaste

47、r Project Schedule DraftedMaster Project Plan DraftedDesign Process OverviewLogical DesignConceptual DesignScenariosScenariosPhysical DesignComponents,Components,User Interface,and User Interface,and Physical DatabasePhysical DatabaseObjects and Services,Objects and Services,User Interface,and User

48、Interface,and Logical DatabaseLogical DatabaseRelationship to PlanningProject PlanProject PlanApprovedApprovedPhysical Design BaselineConceptual DesignLogical DesignPhysical DesignVisionVisionApprovedApprovedLogical Design BaselineConceptual Design BaselineMSF Application ModelBusiness ServicesUser

49、ServicesData ServicesApplication 1Application 2DeliverablePurpose+Functional specification+Master project plan+Master project schedule+Revised master risk assessment document+Describes what will be built+Describes how it will be built+Describes when it will be built+Describes any issues in building

50、it+Deliverables for Project Plan ApprovedOwner+Program management+Program management+Program management+Program management+Contents of the Functional SpecificationContentPurpose+Vision summary+Design goals+Requirements+Usage summary+Features+Dependencies+Schedule summary+Issues+Appendixes+What you w