PM-項目管理-1概述課件

ProjectManagementChap.1Introduction-概述12011春夏學期授課版ProjectManagementChap.1IntroAgenda-本章需要解決的問題WhyneedProjectManagement？PM&SoftwarecharacteristicsProblemsinSWdevelopmentandSPMChallengeofSWdevelopment22011春夏學期授課版Agenda-本章需要解決的問題WhyneedProje現(xiàn)代管理的三個熱點：戰(zhàn)略管理項目管理運作管理就一個組織的管理而言，應該包括三個部分。1.戰(zhàn)略管理：從宏觀上明確和把握發(fā)展方向2.運作管理：對日常的、重復性工作的管理3.項目管理：對一次性的、創(chuàng)新性工作的管理由于項目管理的效率高、反映靈敏，所以運用的企業(yè)更多。32011春夏學期授課版現(xiàn)代管理的三個熱點：戰(zhàn)略管理項目管理運作管理就一個組Moredregsprojectofbeancurd？Illogicalobjective（時間）jerry-build（成本）Subcontract（手續(xù)）Notrefundloan？RiskManagement(風險)MoreUnsuccessfulinfoingproject？Backbonejob-hopping，manpoweralteration(人力資源)Requirementschanged（范圍）Why？42011春夏學期授課版MoredregsprojectofbeancurIn21st,everythingisproject,orisbecomingProject…PaulGracePresidentofPMIProfessionalscertificationcommittee52011春夏學期授課版In21st,everythingisprojectImportant2jobsforfuturesTechniquesinnovation技術革新的典范-優(yōu)選法Projectmanagement沒有項目管理就沒有現(xiàn)代產(chǎn)業(yè)HuaLuogeng華羅庚62011春夏學期授課版Important2jobsforfuturesTe46%26%28%SuccessUSStandishGroup,對1999年當年軟件項目的統(tǒng)計failingStatisticsofSuccessandfailingforITProject有問題的項目Overbudget,overtimeEtc.72011春夏學期授課版46%26%28%SuccessUSStandishGrPMHistory項目管理，遠自幾千年前的人類文明，近如現(xiàn)代工業(yè)領域。例如GreatWallofChina,EgyptianPyramids(金字塔)

航空航天工程項目and建筑工程項目82011春夏學期授課版PMHistory項目管理，遠自幾千年前的人類文明HistoryofProjectManagementModernprojectmanagementbeganwiththeManhattanProject,whichtheU.S.militaryledtodeveloptheatomicbombIn1917HenryGanttdevelopedtheGanttchartasatoolforschedulingworkinjobshopsIn1958,theNavydevelopedPERTchartsInthe1970s,themilitarybeganusingprojectmanagementsoftware,asdidtheconstructionindustryBythe1990s,virtuallyeveryindustrywasusingsomeformofprojectmanagement1985:TQM1990-93:Re-engineering,self-directedteams1996-99:Riskmgmt,projectoffices2000:M&A,globalprojects92011春夏學期授課版HistoryofProjectManagementMPMdevelopmentCPM,PERTNowPMapplicationsismoreandmorePeoples,customer-oriented,softmanagement102011春夏學期授課版PMdevelopmentCPM,PERT102011春ProjectManagementKnowledgeContinuestoGrowandMaturePMIlaunchedtheirCenterforPMKnowledgeandWisdominDecember2001PMIhostedtheirfirstresearchconferenceinJune2000inParis,France,secondoneinJuly2002ThePMBOKGuide–2000EditionisanANSIstandard,andPMI’scertificationdepartmentearnedISO9000certificationHundredsofnewbooks,articles,andpresentationsrelatedtoprojectmanagementhavebeenwritteninrecentyears112011春夏學期授課版ProjectManagementKnowledgeCHowProjectManagement(PM)RelatestoOtherDisciplinesMuchoftheknowledgeneededtomanageprojectsisuniquetoPMHowever,projectmanagersmustalsohaveknowledgeandexperienceingeneralmanagementtheapplicationareaoftheprojectProjectmanagersmustfocusonmeetingspecificprojectobjectives122011春夏學期授課版HowProjectManagement(PM)RePMTripleConstraint每一個項目都會受到范圍目標、時間目標和成本目標的約束這三個目標又經(jīng)常存在沖突，一個合格的項目經(jīng)理，其責任之一就是平衡三者的關系在此過程中，由于項目的不確定性和資源使用的競爭性，平衡往往成為權衡因此，成功的項目管理，就意味著同時實現(xiàn)范圍、時間和成本三個目標，并讓項目利益相關者滿意！132011春夏學期授課版PMTripleConstraint每一個項目都會受到范Inwhatwaysdomodernprojectsdifferfromancientprojects?現(xiàn)代人們對項目及其管理有一些什么樣的認識和做法？142011春夏學期授課版InwhatwaysdomodernprojectProjectsmaybeunderaFunctionalOrganizationMatrixOrganizationProjectOrganization152011春夏學期授課版ProjectsmaybeunderaFunctioFivefunctionsofthePMPlanningOrganizingLeadershipControlChange162011春夏學期授課版FivefunctionsofthePMPlannClassicalApproachAssumesthereisauniversalsetofmanagementprinciples采用公認的管理原則BehavioralApproach:emphasisonhumanaspects強調(diào)人性化SystemApproach采用系統(tǒng)論的方法172011春夏學期授課版ClassicalApproachAssumestherSoftwareneedsmanagement182011春夏學期授課版Softwareneedsmanagement18201SoftwareneedsmanagementSoftwarecharacteristics特性CostStructure成本IndustrialProblems產(chǎn)業(yè)SoftwareDisaster危機ProblemsinSoftwareTechniques技術進步PositioninSEKnowledgestructure知識結構192011春夏學期授課版SoftwareneedsmanagementSoftwSoftwarecharacteristicsEssentials:logicelements,notentitativeelements.

