工程項(xiàng)目管理英文課件:class6-management functions_第1頁
工程項(xiàng)目管理英文課件:class6-management functions_第2頁
工程項(xiàng)目管理英文課件:class6-management functions_第3頁
工程項(xiàng)目管理英文課件:class6-management functions_第4頁
工程項(xiàng)目管理英文課件:class6-management functions_第5頁
已閱讀5頁,還剩51頁未讀, 繼續(xù)免費(fèi)閱讀

下載本文檔

版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進(jìn)行舉報或認(rèn)領(lǐng)

文檔簡介

ManagementFunctions1ASSIGNMENTSReadChapter11–PlanningQ:11-26,31,36,42,432ManagementFunctionsKerznerhighlightsfortheProjectManager,

“TheManagerialskillsheorsherequiresforsuccessfulperformancemaybedrasticallydifferentfromhisfunctionalmanagercounterpart.”3SOMEREASON’SWHYThePMisresponsiblefororganizationalgoalsandobjectivesMusthaveathoroughknowledgeofstandardsandcostcontrolpoliciesLinemanagershavetheluxurytogettoknowtheiremployees.Theprojectmanagerhasasettimehorizontocompletetheproject.4DIRECTINGItisbettertodecideanissueandbe10percentwrongthanitistowaitforthelast10percentofaproblem’sinputandcauseascheduleddelayandimproperuseofresources.“Paralysisthroughanalysis”DirectivesaremosteffectivewhentheKISS(keepitsimplestupid)ruleisapplied5DIRECTINGNeverissueanorderyoucannotenforce.Putalldirectioninhardcopysothereisnoconfusion.Thisisespeciallyimportantwhendealingwithmultiplenativelanguages.Therequestorshouldaskthereceivertorepeatthedirection.6EmployeeMotivationTheoryXandYTheoryZMaslow’sHierarchyHerzborgExpectancyTheory7TheoryXandYIn1960,DouglasMcGregoradvocatedallemployeescouldbegroupedintotwocategories,XandY.TheoryXassumesemployeesareinherentlylazyandrequiresupervision.TheydislikeworkandrequirecontinuoussupervisionTheoryYassumesemployeesselfmotivatedanddonotrequiresupervision8TheoryXandYIn1978WilliamOuchiproposedtherewasatheoryZwhichdescribedtheJapaneseworkculture.FocusonlifetimeemploymentFocusoncollectivedecisionmakingFavorinformaladministrativecontrolPlaceworkersonnonspecializedcareerpaths9TheoryXandYISTHEREACHINESEWORKERCULTUREORDOTHEYFITINTOONEOFTHEEXISTINGTHEORIES?10Maslow’sHeirarchy(1954)SELF-ESTEEMSELF-ACTUALIZATIONSOCIAL/BELONGINGSAFETYPHYSIOLOGICAL11ManagementFunctionsIn1959,HerzborgproposedthelowerthreelevelsofMaslow’sHierarchyarehygienefactors.Onlythetoptwoitemsaremotivators.Lastly,ChrisArgyisdevelopedhisExpectancyTheorywhichsayswhentheneedsoftheorganizationandtheindividualarealignedbothpartiesbenefitsandmotivationincrease.12EmployeeMotivationKerznerhasanextensivelistofwaystomotivateonPages229&230MyExperience:AdoptapositiveattitudeDonotcriticizemanagementCirculatecustomerreportsClearcommunicationofprojectobjectivesDevelopateamattitudeRecognizeoftenindividualperformance13ProjectAuthorityAuthoritycanbedelegatedfromsuperiors.Powerisgrantedbysubordinatesandreflectstheirrespectforhimorher.Aprojectmanagerwhofailstomaintainhisorherallianceswillsoonfindoppositionandindifferencetohisorherprojectobjectives.14ProjectAuthorityAProjectManager’sauthorityshouldbegreaterthanhisresponsibilitycallsforandusuallydependsonthelevelofrisk.TheProjectManagerdoesnothaveunilateralauthorityandmustnegotiatewiththefunctionalmanagers.TheProjectManagerdeterminesthe“when”and“what”oftheprojectwhilethefunctionalmanagerdefines“How”.15GroundRulesExistForAuthorityControlNegotiationsshouldtakeplaceatthelowestlevelofinteraction.DefinitionoftheproblemmustbethefirstpriorityTheissueTheimpactThealternativeTherecommendationsHigherlevelauthorityshouldbeusedif,andonlyif,agreementcannotbereached.16LinearResponsibilityChartsExamples-Kerznerpages233-235MaybeusedtocommunicateResponsibilityforvariousProjectrequirementsCommunicationresponsibilityDatadistributionauthoritySpendingauthorityDesignApprovalauthoritySkills17ProjectCharterThebestwaytocommunicateaProjectManager’sauthorityisina“ProjectCharter”AProjectCharterdefineshisrolerelativeto:ConflictsbetweenfunctionalmanagersandthePMControloverprojectfundsCollaborationinstaffingtheprojectSelectionofsubcontractorsEstablishmentofprojectplansPrimecustomerliaisonandcontactEstablishingaprojectorganization18InterpersonalInfluencesProjectManagershavedelegatedauthoritybutlimitedformalpower.Theymustgetthejobdonebytheirinterpersonalinfluences.Legitimatepower–empoweredtoissueordersRewardpower–perceivedtobeabletorewardPenaltypower–perceivedtobeabletoissuepenaltiesExpertpower–PMprocessesspecialexpertiseReferentpower–personnelareattractedtothePM19BarrierstoProjectTeamDevelopmentDifferingoutlooks,prioritiesandinterestsRoleconflictsProjectobjectivesunclearDynamicprojectenvironmentCompetitionoverteamleadershipLackofteamdefinitionandstructure20BarrierstoProjectteamDevelopmentTeampersonnelselectionCredibilityofprojectmanagerLackofteammembercommitmentCommunicationproblemsLackofseniormanagementsupport21FiveMostCommonDysfunctionsofaTeamPatrickLencionihasidentifiedthefivemostcommondysfunctionsofateam.AbsenceoftrustFearofconflictLackofcommitmentAvoidanceofaccountabilityInattentiontoresults22Value-BasedProjectLeadershipToday,companiesarelookingforwaystoalignemployeespersonalvalueswiththeorganizationvalues.ProjectManagementismovingawayfromineffectivevaluestoeffectivevalues23IneffectiveValuesMistrustJobDescriptionsPowerandauthorityInternalfocusSecurityConformityPredictabilityInternalcompetitionReactivemgmt.BeauracracyTraditionalEd.HierarchicalleadershipTacticalthinkingComplianceMeetingstandards24EffectiveValuesTrustCompetencymodelsTeamworkStakeholderfocusTakingrisksInnovationFlexibilityInternalcollaborationsProactivemgmt.BoundarylessLifelongeducationMultidirectionalleadershipStrategicthinkingCommitmentContinuousimprovements25Functional/ProjectManagerConflictsConflictswillexistnomatterhowhardwestructurethework.ProjectManagerWhatistobedoneWhenwillthetaskbedoneWhywillthetaskbedoneHowmuchmoneyisavailabletodothetaskHowwellhasthetotalprojectbeendone.26Functional/ProjectManagerConflictsFunctionalManagerWhowilldothetaskWherewillthetaskbedoneHowwillthetaskbedoneHowwellhasthefunctionalinputbeenintegratedintotheproject27Functional/ProjectManagerConflictsTheconflictsrevolvearoundsuchitemsasprojectpriority,manpowercosts,andtheassignmentoffunctionalpersonneltotheprojectmanager.28GoodandPoorProjectManagersContributionsfromPeopleGood–Encouragesactivecooperationandresponsibleparticipation.Theresultisthatbothgoodandbadinformationiscontributedfreely.Poor–maintainsanatmosphereofpassiveresistancewithonlyresponsiveparticipation.Thisresultsininformationbeingwithheld.29GoodandPoorProjectManagersOrganizationalOrderGood–Developspolicyandencouragesacceptance.Poor–Goesbeyondpoliciesandattemptstodevelopproceduresandmeasurements.30GoodandPoorProjectManagersEmployeePerformanceGood–Keepspeopleinformedandsatisfiedbyaligningmotiveswithobjectives.Positivethinkingandcooperationareencouraged.AgoodPMiswillingtogivemoreresponsibilitytothosewillingtoacceptit.Poor-keepspeopleuninformed,frustrated,defensive,andnegative.Motivesarealignedwithincentivesratherthanobjectives.Developsa“stayoutoftroubleatmosphere”31GoodandPoorProjectManagersProjectManagerPerformanceGood–Assumesthatemployeemisunderstandingscanandwilloccur,andthereforeblameshimorherself.Constantlyattemptstoimproveandbemorecommunicative.Heorshereliesonmoralpersuasion.Itistherightthingtodo.Poor–Assumesthatemployeesareunwillingtocooperateandthereforeblamessubordinates.Demandsmorethroughauthoritarianattitudesandreliesheavilyonmaterialincentives.32GoodandPoorProjectManagersManagementProblem-SolvingGood–Performshisownproblem-solvingatthelevelforwhichheorsheisresponsiblethroughdelegationofproblemsolvingresponsibilities.Poor–Willdosubordinateproblem-solvinginknownareas.Forareasheorshedonotknow,theywillrequiretheirapprovalbeforeimplementing33GoodandPoorProjectManagersOrganizationalOrderGood–develops,maintainsandusesasingleintegratedmanagementsysteminwhichauthorityandresponsibilityaredelegatedtothesubordinates.Heorsheknowsthatoccasionalslippagesandoverrunswilloccurandimplytriestominimizetheireffect.Poor–delegatesaslittleauthorityandresponsibilityaspossibleandrunstheriskofcontinualslipagesandoverruns.34GoodandPoorProjectManagersPerformanceofPeopleGood–Findsthatsubordinateswillinglyacceptresponsibility,aredecisiveinattitudetowardtheproject,andaresatisfied.Poor–Findsthathisorhersubordinatesarereluctanttoacceptresponsibility,areindecisiveintheiractionsandseemfrustrated.35GoodandPoorProjectManagersPerformanceoftheProjectManagerGood–Assumesthathisorherkeypeople“canruntheshow”Heorsheexhibitsconfidenceinthoseindividualsworkinginareasinwhichheorshehavenoexpertiseandexhibitspatiencewithpeopleworkinginareaswhereheorsheisfamiliar.Heorsheisnevertoobusytohelphisorherpeoplesolveapersonalorprofessionalproblem.Poor–Considershimorherselfindispensable,isovercautiouswithworkperformedinunfamiliarareasandisoverlyinterestedinworkheorsheknows.Heorsheisalwaystiedupinmeetings.36ManagementPitfallsLackofself-control(knowingoneself)ActivitytrapsManagingversusdoingPeopleversustaskskillsIneffectivecommunicationTimemanagementManagementbottlenecks37COMMUNICATION38COMMUNICATIONUpwardCommunicationToManagementProjectManagerLateralCommunicationToPeers,FunctionalGroups&CustomersLateralCommunicationToFriends,SocialGroups&OrganizationsDownwardCommunicationToSubordinates&ProjectOffice39ProvidingProj.DirectionDecision-MakingAuthorizingworkDirectingActivitiesNegotiatingReporting/BriefingsAttendingMeetingsOverallProjectManagementMarketingandSellingPublicrelationsRecordsManagementMinutesMemos/Letters/NewslettersReportsSpecificationsContractsCOMMUNICATIONREQUIREMENTS

