




版權(quán)說(shuō)明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請(qǐng)進(jìn)行舉報(bào)或認(rèn)領(lǐng)
文檔簡(jiǎn)介
1、微軟產(chǎn)品開(kāi)發(fā)管理The development teamThe development environmentThe development processThe development managementDev managerOwn implementation of the productOverall design, keep the project on course, monitor the health, coordinate with other functional teamsDev leadsOwn featuresrequirement, design, implemen
2、tation, coordinate architectural issues with leads of other dev teamDevsOwn implementation of featuresImplement, test and document features, fix bugs, support QA and UEThe architecture design teamThe performance teamThe code review teamEtc.Everybody use the same environmentMandatoryProductivityPredi
3、ctabilityFew exceptionsE.g., source editorCrucial for protecting company assetCrucial for parallel developmentSupport versioning, branching, locking, backup and restoreFacilitate automatic build processIntegrate with other dev toolsThe project repository Put all project related files and docs into t
4、he source code management systemSource filesCompiler, linker, libraries, build scriptsInstallation tools and scriptsTesting tools and scriptsProject specs, plans, user docs Appoint owner/admin for the systemAll bugs and issues are loggedRequired fieldsTitle, description, change historyOwnerOpen date
5、, 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 fixedUse common queries for the teamFor the dev manager and dev leadsBug open rates and close ratesBug change ratesBug fix f
6、ailed countsModeling toolDebuggerPerformance analysis toolsCoverage analysis toolsTeam websitesEtc.Everybody follows the same procedureMandatoryProductivityPredictabilityNo exceptionsDesign specsCoding standardsSource code check-in proceduresBug fixing proceduresContingency proceduresBuild breaksSec
7、urity breathThe goal: Build to spec on timeThe risk:People: Customers, personnel, organization, skillsProcessMission, budget, cost, schedule, design, build, testTechnologySecurity, dev and test environment, tools, availabilityEnvironmentCompetition, economic, regulation, legalRetired RisksRisk Asses
8、sment DocumentTop 103. Plan 5. Control2. Analyze1. IdentifyRiskStatements4. TrackThe ongoing deliverable of this process is a living risk assessment documentResearch projects during minor releasesMarket trends and advancesCompetitor innovations and directionsEvaluate technologiesCapability, quality,
9、 sophisticationEase of useTeam skillsPrototypeIdentify key risksDefine experimentsSimulate end resultBalance among resource, feature set and scheduleDefine tasks and estimatesParallel developmentSchedule commitmentSchedule ownershipCredibility/PredictabilityDaily builds and smoke testsThe heartbeat
10、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 a list of outstanding issuesManaging by walking around (MBWA)Shows
11、you are involved and care about the projectSome people not comfortable speaking at meetingsRegular one-on-one with team membersSharing informationShare successShare failureChanging CourseGet the facts, but dont overanalyzeInvolves others in the discussionUse external teams to augment dev and testCut
12、 features instead of extending scheduleChanging SpeedWhen to increase pressureTo meet 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
13、show the team the progressAppreciation recognize teams effortTest in real worldFeedback (features, performance, UI)MarketingAugmenting your stuffRecruiting beta sitesDistribute softwareCommunicate beta statusResults-orientedReward beta sitesStart early!Get the feedback!Build a good tool to manage informationFormalize the process of learning from past experiencePost-milestone review meetings Capture project learning to develop team members and improve the pr
溫馨提示
- 1. 本站所有資源如無(wú)特殊說(shuō)明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請(qǐng)下載最新的WinRAR軟件解壓。
- 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請(qǐng)聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
- 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁(yè)內(nèi)容里面會(huì)有圖紙預(yù)覽,若沒(méi)有圖紙預(yù)覽就沒(méi)有圖紙。
- 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
- 5. 人人文庫(kù)網(wǎng)僅提供信息存儲(chǔ)空間,僅對(duì)用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對(duì)用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對(duì)任何下載內(nèi)容負(fù)責(zé)。
- 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請(qǐng)與我們聯(lián)系,我們立即糾正。
- 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時(shí)也不承擔(dān)用戶因使用這些下載資源對(duì)自己和他人造成任何形式的傷害或損失。
最新文檔
- 家庭農(nóng)場(chǎng)養(yǎng)殖技術(shù)推廣協(xié)議
- 時(shí)尚潮玩商品網(wǎng)絡(luò)銷售合作權(quán)責(zé)共擔(dān)協(xié)議
- 昆蟲記選讀教學(xué)教案:初中生物與自然知識(shí)結(jié)合學(xué)習(xí)指導(dǎo)
- 應(yīng)對(duì)項(xiàng)目管理中的風(fēng)險(xiǎn)應(yīng)對(duì)策略
- 海底兩萬(wàn)里的冒險(xiǎn)之旅教案設(shè)計(jì)
- 養(yǎng)老服務(wù)機(jī)構(gòu)投資建設(shè)合同
- 高端設(shè)備采購(gòu)與維護(hù)合同
- 花木蘭報(bào)國(guó)傳奇故事解讀
- 租賃戶外場(chǎng)地合同協(xié)議書
- 2024-2025學(xué)年高二化學(xué)人教版選擇性必修3教學(xué)課件 第一章 第一節(jié) 第1課時(shí) 有機(jī)化合物的分類
- 火電廠汽機(jī)專業(yè)技術(shù)培訓(xùn)
- DB22T 3064-2019 農(nóng)業(yè)現(xiàn)代化發(fā)展水平評(píng)價(jià)指標(biāo)體系
- 石膏娃娃課件教學(xué)課件
- 質(zhì)量部年終述職報(bào)告
- 2024全新《婚姻法》精美課件
- 口腔健康全身健康課件
- 2024年國(guó)家公務(wù)員考試公共法律知識(shí)考試題庫(kù)及答案(共530題)
- 數(shù)字出版概論 課件 第一章 數(shù)字出版及其發(fā)展歷程
- 2024年江蘇教師資格證中學(xué)綜合素質(zhì)試卷及解答
- Wonderware InTouch:報(bào)警與事件處理機(jī)制技術(shù)教程.Tex.header
- 北京2024年北京服裝學(xué)院第一批人才招聘筆試歷年典型考題及考點(diǎn)附答案解析
評(píng)論
0/150
提交評(píng)論