(精品)运筹帷幄——微软程序经理.ppt

上传人:gsy****95 文档编号:84313184 上传时间:2023-04-04 格式:PPT 页数:37 大小:424.50KB
返回 下载 相关 举报
(精品)运筹帷幄——微软程序经理.ppt_第1页
第1页 / 共37页
(精品)运筹帷幄——微软程序经理.ppt_第2页
第2页 / 共37页
点击查看更多>>
资源描述

《(精品)运筹帷幄——微软程序经理.ppt》由会员分享,可在线阅读,更多相关《(精品)运筹帷幄——微软程序经理.ppt(37页珍藏版)》请在taowenge.com淘文阁网|工程机械CAD图纸|机械工程制图|CAD装配图下载|SolidWorks_CaTia_CAD_UG_PROE_设计图分享下载上搜索。

1、 PROGRAM MANAGEMENT PROGRAM MANAGEMENT IN MICROSOFT IN MICROSOFT Jeff Xiong Microsoft Corporation All rights reserved by Jeff XiongWho I AmProgram Manager at Microsoft:2002 MSN 82001 MSN Search2000 Windows Me1999 Windows 2000 1997 Internet Explorer 4.0,5.01996 Java VM,Internet Explorer 3.0Staff Prog

2、rammer at IBM:1995 InfoSage,IBM Internet Division in NYAgenda1.PM Introduction2.PM Role in Project Lifecycles3.PM Strategies1.Program Manager IntroductionWhats Program Manager?One of three major job disciplines in MS software product group.Complete responsibility for delivering the right products to

3、 the right customers with high quality and on time.Direct extension of General Management.All the responsibility but no authority.Product Unit Report StructureProduct Unit ManagerGroup PMDev ManagerTest ManagerPM LeadPMDev LeadDevTest LeadTesterProject Team Working StructureDeveloper LeadDeveloperDe

4、veloperDeveloperDeveloperTester LeadTester Tester Tester Tester Product ManagerProgram ManagerUser EducationUsability EngineerDesignerHistory of Program ManagerJabe Blumenthal Multiplan,1984,Supported by BillG,and formalizedToday:5000 PMs(50,000 employees)Unique job description at Microsoft in the S

5、oftware Industry.Fuzzy requirements:No degrees in PMPM doesnt write code!Software Product CodeMarketing and business modelProduct design and specificationMilestones,schedulesStatus meetings,bug trackingTesting effortInternationalization and LocalizationUser documentation,education and training Produ

6、ct supportWhy do we need PMSoftware projects get much largerTeams need a leader that has breadth and vision,determined to drive product from idea to delivery Developers and testers need buffer to focus on coding and testing.Different groups of people need to communicate effectively Program Manager T

7、o-DosSolely responsible for the shipping of the product.Have the products vision,write project specification.Drive work item list,keep track based on specs.Organize meetings and triage bugs.Keep track of the project schedule.Guide the project development process.Decide all implementation trade-offs.

8、Coordinate and communicate with all groups of people.PM is a leader,facilitator,and coordinator.Project Manager vs.Program ManagerOne person vs.a group of peopleManage people vs.manage projectGiven authority vs.earned authorityWrite project plan vs.write design spec2.Program Manager Roles in Project

9、 LifecyclesProject Process LifecyclePlanning phaseDevelopment phaseStabilization phaseRelease phasePostmortemStart next version cycle.PM in Planning PhasePrepare project plan draft(vision statement,high level features,proposed schedule and milestone,resource estimate).Brainstorm with team members an

10、d finalize feature set.Write one-page spec(prioritized feature sets,resource estimates,schedule estimates,risk estimates)Write detailed design specifications.PM in Development PhaseReview developers technical implementation design,testing plan and test cases.Host meeting to go through all work items

11、,assign tasks and finalize schedules.Define and enforce processes for build,check-in,and bug triage.Setup team meeting schedule,drive meetings and track working itemsMaintain team web site and team aliasPM in Stabilization PhaseTriage daily to monitor and assign bugs promptly.Drive Code Complete and

12、 UI freeze dates.Make feature and trade off decisions,enforce DCR(Design Change Request)process.Communicate to UE,Localization,Legal.Manage internal and external beta releasesPM in Release PhaseDrive Zero Bug Date and Release Candidates.Conduct War meeting to review bugs everyday.Decide on showstopp

13、er issues.Push testing to run final testing pass and sign off.Sign off and send announcement.Host a ship party!PM in PostmortemOrganize postmortem project team meeting Prepare documents to retract good and bad things happened in the project lifecycle.Decide on future improvement areas.List action it

14、ems for each team or person,follow up through next release cycle.3.Program Manager StrategiesPM Core Competences-IQCoding skillsArchitectural designUser-study techniquesUser interface designAPI and Schema Interface designCommunication skills,written and oral,formal and informalPresentation skillsFin

