微软产品开发管理

1、微软产品开发管理第一页，共三十四页。Microsoft Solution Framework第二页，共三十四页。AgendaThe development teamThe development environmentThe development processThe development management第三页，共三十四页。The development team第四页，共三十四页。The organization chart第五页，共三十四页。The rolesDev managerOwn implementation of the productOverall design, k

2、eep the project on course, monitor the health, coordinate with other functional teamsDev leadsOwn featuresrequirement, design, implementation, coordinate architectural issues with leads of other dev teamDevsOwn implementation of featuresImplement, test and document features, fix bugs, support QA and

3、 UE第六页，共三十四页。The virtual teamsThe architecture design teamThe performance teamThe code review teamEtc.第七页，共三十四页。The development environment第八页，共三十四页。The principle A standard environmentEverybody use the same environmentMandatoryProductivityPredictabilityFew exceptionsE.g., source editor第九页，共三十四页。The

4、 development toolsSource code management systemCrucial for protecting company assetCrucial for parallel developmentSupport versioning, branching, locking, backup and restoreFacilitate automatic build processIntegrate with other dev tools第十页，共三十四页。The development toolsSource code management systemThe

5、 project repository Put all project related files and docs into the source code management systemSource filesCompiler, linker, libraries, build scriptsInstallation tools and scriptsTesting tools and scriptsProject specs, plans, user docs Appoint owner/admin for the system第十一页，共三十四页。The development t

6、oolsIssue tracking systemAll bugs and issues are loggedRequired fieldsTitle, description, change historyOwnerOpen date, update date, close dateOpened by, changed by, fixed by, closed byStatusPrioritySeverityFix by MilestoneThe build number when the bug is foundThe build number when the bug is fixed第

7、十二页，共三十四页。The development toolsIssue tracking systemUse common queries for the teamFor the dev manager and dev leadsBug open rates and close ratesBug change ratesBug fix failed counts第十三页，共三十四页。Cost to Fix a Bug第十四页，共三十四页。The development toolsOther toolsModeling toolDebuggerPerformance analysis tool

8、sCoverage analysis toolsTeam websitesEtc.第十五页，共三十四页。Demo: Performance Profiling 第十六页，共三十四页。The development process第十七页，共三十四页。The principle -A standard processEverybody follows the same procedureMandatoryProductivityPredictabilityNo exceptions第十八页，共三十四页。第十九页，共三十四页。A standard development processDesign

9、 specsCoding standardsSource code check-in proceduresBug fixing proceduresContingency proceduresBuild breaksSecurity breath第二十页，共三十四页。The development management第二十一页，共三十四页。The principle -A risk management approachThe goal: Build to spec on timeThe risk:People: Customers, personnel, organization, ski

10、llsProcessMission, budget, cost, schedule, design, build, testTechnologySecurity, dev and test environment, tools, availabilityEnvironmentCompetition, economic, regulation, legal第二十二页，共三十四页。Retired RisksRisk Assessment DocumentTop 103. Plan 5. Control2. Analyze1. IdentifyRiskStatements4. TrackRisk M

11、anagement ProcessThe ongoing deliverable of this process is a living risk assessment document第二十三页，共三十四页。Research, evaluation and prototypingResearch projects during minor releasesMarket trends and advancesCompetitor innovations and directionsEvaluate technologiesCapability, quality, sophisticationE

12、ase of useTeam skillsPrototypeIdentify key risksDefine experimentsSimulate end result第二十四页，共三十四页。SchedulingBalance among resource, feature set and scheduleDefine tasks and estimatesParallel developmentSchedule commitmentSchedule ownershipCredibility/Predictability第二十五页，共三十四页。Project ExecutionMeasuri

13、ng and monitoring progressDaily builds and smoke testsThe heartbeat of your projectCrucial to maintain project consistency, integration, quality and visibilityTracing bugsWeekly bug status reportBug threshold Status meetingsHave a specific purposeInvolve PM, QA, and UE Keep it short and frequentKeep

14、 a list of outstanding issues第二十六页，共三十四页。Project ExecutionMeasuring and monitoring progressManaging by walking around (MBWA)Shows you are involved and care about the projectSome people not comfortable speaking at meetingsRegular one-on-one with team membersSharing informationShare successShare failu

15、re第二十七页，共三十四页。Project ExecutionMaking changesChanging CourseGet the facts, but dont overanalyzeInvolves others in the discussionUse external teams to augment dev and testCut features instead of extending schedule第二十八页，共三十四页。Project ExecutionMaking changesChanging SpeedWhen to increase pressureTo mee

16、t milestonesTo recover from a missed dateTo response to external competitive pressureHow to increase pressureDuration be clear how long overtime will lastComfort make overtime enjoyableSpirit team commitmentProgress show the team the progressAppreciation recognize teams effort第二十九页，共三十四页。Beta Testin

17、gBenefitsTest in real worldFeedback (features, performance, UI)MarketingAugmenting your stuff第三十页，共三十四页。Beta Testing ManagementRecruiting beta sitesDistribute softwareCommunicate beta statusResults-orientedReward beta sitesStart early!Get the feedback!Build a good tool to manage information第三十一页，共三十四页。PostmortemsFormalize the process of learning from past experiencePost-milestone review meetings Capture project learning to develop team members and