微軟產(chǎn)品開發(fā)管理

1、微軟產(chǎn)品開發(fā)管理 微軟（中國）Microsoft Solution FrameworkAgendaThe development teamThe development environmentThe development processThe development managementThe development teamThe organization chartThe roles Dev manager Own implementation of the product Overall design, keep the project on course, monitor the h

2、ealth, coordinate with other functional teams Dev leads Own features requirement, design, implementation, coordinate architectural issues with leads of other dev team Devs Own implementation of features Implement, test and document features, fix bugs, support QA and UEThe virtual teamsThe architectu

3、re design teamThe performance teamThe code review teamEtc.The development environmentThe principle A standard environmentEverybody use the same environmentMandatoryProductivityPredictabilityFew exceptionsE.g., source editorThe development toolsSource code management system Crucial for protecting com

4、pany asset Crucial for parallel development Support versioning, branching, locking, backup and restore Facilitate automatic build process Integrate with other dev toolsThe development toolsSource code management systemThe project repository Put all project related files and docs into the source code

5、 management systemSource filesCompiler, linker, libraries, build scriptsInstallation tools and scriptsTesting tools and scriptsProject specs, plans, user docs Appoint owner/admin for the systemThe development toolsIssue tracking system All bugs and issues are logged Required fields Title, descriptio

6、n, change history Owner Open date, update date, close date Opened by, changed by, fixed by, closed by Status Priority Severity Fix by Milestone The build number when the bug is found The build number when the bug is fixedThe development toolsIssue tracking systemUse common queries for the teamFor th

7、e dev manager and dev leadsBug open rates and close ratesBug change ratesBug fix failed countsCost to Fix a BugThe development toolsOther tools Modeling tool Debugger Performance analysis tools Coverage analysis tools Team websites Etc.Demo: Performance Profiling The development processThe principle

8、 -A standard process Everybody follows the same procedure Mandatory Productivity Predictability No exceptionsA standard development process Design specs Coding standards Source code check-in procedures Bug fixing procedures Contingency procedures Build breaks Security breathThe development managemen

9、tThe principle -A risk management approach The goal: Build to spec on time The risk: People: Customers, personnel, organization, skills Process Mission, budget, cost, schedule, design, build, test Technology Security, dev and test environment, tools, availability Environment Competition, economic, r

10、egulation, legalRetired RisksRisk Assessment DocumentTop 103. Plan 5. Control2. Analyze1. IdentifyRiskStatements4. TrackRisk Management ProcessThe ongoing deliverable of this process is a living risk assessment documentResearch, evaluation and prototyping Research projects during minor releases Mark

11、et trends and advances Competitor innovations and directions Evaluate technologies Capability, quality, sophistication Ease of use Team skills Prototype Identify key risks Define experiments Simulate end resultScheduling Balance among resource, feature set and schedule Define tasks and estimates Par

12、allel development Schedule commitment Schedule ownership Credibility/PredictabilityProject ExecutionMeasuring and monitoring progress Daily builds and smoke tests The heartbeat of your project Crucial to maintain project consistency, integration, quality and visibility Tracing bugs Weekly bug status

13、 report Bug threshold Status meetings Have a specific purpose Involve PM, QA, and UE Keep it short and frequent Keep a list of outstanding issuesProject ExecutionMeasuring and monitoring progress Managing by walking around (MBWA) Shows you are involved and care about the project Some people not comf

14、ortable speaking at meetings Regular one-on-one with team members Sharing information Share success Share failureProject ExecutionMaking changesChanging CourseGet the facts, but dont overanalyzeInvolves others in the discussionUse external teams to augment dev and testCut features instead of extendi

15、ng scheduleProject ExecutionMaking changes Changing Speed When to increase pressure To meet milestones To recover from a missed date To response to external competitive pressure How to increase pressure Duration be clear how long overtime will last Comfort make overtime enjoyable Spirit team commitm

16、ent Progress show the team the progress Appreciation recognize teams effortBeta TestingBenefits Test in real world Feedback (features, performance, UI) Marketing Augmenting your stuffBeta Testing Management Recruiting beta sites Distribute software Communicate beta status Results-oriented Reward beta sites Start early! Get the feedback! Build a good tool to manage informationPostmortems Formalize the process of learning from past experience Post-milestone review meetings Capture project learning to develop