15、ancial acumenKnowledge of basic business,contract,patent,and copyright lawMarket research techniquesKnowledge of competitorsCan learn and use any software in no time flatPM Core Competences-EQRaw IntelligenceLeadershipSelf-awarenessContract and business negotiationUser EmpathySensitivity to Confiden

16、tial informationInterpersonal skillsSchedule and Project ManagementTime ManagementOrganizational skillsTeam dynamicsGroup psychologyAbility to manage other disciplinesRecruiting,interviewing,and hiringWho can be Program ManagerPassionate about producing software product,who can lead and feels owners

17、hip.Have a strong interest in design issues and is sharp in understanding technical issuesHave a keen sense of timing and schedule,able to track and prioritize complicated tasksAlways find ways to walk around a problem by himself or making other people help.Able to make a decision quickly and confid

18、ently,willing to make trade-offs.PMs Core MindsetsCommunication,Leadership and Relationship CommunicationRelationshipLeadershipPM Communication MethodsEmailsStatus reportsSpec reviewsMeeting schedules and minutesCheck-in emailbug reportGeneral Q&AMeetingsBug triageTeam meetingSpec reviewWar meetingP

19、resentationTeam websitesDirect contacts Communication Strategies:EmailsUse it!Be responsive,reply questions of concern swiftly.Be inclusive,email should reach everyone that of interestKeep your team well informed,no surprises spec drafts,key changes things that might effect peoples plansAction item

20、expectations for recipientsDocument meeting conclusions and important conversationsCommunication Strategies:MeetingsBe exclusive,only include people who are necessarySetup clear goals and agendas beforehand Listen with deep,genuine attention.Tune in to both words said and emotions underneathGuide im

21、pulsive feelings toward deeper inquiry and dialogue.Get to the heart of the problem,spot and stop deviations along the wayUse entrainment to control heated discussionsWrite meeting minutes to recap progress and expectations PMs Leadership AspectsSolely responsible for the shipping of the product Hav

22、e products vision,inspire commitment in team membersMake decisions on features and trade-offsSchedule and drive team meetingsPrioritize tasks,assign work items and set expectationsDecide milestones and drive schedulesPrepare and avoid disasterLeadership Strategies:Earned powerInspire team with visio

23、n,passion and commitmentEarn respect by listening to team members and making sound decisionsEarn trust not necessarily by telling people what to do,but by convincing people through reasonBe dependable and accountable in tough situationsLeadership Strategies:Making DecisionsYou own project only means

24、 you are responsible,dont expect everything your wayVoting is not deciding,its absolving yourself of management responsibilityGood decisions leave many unhappy.Tips:Have courage:know when to be a leaderKeep mind open for debates,gather all related factsApply best judgmentWork for support of key play

25、ersWork for rough consensusPersuade or manage everyone elseLeadership Strategies:Pushing ReleaseCommit yourself first,then expect team commitmentFacilitate needs and clearing roadblocks Set detailed goals and expectations,negotiate beforehand and demand resultsPush for features to finish,not grind t

26、he person.Attitude is keyDemand best from team,but stand for team against unrealistic requests Leadership Strategies:Avoiding DisasterAdmit that disaster is possibleSet expectations around risk propositionsClarify dependencies&risksPrecisely define approach and goals Clearly separate disaster from s

27、uccessPlan to reviewPlan for lookouts What are our measurements?How are we doing?What are the current risks?How are we managing them?Who is responsible for reviewing risk status?PMs relationship networkWork with all kinds of peopleDevelopers,testers,product manager,marketing manager,user education d

28、epartment,web designer,usability engineer,customer,etcCoordinate wide range of people to make project workRelationship Strategies:Working with DevelopmentBe a technical expert,you cant do good design without technical knowledgeTalk to development in their own language.Apply insight to technical deta

29、ils,make sound judgment when development conflicts with business needsKnow each member thoroughly,from technical expertise,characters to potentials,and what makes him/her tickBuild sense of team belongingRelationship Strategies:Working with Anyone How can I get their best work through:InspiringTalki

30、ng&ListeningClearing roadblocksSharing goalsInstructingChallenging/Making demandsHow can this person make my project:Easier to use for customersBe more reliable and higher qualityShip soonerSell more copies(generate more hits)Have better ROIEasier to maintainSatisfy the project goals and objectivesReach division/corporate tactical and strategic goalsConclusionPM is a unique position that drives Microsoft making great products.PM defines and manages project processes through whole lifecycle.PMs core mindsets are Communication,Leadership and Relationship.Q&A

展开阅读全文
相关资源
相关搜索

当前位置:首页 > 生活休闲 > 生活常识

本站为文档C TO C交易模式,本站只提供存储空间、用户上传的文档直接被用户下载,本站只是中间服务平台,本站所有文档下载所得的收益归上传人(含作者)所有。本站仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。若文档所含内容侵犯了您的版权或隐私,请立即通知淘文阁网,我们立即给予删除!客服QQ:136780468 微信:18945177775 电话:18904686070

工信部备案号:黑ICP备15003705号© 2020-2023 www.taowenge.com 淘文阁