黑白簡(jiǎn)約工作匯報(bào)模板課件_第1頁(yè)
黑白簡(jiǎn)約工作匯報(bào)模板課件_第2頁(yè)
黑白簡(jiǎn)約工作匯報(bào)模板課件_第3頁(yè)
黑白簡(jiǎn)約工作匯報(bào)模板課件_第4頁(yè)
黑白簡(jiǎn)約工作匯報(bào)模板課件_第5頁(yè)
已閱讀5頁(yè),還剩16頁(yè)未讀, 繼續(xù)免費(fèi)閱讀

下載本文檔

版權(quán)說(shuō)明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請(qǐng)進(jìn)行舉報(bào)或認(rèn)領(lǐng)

文檔簡(jiǎn)介

1、黑白簡(jiǎn)約工作匯報(bào)模板課件黑白簡(jiǎn)約工作匯報(bào)模板課件Performance Against SchedulePlan: summarize original schedule of projectList key milestonesActual: summarize what really happened in relationship to planList differences in terms of original dates (x weeks late, x months early, etc.)Performance Against SchedulePlPerformance A

2、gainst QualityQuality goal: state original quality goal or goals for the projectList key metrics (items for measuring success)Actual: summarize what really happened in relationship to quality goalsList progress against metricsPerformance Against QualityQuaPerformance Against BudgetBudget: state orig

3、inal quality goal or goals for the projectList key cost goals, expenditure limitsActual cost/expenditures: summarize what really happened in relationship to budgetList progress against goals & limitsPerformance Against BudgetBudgPost-Mortem By DepartmentPost-Mortem By DepartmentProject Planning How

4、Was the Project Planned?Who was responsible for original plans?How did that work? Right set of people?Was project well defined from beginning?Was there an actual written plan?How was project plan communicated?How well did that work?Project Planning How Was the Project Planning Was the Plan the Right

5、 One?Was the plan a good one?What was good? What was missing?Was the plan realistic?How did the plan evolve over time?Was the change good or bad?How did the changes affect the project?Key areas for improvement:Make very specific recommendations.Project Planning Was the PlanResearch & Development How

6、 Was R&D Managed?How was the project managed through R&D? How many teams, number of people, reporting structure, etc. How well did that work? Improvements?How did the R&D teams communicateWhat methods, timing, etc.How well did that work?Research & Development How WaResearch & Development How Effecti

7、ve & Efficient Was R&D?Identifying & solving technical problemsWere issues identified early enough?Were problems solved well?What worked? Didnt work? Could be better?Estimates & executionWere estimates on track with actuals?What helped people estimate well? What caused people to estimate poorly?Rese

8、arch & Development How EfProject Management How Was the Project Managed?Meetings: who/when/how oftenHow well did this work?Communication: who/when/how oftenHow well did this work?Changes: how tracked, communicatedHow well did this work?Other methods: email, schedules, databases, reports, etc.Project

9、 Management How Was thManufacturingWas team properly prepared to receive product?BOM & paperwork complete & accurate?Materials ordered & ready?Did product meet manufacturability goals?Were there unexpected delays or problems?ManufacturingWas team properlyQuality Assurance & SupportHow was product qu

10、ality measured?Was this effective? Efficient?How did final product compare against quality goals?How were quality issues resolved?Were support teams properly prepared?Is product quality consistent with support resources?Quality Assurance & SupportHowMarketingDid positioning match final product?Was p

11、ositioning successful? Appropriate? Effective?Was product launch effective?Were marketing programs effectively implemented?Did product & launch meet marketing goals?MarketingDid positioning matchSalesWas channel & sales force appropriately informed about product?Did product and message meet customer

12、 need?Was timing appropriate? Cost?How do initial sales compare to goals?How has product been received?SalesWas channel & sales forceKey LessonsKey LessonsWhat Went RightSummarize in quick bullet points specific things that worked wellUse specific examples: “daily 15-minute morning status meetings w

13、orked well” instead of “team communicated well”.Distribute or list network location of forms, procedures, reports, etc. that were found to be particularly useful.What Went RightSummarize in quWhat Went WrongSummarize in quick bullet points specific things that caused problemsTry to isolate specific attitudes, procedures, methods, timing issues, etc. that caused problemsHow did team respond to problems?What Went WrongSummarize in quRecommendationsBy department or management level, record critical recommendations for future products o

溫馨提示

  • 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ì)自己和他人造成任何形式的傷害或損失。

評(píng)論

0/150

提交評(píng)論