Product Cycle Model.ppt

  1. 1、本文档共22页,可阅读全部内容。
  2. 2、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
  3. 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  4. 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
Product Cycle Model

2000-5-15 Microsoft Product Cycle Model Mingyuan Zhang May 2005 Objectives Get to know Microsoft organization (segments, products) Get to know Microsoft product team organization, individual roles Learn concepts of Microsoft Product Cycle Model 知己知彼,利人利己 Agenda Overview and related concepts Planning phase Design phase Implementation phase Stabilization phase Release phase Microsoft Segments Microsoft Departments in China Microsoft China (Sales Marketing) Research Asia (MSRA) Advanced Technology Center (ATC) Global Technical Engineering Center (GTEC) China Technology Center (CTC) Windows China Research Development Center (RD) Office Developer Tools Windows Server System China Test Initiative (CTI) Home Entertainment Chinese Technology MSTV Product Cycle Model and Product Team Roles Program Manager (PM) Developer (SDE) Tester (STE) Localization (SLE/LPM) Release Manager Product Team Org Chart – Sample Glossary IDW/IDS: Internal Develop Workstation / Internal Develop Server RC: Release Candidate, Release Criteria RTM/RTW: Release to Manufacture / Release to Web DCR: Design Change Request BVT: Build Verification Test Dogfood Escrow Check-in Build branch Bug bar Bug bash Showstopper bug: Must fix bugs in major milestones (RC, RTM) Fiscal Year (July – June) / Calendar Year Planning Overview Responsibilities Design Overview Responsibilities Implementation Overview Responsibilities Stabilization Overview Responsibilities Release Overview Responsibilities Questions Exit Criteria What it is A set of statements or conditions When all statements or conditions are set to yes, the project moves to the next phase Why it is important Rule of the game Basis to decide whether task/phase is completed Defined prior to task/phase starts More specific and clear is better Milestones Tradeoff Most important factor Quality driven Schedule driven Feature driven Adjustment Expand the time of develop and test Add more resources Cut features * * Great Plains bCentral Navision Windows Serv

文档评论(0)

af60068 + 关注
实名认证
内容提供者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档