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

1、微軟產(chǎn)品開發(fā)管理微軟（中國）微軟產(chǎn)品開發(fā)管理microsoft solution framework微軟產(chǎn)品開發(fā)管理agenda the development team the development environment the development process the development management微軟產(chǎn)品開發(fā)管理the development team微軟產(chǎn)品開發(fā)管理the organization chart微軟產(chǎn)品開發(fā)管理the roles dev manager own implementation of the product overall design

2、, keep the project on course, monitor the health, 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, suppo

3、rt qa and ue微軟產(chǎn)品開發(fā)管理the virtual teams the architecture design team the performance team the code review team etc.微軟產(chǎn)品開發(fā)管理the development environment微軟產(chǎn)品開發(fā)管理the principle a standard environment everybody use the same environment mandatory productivity predictability few exceptions e.g., source editor

4、微軟產(chǎn)品開發(fā)管理the development toolssource code management system crucial for protecting company asset crucial for parallel development support versioning, branching, locking, backup and restore facilitate automatic build process integrate with other dev tools微軟產(chǎn)品開發(fā)管理the development toolssource code manage

5、ment system the project repository put all project related files and docs into the source code management system source files compiler, linker, libraries, build scripts installation tools and scripts testing tools and scripts project specs, plans, user docs appoint owner/admin for the system微軟產(chǎn)品開發(fā)管理

6、the development toolsissue tracking system all bugs and issues are logged required fields title, description, 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

7、number when the bug is fixed微軟產(chǎn)品開發(fā)管理the development toolsissue tracking system use common queries for the team for the dev manager and dev leads bug open rates and close rates bug change rates bug fix failed counts微軟產(chǎn)品開發(fā)管理cost to fix a bug微軟產(chǎn)品開發(fā)管理the development toolsother tools modeling tool debugg

8、er performance analysis tools coverage analysis tools team websites etc.微軟產(chǎn)品開發(fā)管理demo: performance profiling 微軟產(chǎn)品開發(fā)管理the development process微軟產(chǎn)品開發(fā)管理the principle -a standard process everybody follows the same procedure mandatory productivity predictability no exceptions微軟產(chǎn)品開發(fā)管理a standard development

9、process design specs coding standards source code check-in procedures bug fixing procedures contingency procedures build breaks security breath微軟產(chǎn)品開發(fā)管理the development management微軟產(chǎn)品開發(fā)管理the principle -a risk management approach the goal: build to spec on time the risk: people: customers, personnel, o

10、rganization, skills process mission, budget, cost, schedule, design, build, test technology security, dev and test environment, tools, availability environment competition, economic, regulation, legal微軟產(chǎn)品開發(fā)管理retired risksrisk assessment documenttop 103. plan 5. control2. analyze1. identifyriskstatem

11、ents4. trackrisk management processthe ongoing deliverable of this process is a living risk assessment document微軟產(chǎn)品開發(fā)管理research, evaluation and prototyping research projects during minor releases market trends and advances competitor innovations and directions evaluate technologies capability, quali

12、ty, sophistication ease of use team skills prototype identify key risks define experiments simulate end result微軟產(chǎn)品開發(fā)管理scheduling balance among resource, feature set and schedule define tasks and estimates parallel development schedule commitment schedule ownership credibility/predictability微軟產(chǎn)品開發(fā)管理p

13、roject 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 report bug threshold status meetings have a specific purpose involve pm, qa, and ue

14、 keep it short and frequent keep a list of outstanding issues微軟產(chǎn)品開發(fā)管理project executionmeasuring and monitoring progress managing by walking around (mbwa) shows you are involved and care about the project some people not comfortable speaking at meetings regular one-on-one with team members sharing in

15、formation share success share failure微軟產(chǎn)品開發(fā)管理project executionmaking changes changing course get the facts, but dont overanalyze involves others in the discussion use external teams to augment dev and test cut features instead of extending schedule微軟產(chǎn)品開發(fā)管理project executionmaking changes changing spe

16、ed 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 commitment progress show the team the progress appreciation re

17、cognize teams effort微軟產(chǎn)品開發(fā)管理beta testingbenefits test in real world feedback (features, performance, ui) marketing augmenting your stuff微軟產(chǎn)品開發(fā)管理beta 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 information微軟產(chǎn)品開發(fā)管理postmortems formalize the process of learning from past experience post-milestone review meetings capture project learning to develop team members