DevelopingSoftware，andproducingproduct.NowearandtearinusingtimeFailingprobabilityTubcurveofproduct202011春夏學期授課版SoftwarecharacteristicsEssentSoftwarecharacteristics(cont.)timeFailingprobability不愿看到的realcurveofSD期望的IdealcurveofSD212011春夏學期授課版Softwarecharacteristics(cont.Softwarecharacteristics(cont.)Production:Standardization&assembleMassSW:customizationScientificarithmeticfunctionlib(1960’s）DatastructurereusingReusingcomponents人們設法改進軟件開發(fā)的過程。222011春夏學期授課版Softwarecharacteristics(contCostStructureischangedOne-offCostofmanufactureLogicproduct—minimediacostisignoredIcessMoreMaintaincostserviceisquality解決軟件危機本來就是為了回答兩個問題：如何高效率的開發(fā)軟件如何維護越來越多的軟件232011春夏學期授課版CostStructureischangedOne-oMainproblemsinSWindustryIndustrialscale如何定量度量軟件的規(guī)模？Coretechnique如何發(fā)展核心技術Pirateandillegalcopy如何防止盜版和非法拷貝？242011春夏學期授課版MainproblemsinSWindustryIn為什么會有這樣的問題存在？

發(fā)展策略的缺乏印度我們自己發(fā)展規(guī)則知識決定一切（創(chuàng)新，團隊）頭腦產(chǎn)業(yè)新的管理模式252011春夏學期授課版為什么會有這樣的問題存在？發(fā)展策略的缺乏252011春夏學軟件原因引起的災難NATO，1958，SoftwareDisastersisputforwardMoreandmoreunsuccessfulSWProject:NASA,1999-10,Marsweathersatellitelost.US$125million.1963-1966,IBM360OS(1000Bug/Rel.)262011春夏學期授課版軟件原因引起的災難NATO，1958，SoftwareD軟件原因引起的災難(Cont.)Somedata：BeyondSWtimedeadline:about70％SWProject.Beyond20%-50%planningrel.timeinBigProjectBeyondSWcost：90％SWProject.Biggertheprojectis，morecosttospendAuditBureauUS:usablecontractSWisonly2％98％isunsuccessful272011春夏學期授課版軟件原因引起的災難(Cont.)Somedata：2720SoftwareDisasters(Cont.)CrunchModeDeathMarch282011春夏學期授課版SoftwareDisasters(Cont.)CrunSoftwareDisasters(Cont.)chronicafflictionSuggestedbyProf.DanielTiechrow,UniversityofMichigan292011春夏學期授課版SoftwareDisasters(Cont.)chro軟件災難的特點SD開發(fā)逾期.SD成本超過預算.SQA質(zhì)量沒有保證.302011春夏學期授課版軟件災難的特點SD開發(fā)逾期.302011春夏學期授課版規(guī)模、成本、進度、質(zhì)量等的定量度量復雜性控制提高生產(chǎn)效率ProblemsinSWtechnique312011春夏學期授課版規(guī)模、成本、進度、質(zhì)量等的定量度量ProblemsinSExchange2000Windows2000PM25About250Dev.140About1700Test350About3200e.g.:?Windows95have10,000,000linecode

?Windows2000have50,000,000linecodemore3000engineersand100+teamsExchange2000和Windows2000DevOrg.structure322011春夏學期授課版Exchange2000Windows2000PM25Abtypeofproject332011春夏學期授課版typeofproject332011春夏學期授課版typeofproject規(guī)模(big,middle,mini)復雜度

產(chǎn)品/服務

應用

用戶342011春夏學期授課版typeofproject規(guī)模(big,middlPMinSWEBOK《SWEBOK》GuidetotheSoftwareEngineeringBodyofKnowledge352011春夏學期授課版PMinSWEBOK《SWEBOK》352011春夏學

ContentsSoftware&SESPMSystemengineeringRequirementanalysisData-process-orientedanalysisOORAData-OrientedSoftwareDesignData-process-orientedDesignOODUIProgramandcodingSoftwareTestingmantainanceConfigurationmanagementReuseTech.RPCASENewTech.forSWD362011春夏學期授課版ContentsSoftware&SEUI362011ChallengeinSWdevelopment

軟件發(fā)展挑戰(zhàn)Deadlines期限(85%)Resourceconstrained需求扭曲（83％）Communicationswithteams通信消耗（80％）Commitmentfromteam團隊承諾（74％）Makemilestone里程碑（90％）Change變更（60％）Planningagreeforteams計劃符合性（57％）Topcommitment最終義務（45％）Conflict沖突（42％）,subcontract轉(zhuǎn)包（38％）372011春夏學期授課版ChallengeinSWdevelopment

軟件ChallengeforPMProjectmanager：EstimationandPlanning預算和計劃Qualitystd.andmatrix品質(zhì)Guidefororganizationstrategies組織策略Techniquesofvisualizingtheprocess過程技術Roledefinition角色分配Ruleforsuccess成功規(guī)則NoSTD.沒有標準382011春夏學期授課版ChallengeforPMProjectmanageChallengeforteammembersTeammembers：Incorrectworkingdescriptions不恰當?shù)墓ぷ髅枋鯥Tmanagementmiss管理疏忽InsufficiencyApplicationdomainknowledge應用領域知識缺乏Insufficiencydocument文檔缺乏Precedingtaskisnotfinishedontime—includingequipment任務不能按時完成Lackofcommunicationwithuserandengineerer和用戶缺乏溝通Lackofqualitycontrol質(zhì)量控制缺乏SWDevelopmentenvironmentchange外界環(huán)境變化Deadlinepress終期壓力392011春夏學期授課版ChallengeforteammembersTeamMistake過失inSWdevelopmentSource<Rapiddevelopment>Productaspect需求鍍金：項目具有比實際需求多得多的性能功能蔓延：項目平均會有25%的需求變更（Jones1994）開發(fā)人員的鍍金：開發(fā)人員著迷于新技術又推又拉的交易：經(jīng)理在批準項目進度順延時又加入了新的功能研究導向的開發(fā)402011春夏學期授課版Mistake過失inSWdevelopmentSou軟件項目常見錯誤過程缺乏計劃過于樂觀的計劃在壓力下放棄計劃缺乏足夠的風險管理承包人導致的失敗在模糊的項目前期（fuzzyfrondend）浪費時間前期活動不合要求412011春夏學期授課版軟件項目常見錯誤過程412011春夏學期授課版軟件項目常見錯誤設計低劣缺少質(zhì)量保證措施缺少管理控制太早和過于頻繁的集成項目估算時遺漏必要的任務追趕計劃魯莽編碼422011春夏學期授課版軟件項目常見錯誤設計低劣422011春夏學期授課版軟件項目常見錯誤技術相關的錯誤銀彈綜合癥:過于相信以前沒有采用過的技術的宣傳過高估計了新技術或方法帶來的節(jié)省量項目中間切換工具缺少自動的源代碼控制手段432011春夏學期授課版軟件項目常見錯誤技術相關的錯誤432011春夏學期授課版軟件項目常見錯誤人員相關的錯誤挫傷積極性人員素質(zhì)低對有問題的員工失控英雄主義項目后期加入人員：“火上加油”辦公環(huán)境差開發(fā)人員與客戶之間發(fā)生摩擦不現(xiàn)實的預期442011春夏學期授課版軟件項目常見錯誤人員相關的錯誤442011春夏學期授課版軟件項目常見錯誤缺乏有效的高層對項目的支持缺乏各種角色的齊心協(xié)力缺乏用戶介入政治高于物質(zhì)充滿想像：“項目組沒人真正相信他們能夠按給定的計劃進度完成項目，但他們認為如果每個人能夠努力工作，并且不出現(xiàn)問題，他們可能會很幸運地按時完成任務。452011春夏學期授課版軟件項目常見錯誤缺乏有效的高層對項目的支持452011春夏學軟件項目常見的錯誤試分析以下故事中的項目所存在的錯誤：

一天，一位年青人被選來“寫”一個用在自動化制造設備上的程序。選擇他的理由很簡單：他是技術小組中唯一參加過編程培訓的人。他懂得匯編語言和Fortran語言，但是他不知道軟件工程，更不知道軟件計劃和跟蹤方面的知識。462011春夏學期授課版軟件項目常見的錯誤試分析以下故事中的項目所存在的錯誤：462軟件項目常見的錯誤他的老板給了他一些手冊和對系統(tǒng)功能的口頭描述。他被告知系統(tǒng)必須在兩個月內(nèi)開發(fā)完成。他讀了手冊，考慮了他的方法，然后開始編程，兩個星期后，老板把他叫到了辦公室并問他事情干得怎么樣？“很好”，雄心勃勃的年青的工程師說，“比我想像的要簡單的多。我已經(jīng)接近完成75％了。”老板笑了，“真不可思議”，然后他告訴這個年青人繼續(xù)好好干，在下個星期他將再次會見他。472011春夏學期授課版軟件項目常見的錯誤他的老板給了他一些手冊和對系統(tǒng)軟件項目常見的錯誤一個星期后，老板把年青人叫到了辦公室，問“我們的進展如何？”“很順利”，年青人說“但是我遇到了一些小難題，我將解決它們并且很快就能保持進度”“那么，最終日期能保證嗎？”老板問?！皼]問題,”工程師說，“我已經(jīng)快完成90％了?！比绻阍谲浖绻ぷ髁藥啄辏憧梢酝瓿蛇@個故事。毫不驚奇，年青人在項目的90％處停滯不前，直到在別人的幫助下在一個月后完成了項目。482011春夏學期授課版軟件項目常見的錯誤一個星期后，老板把年青人叫到了辦公Q&A492011春夏學期授課版Q&A492011春夏學期授課版ProjectManagementChap.1Introduction-概述502011春夏學期授課版ProjectManagementChap.1IntroAgenda-本章需要解決的問題WhyneedProjectManagement？PM&SoftwarecharacteristicsProblemsinSWdevelopmentandSPMChallengeofSWdevelopment512011春夏學期授課版Agenda-本章需要解決的問題WhyneedProje現(xiàn)代管理的三個熱點：戰(zhàn)略管理項目管理運作管理就一個組織的管理而言，應該包括三個部分。1.戰(zhàn)略管理：從宏觀上明確和把握發(fā)展方向2.運作管理：對日常的、重復性工作的管理3.項目管理：對一次性的、創(chuàng)新性工作的管理由于項目管理的效率高、反映靈敏，所以運用的企業(yè)更多。522011春夏學期授課版現(xiàn)代管理的三個熱點：戰(zhàn)略管理項目管理運作管理就一個組Moredregsprojectofbeancurd？Illogicalobjective（時間）jerry-build（成本）Subcontract（手續(xù)）Notrefundloan？RiskManagement(風險)MoreUnsuccessfulinfoingproject？Backbonejob-hopping，manpoweralteration(人力資源)Requirementschanged（范圍）Why？532011春夏學期授課版MoredregsprojectofbeancurIn21st,everythingisproject,orisbecomingProject…PaulGracePresidentofPMIProfessionalscertificationcommittee542011春夏學期授課版In21st,everythingisprojectImportant2jobsforfuturesTechniquesinnovation技術革新的典范-優(yōu)選法Projectmanagement沒有項目管理就沒有現(xiàn)代產(chǎn)業(yè)HuaLuogeng華羅庚552011春夏學期授課版Important2jobsforfuturesTe46%26%28%SuccessUSStandishGroup,對1999年當年軟件項目的統(tǒng)計failingStatisticsofSuccessandfailingforITProject有問題的項目Overbudget,overtimeEtc.562011春夏學期授課版46%26%28%SuccessUSStandishGrPMHistory項目管理，遠自幾千年前的人類文明，近如現(xiàn)代工業(yè)領域。例如GreatWallofChina,EgyptianPyramids(金字塔)

航空航天工程項目and建筑工程項目572011春夏學期授課版PMHistory項目管理，遠自幾千年前的人類文明HistoryofProjectManagementModernprojectmanagementbeganwiththeManhattanProject,whichtheU.S.militaryledtodeveloptheatomicbombIn1917HenryGanttdevelopedtheGanttchartasatoolforschedulingworkinjobshopsIn1958,theNavydevelopedPERTchartsInthe1970s,themilitarybeganusingprojectmanagementsoftware,asdidtheconstructionindustryBythe1990s,virtuallyeveryindustrywasusingsomeformofprojectmanagement1985:TQM1990-93:Re-engineering,self-directedteams1996-99:Riskmgmt,projectoffices2000:M&A,globalprojects582011春夏學期授課版HistoryofProjectManagementMPMdevelopmentCPM,PERTNowPMapplicationsismoreandmorePeoples,customer-oriented,softmanagement592011春夏學期授課版PMdevelopmentCPM,PERT102011春ProjectManagementKnowledgeContinuestoGrowandMaturePMIlaunchedtheirCenterforPMKnowledgeandWisdominDecember2001PMIhostedtheirfirstresearchconferenceinJune2000inParis,France,secondoneinJuly2002ThePMBOKGuide–2000EditionisanANSIstandard,andPMI’scertificationdepartmentearnedISO9000certificationHundredsofnewbooks,articles,andpresentationsrelatedtoprojectmanagementhavebeenwritteninrecentyears602011春夏學期授課版ProjectManagementKnowledgeCHowProjectManagement(PM)RelatestoOtherDisciplinesMuchoftheknowledgeneededtomanageprojectsisuniquetoPMHowever,projectmanagersmustalsohaveknowledgeandexperienceingeneralmanagementtheapplicationareaoftheprojectProjectmanagersmustfocusonmeetingspecificprojectobjectives612011春夏學期授課版HowProjectManagement(PM)RePMTripleConstraint每一個項目都會受到范圍目標、時間目標和成本目標的約束這三個目標又經(jīng)常存在沖突，一個合格的項目經(jīng)理，其責任之一就是平衡三者的關系在此過程中，由于項目的不確定性和資源使用的競爭性，平衡往往成為權衡因此，成功的項目管理，就意味著同時實現(xiàn)范圍、時間和成本三個目標，并讓項目利益相關者滿意！622011春夏學期授課版PMTripleConstraint每一個項目都會受到范Inwhatwaysdomodernprojectsdifferfromancientprojects?現(xiàn)代人們對項目及其管理有一些什么樣的認識和做法？632011春夏學期授課版InwhatwaysdomodernprojectProjectsmaybeunderaFunctionalOrganizationMatrixOrganizationProjectOrganization642011春夏學期授課版ProjectsmaybeunderaFunctioFivefunctionsofthePMPlanningOrganizingLeadershipControlChange652011春夏學期授課版FivefunctionsofthePMPlannClassicalApproachAssumesthereisauniversalsetofmanagementprinciples采用公認的管理原則BehavioralApproach:emphasisonhumanaspects強調(diào)人性化SystemApproach采用系統(tǒng)論的方法662011春夏學期授課版ClassicalApproachAssumestherSoftwareneedsmanagement672011春夏學期授課版Softwareneedsmanagement18201SoftwareneedsmanagementSoftwarecharacteristics特性CostStructure成本IndustrialProblems產(chǎn)業(yè)SoftwareDisaster危機ProblemsinSoftwareTechniques技術進步PositioninSEKnowledgestructure知識結構682011春夏學期授課版SoftwareneedsmanagementSoftwSoftwarecharacteristicsEssentials:logicelements,notentitativeelements.

DevelopingSoftware，andproducingproduct.NowearandtearinusingtimeFailingprobabilityTubcurveofproduct692011春夏學期授課版SoftwarecharacteristicsEssentSoftwarecharacteristics(cont.)timeFailingprobability不愿看到的realcurveofSD期望的IdealcurveofSD702011春夏學期授課版Softwarecharacteristics(cont.Softwarecharacteristics(cont.)Production:Standardization&assembleMassSW:customizationScientificarithmeticfunctionlib(1960’s）DatastructurereusingReusingcomponents人們設法改進軟件開發(fā)的過程。712011春夏學期授課版Softwarecharacteristics(contCostStructureischangedOne-offCostofmanufactureLogicproduct—minimediacostisignoredIcessMoreMaintaincostserviceisquality解決軟件危機本來就是為了回答兩個問題：如何高效率的開發(fā)軟件如何維護越來越多的軟件722011春夏學期授課版CostStructureischangedOne-oMainproblemsinSWindustryIndustrialscale如何定量度量軟件的規(guī)模？Coretechnique如何發(fā)展核心技術Pirateandillegalcopy如何防止盜版和非法拷貝？732011春夏學期授課版MainproblemsinSWindustryIn為什么會有這樣的問題存在？

發(fā)展策略的缺乏印度我們自己發(fā)展規(guī)則知識決定一切（創(chuàng)新，團隊）頭腦產(chǎn)業(yè)新的管理模式742011春夏學期授課版為什么會有這樣的問題存在？發(fā)展策略的缺乏252011春夏學軟件原因引起的災難NATO，1958，SoftwareDisastersisputforwardMoreandmoreunsuccessfulSWProject:NASA,1999-10,Marsweathersatellitelost.US$125million.1963-1966,IBM360OS(1000Bug/Rel.)752011春夏學期授課版軟件原因引起的災難NATO，1958，SoftwareD軟件原因引起的災難(Cont.)Somedata：BeyondSWtimedeadline:about70％SWProject.Beyond20%-50%planningrel.timeinBigProjectBeyondSWcost：90％SWProject.Biggertheprojectis，morecosttospendAuditBureauUS:usablecontractSWisonly2％98％isunsuccessful762011春夏學期授課版軟件原因引起的災難(Cont.)Somedata：2720SoftwareDisasters(Cont.)CrunchModeDeathMarch772011春夏學期授課版SoftwareDisasters(Cont.)CrunSoftwareDisasters(Cont.)chronicafflictionSuggestedbyProf.DanielTiechrow,UniversityofMichigan782011春夏學期授課版SoftwareDisasters(Cont.)chro軟件災難的特點SD開發(fā)逾期.SD成本超過預算.SQA質(zhì)量沒有保證.792011春夏學期授課版軟件災難的特點SD開發(fā)逾期.302011春夏學期授課版規(guī)模、成本、進度、質(zhì)量等的定量度量復雜性控制提高生產(chǎn)效率ProblemsinSWtechnique802011春夏學期授課版規(guī)模、成本、進度、質(zhì)量等的定量度量ProblemsinSExchange2000Windows2000PM25About250Dev.140About1700Test350About3200e.g.:?Windows95have10,000,000linecode

?Windows2000have50,000,000linecodemore3000engineersand100+teamsExchange2000和Windows2000DevOrg.structure812011春夏學期授課版Exchange2000Windows2000PM25Abtypeofproject822011春夏學期授課版typeofproject332011春夏學期授課版typeofproject規(guī)模(big,middle,mini)復雜度

產(chǎn)品/服務

應用

用戶832011春夏學期授課版typeofproject規(guī)模(big,middlPMinSWEBOK《SWEBOK》GuidetotheSoftwareEngineeringBodyofKnowledge842011春夏學期授課版PMinSWEBOK《SWEBOK》352011春夏學

ContentsSoftware&SESPMSystemengineeringRequirementanalysisData-process-orientedanalysisOORAData-OrientedSoftwareDesignData-process-orientedDesignOODUIProgramandcodingSoftwareTestingmantainanceConfigurationmanagementReuseTech.RPCASENewTech.forSWD852011春夏學期授課版ContentsSoftware&SEUI362011ChallengeinSWdevelopment

軟件發(fā)展挑戰(zhàn)Deadlines期限(85%)Resourceconstrained需求扭曲（83％）Communicationswithteams通信消耗（80％）Commitmentfromteam團隊承諾（74％）Makemilestone里程碑（90％）Change變更（60％）Planningagreeforteams計劃符合性（57％）Topcommitment最終義務（45％）Conflict沖突（42％）,subcontract轉(zhuǎn)包（38％）862011春夏學期授課版ChallengeinSWdevelopment

軟件ChallengeforPMProjectmanager：EstimationandPlanning預算和計劃Qualitystd.andmatrix品質(zhì)Guidefororganizationstrategies組織策略Techniquesofvisualizingtheprocess過程技術Roledefinition角色分配Ruleforsuccess成功規(guī)則NoSTD.沒有標準872011春夏學期授課版ChallengeforPMProjectmanageChallengeforteammembersTeammembers：Incorrectworkingdescriptions不恰當