《运筹帷幄微软程序经理培训教材》由会员分享，可在线阅读，更多相关《运筹帷幄微软程序经理培训教材（37页珍藏版）》请在金锄头文库上搜索。
1、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 Programmer at IBM:1995 InfoSage, IBM Internet Division in NYAgenda1
2、.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 the right customers with high quality and on time.Direct e
3、xtension of General Management. All the responsibility but no authority.Product Unit Report StructureProduct Unit ManagerGroup PMDev ManagerTest ManagerPM LeadPMDev LeadDevTest LeadTesterProject Team Working StructureDeveloper LeadDeveloperDeveloperDeveloperDeveloperTester LeadTester Tester Tester T
4、ester 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 Software Industry. Fuzzy requirements: No degrees in P
5、MPM doesnt write code!Software Product CodeMarketing and business modelProduct design and specificationMilestones, schedulesStatus meetings, bug trackingTesting effortInternationalization and LocalizationUser documentation, education and training Product supportWhy do we need PMSoftware projects get
6、 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 effectivelyProgram Manager To-DosSolely responsible for the shipping of the
7、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.Coordinate and communicate with all groups o
8、f 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 LifecyclesProject Process Lifecycle
9、Planning 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 and finalize feature set.Write one
10、-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, assign tasks and finaliz
11、e 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 UI freeze dates.Make
12、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 showstopper issues.Push te
13、sting 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 items for each team
14、 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 skillsFinancial acum
15、enKnowledge 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 Confidential i
16、nformationInterpersonal 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 ownership
17、.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 confiden
18、tly, 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 meeting
19、PresentationTeam 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
20、 item 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 undernea
21、thGuide impulsive 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
22、product Have 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 t
23、eam with vision, 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 p
24、roject only means 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 f
25、or support of key playersWork 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 feat
26、ures to finish, not grind the 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
27、Clearly separate disaster from successPlan 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 manage
28、r, marketing manager, user education department, 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
29、own language. Apply insight to technical details, 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
30、 can I get their best work through:InspiringTalking & 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 ROIEasie
31、r 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
