1 / 20

The Development Plan

Learn the importance of having a balanced development plan, how it helps the team, and how to track progress and measure plan quality. Use TSPi support tools to work efficiently and know what to do when.

jaredsuarez
Télécharger la présentation

The Development Plan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Development Plan TawatchaiIempairote September 2, 2557

  2. แผนคืออะไร • ทำไมเราถึงต้องมีแผน • แผนที่สมดุลเป็นอย่างไร • แผนที่สมดุลจะช่วยทีมคุณได้อย่างไร • TSPi Support Tools • PLAN1 Script • การติดตามความก้าวหน้าของแผน • การวัดคุณภาพของแผน

  3. ความต้องการการวางแผน (The Need for Planning) • ทำแผนเพื่ออะไร (simple or complex?) • work more efficiently • know what and remind when to do • framework + context = work in a rational order • (with firmed schedule & fixed resources) => amount of work *** realistic plan => • แผนที่มีคุณภาพ จะมีส่วนอย่างมากที่จะทำให้โครงการประสบความสำเร็จ • แผน..ทิ่balanced • Unbalanced workload • แผนที่ Balancedคือ ทุกคนในทีมทำงานที่ตนรับผิดชอบได้ในเวลาที่กำหนด (ไม่ต้องรอกัน) • การ balanceแผน เพื่อให้กิจกรรมสามารถทำได้ต่อเนื่อง

  4. ความต้องการการวางแผน (The Need for Planning) • การติดตามความก้าวหน้าตามแผนที่ได้วางไว้ • แผนที่มีรายละเอียดจะช่วยในการติดตามและจัดการกับงานของคุณ • => ต้องการวิธีการที่จะบอกว่า ahead or behind schedule เท่าไหร่ • Planned Value (PV) & Earned Value (EV)

  5. Planned-Value Calculations • Task • Plan Hours • Cumulative Hours • Plan Value (PV) • Cumulative PV • ดูตัวอย่างที่ Table 5.1

  6. of the total job A B EV: when A + B had completed No partial credit for half-done tasks PV = planned percentage of the total job that each task contributes. EV = The sum of all PVs for the tasks that have been completed at that point.

  7. ความต้องการการวางแผน (The Need for Planning) • การวางแผนในรายละเอียด • TSPi process requires that teams estimate tasks to a granularity of about 10 or fewer hours. • However, this level of granularity is needed only at the engineer level. • การจัดการงานแทรก(Unplanned Tasks) • TSPi provides a phase when you can record time spent on “management and miscellaneous” （M&M）tasks. • 5-10% of total project time

  8. ความต้องการการวางแผน (The Need for Planning) • ระดับการประมาณการ • Sizes of parts and assemblies • Modules (assemblies of objects) • Components (assemblies of modules) • Products (assemblies of components) • System (assemblies of products)

  9. ความต้องการการวางแผน (The Need for Planning) • การติดตั้งแผน (Implementation Planning) • STRAT: conceptual design ในแต่ละ cycle • SUMP • SUMQ

  10. TSPi Planning Process • ดู Figure 5.2 มี 9 steps • STRAT • SUMS • TASK • SCHEDULE • SUMQ

  11. Produce conceptual design Development Strategy Enter size data on SUMS Produce Team Plan Make Quality Plan Engineer make personal plan Produce team member plan Balance team workload Produce the final team plan TSPi Planning Process TSPi Planning Overview

  12. TSPi Planning Process Initial estimates of parts for each cycle list the component name and size to be developed in 1st cycle + test plan & requirement Strategy phase • Calculate PV and expected completion date for each task How long each task will take & Time for the full team each week Enter the info on the …form What you do? Review the TASK and SCHEDULE forms for each person, and balance the workload - Copy TASK and SCHEDULE for each person Determine PV and estimated completion for each personal task - Use the adjusted individual plans to regenerate the overall team - deleting tasks others will perform • - Give these to all team members and instructor Generate new The products you produce

  13. TPSi Support Tool • The TSPi Support Tool can be used to help support the process, but it doesn’t fully automate the process. • *** To build a common team understanding of the work and a shared team commitment to the plan.*** • Appendix F

  14. Development Plan Sripts P. 74-91 Based on the conceptual design • Planning overview • List the products to be produced in this development cycle and estimate their size. STRAT,SUMS • Produce the task plan: Time required to perform each process task；Rough order ; Planned value（PV）of each task. TASK • Produce the schedule plan:Each Engineer’s planned time for each project task；The total planned team hours by week；The anticipated completion week for each task；PV for each week SCHEDULE • Produce the quality plan:the quality performance for every part and assembly in the systemSUMP and SUMQ • Break out individual plans based on the team TASK and SCHEDULE • Balance workload, then reconsolidate the team TASK and SCHEDULE plans • Produce and distribute the plans: send TASK, SCHEDULE, SUMS, SUMP, and SUMQ to team members and instructor

  15. Summary rates Percentdefect-free (PDF) Defects per page Defect per KLOC Defect ratios A/FR (appraisal to failure ratio) Review rates Inspection rates Defect injection rates Defect removal rates Phase yields Process yields Handing poor-quality parts Quality criteria Quality Plan

  16. TSPi Project Tracking Process - When a task is completed, enter the week in the TASK form - will feed the EV for that week At the end of each work week, generate the updated TASK and SCHEDULE to show the time and EV status of your work (WEEK form) Record your time in the time recording log Enter defects on the defect recording log - These feed the SUMP form for each assembly Update SUMP to track the time, size, and defect data for each engineer Once a component has been developed, enter its size in SUMS for that part Generate the SUMQ form for each assembly, with time, size, and defect data + documentation size Generate team level TASK & SCHEDULE, and assembly-level SUMP and SUMQ

  17. The Quality Plan • The quality plan gives the quality performance for every part and assembly in the system. • It is a summary of the quality results for the project to date, comparing the quality goals with the actual results as they become available. • The quality plan has the following sections:

  18. The Quality Plan

  19. The Quality Plan • Use the TSPi tool to generate the final quality plan on form SUMQ • （the team-level quality plan） • The quality plan is heavily dependent on having sound data input • Hence the data recorded for every task and every defect must be as accurate as • possible, or the final results will quickly become gibberish!

  20. งานที่ต้องส่ง • TASK • SCHEDULE • SUMP • SUMQ • สามารถนำเสนอแผนของทีมได้ เมื่อต้องการ • สามารถแสดงหลักฐานการปฏิบัติตามแผน/ปรับแผนได้

More Related