ThePMspends90%0fhis/hertimecommunicating40TeamMeetingsEstablishasettimeforallmeetingsandinsuretheyareoneveryone’sagendaStartontimeBein-chargeInsureconferencecallsareestablishedbeforethemeetingstarttime.DevelopanagendaforeachmeetingConductonepieceofbusinessatatimeAlloweachmembertocontributeandinsureeveryonespeaks41TeamMeetingsBereadytoconfronttheverbalmemberTestforreadinesstomakeadecisionMakeadecisionTestforcommitmenttothedecisionAssignrolesandresponsibilitiesAgreeonfollow-upandaccountabilitydatesIndicatenextstepsMaintainastatusofopenassignmentsandrevieweachmeetingPublishminutesofthemeeting42Cross-CuttingSkillsActivelisteningBrainstormingIdeasCommunicationConflictResolutionCulturalsensitivityData-gatheringFacilitationskillsInfo.ManagementLeadershipMotivationskillsNegotiatingPresentationskillsPrioritizationskillsProblemsolvingRelationshipskillsStakeholderident.&impactanalysis43ActiveListeningActivelisteningisastructuredwayoflisteningbyfocusingonthespeaker,theirwordandbodylanguage.Suspendingone’sownframeofreference,suspendingjudgmentandavoidingotherinternalmentalactivities.Besensitivetobarrierstolisteningwhetherthesourceofthebarriersarethelistenerorspeaker.44ProjectProblem-SolvingProblemsolvinganddecisionmakinggohandinhand.Problemsolvinginvolvesunderstandingtheproblem,gatheringthefactsanddevelopingalternatives.Decisionsaremadewhenweselecttheappropriatealternative.45ProjectProblem-SolvingIndividualsorteamsmaynothighlightaproblemandtrytosolveitquietly.DatagatheringtechniquesareshownonKerzner,pages282-283Someproblemsarenotalwaysrealorrequiretheprojectmanagertomakeadecision.Usually,aproblemresolutionrequiresameeting.46Problem-SolvingMeetingsAlwaysissueanagendaInvitesubjectmatterexpertsInviteareasimpactedbythedecisionInvitedecisionmakersTheProjectManagermustbeabletoobtaintheresourcestosolvetheproblem.Alternativesmustbeassessedastoimpactonprojectobjectives47BrainstormingFocusonquantityWithholdcriticismWelcomeunusualideasCombineandimproveideas48ProjectDecision-MakingDecisionProcessAlternativesMajorityorconsensusQualifiedmajorityorconsensusProjectmanagerdirectedClientdirected49DecisionMakingLeadershipStylesTheautocraticdecision-makerThefearfuldecision-makerThecirculardecision-makerThedemocraticdecision-makerTheself-servingdecision-maker50SelectedProverbsThemostvaluable&leastusedwordinaPM’svocabularyis“NO”Theconditionsattachedtoapromiseareforgotten,andthepromiseisremembered.Itisoktostrivetoexceedbut“Donotbeahero”NeverunderestimatethepowerofafocusedteamWhatisnotonpaper,hasnotbeensaid.51SelectedProverbsAlwaysthinkwhyaquestionwasaskedbeforeanswering.Whenmanagementasksi

溫馨提示

  • 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 人人文庫網(wǎng)僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負(fù)責(zé)。
  • 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時也不承擔(dān)用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。

評論

0/150

提交評論