ithnithmBookC_StringPrint_SetupTPrintStartupSound_TabLISTBook_PrefsAct List Scene Drawing_Model Draw_Specs diagram_struct_arrayDependentsScriptPad_ListManuscriptPlayPlay_PrefsModelSubscript_Set_ListSubscript_SetArraySimulation_ModelRun_Specsentity_struct_arrayentity_structint16_arraydouble_arraytoken_type_arrayrun_handle_array Draw_Index!Poster_Info"token_type#Poster_Tab$AliasRecord%Play_Where&diagram_struct'Point_array(movie_attach)Picture_Tab*Pad+Model_Index_array,Button_Type-Condition.Movie_Tab/Model_Index0slider_type1Log_Condn2Log_Page3Picture_Data4Picture5Dependent_Entry6graph_type7curve_type_array8curve_type9table_type:table_var_type_array;table_var_type<SET=Panel>Sector_Specs?Sense_Setup@select_struct_arrayAallow_struct_arrayBPicture_arrayCEntity_Controller_MapDSection_ListEWindow_ListFModel_WindowGPad_WindowH<> ,,W?BW?W?     W?ZW?    JJ  drmd   !N!<This is the productivity in tasks per week of your designers.! "c ?????? Nfrac_hw_time_planning0 # This is the fraction of the hardware development effort that you wish to allocate to planning. Time not allocated to planning goes to implementation. Planning comprises overall project planning, coordination with other groups, and planning individual tasks. !: 6"s ??7????NTotal_Relevant_HW_Plns0 # 8This is the number of relevant plans that are in place.! " f  ??e???N hw_planningif Total_Relevant_HW_Plns0 then (hw_plnng_pers_hrs/40)*hw_planning_productivity else 0 <(D##<##(#######(# ## ### fThis is the flow of plans being created. The basic relationship is (time planning * plans per time).! "c @ ???????????????Nimpact_of_hw_planninghw_planning_index XX??ə?333334?ٙ??333333?ffffff?陙????QR??=p =?QR?zG? =p?Q? =p ?Q?Q# ! "c??????????h?????Nnorm_hw_tasks_per_week.25 ##?# iThis is the normal productivity of designers. It can be improved with planning and worsened by burnout.! "c/?????????w?????Nhw_planning_productivity01.5*norm_hw_tasks_per_week*impact_of_hw_burnout ##?### # # xThis is the productivity of your designers in planning. They can plan 50% more tasks than they can implement per week.! "c'???????Nhw_planning_index(Total_Relevant_HW_Plns/initial_hw_tasks<ed ##<# This is a 0-1 measure of how complete your plans are. 0 indicates that you've done no planning. 1 indicates that you've done as much as you possibly could have given where you are in the project.! "c??????????G?????Nfrac_hw_time_implmntng1-frac_hw_time_planning* ### HThis is the fraction of time that is spent designing (versus planning).! " s??@hMl????NCume_HW_Burnout0  # mThis is the degree to which your team is burnt out. A higher number means they can not work as effectively.! "N @Y  *$ff_?!"~NVH. Hn Hn?<pf"(H @>^The hardware team is starting to get burned out. You may want to go a little easier on them.%& *$_? d@TRThe hardware designers are walking zombies. You can't keep working them so hard.%&f??@D???Ninc_in_hw_burnouthw_work_hours_per_week-40U  #U#(# ! "c ???????????????Nimpact_of_hw_burnoutCume_HW_Burnout @.@>@F@N@R@V@Z@@^@`@b??Gz?\(\?ffffff?p =q?ٙ?љ?Q?Q?zG{# ! "f!??@C/???Ndissipation_of_hw_brnot"Cume_HW_Burnout/time_to_dis_hw_bo   # ## ! "c*@@??@@@@@@S???@?Ntime_to_dis_hw_bo5# TThis is about how long it takes poor, burned out designers to get back up to speed.! "c+/??????Nhw_plnng_pers_hrs,total_hw_person_hours*frac_hw_time_planningT #T## ! "f.9??r???Nobsoleting_hw_plans/(completing_hw_des+hw_functionality_erosion)/2*)#*#)# ## sThis is the flow of plans becoming irrelevant. As tasks are completed or eroded, some plans are no longer needed.! "c AC??????˖$by????A?????P sw_des_prodBnorm_sw_tasks_per_week*impact_of_sw_burnout*impact_of_sw_planning@### ## BThis is the number of tasks that a designer can execute per week.! "cD?????? Pfrac_sw_time_planning0# This is the fraction of the software development effort that you wish to allocate to planning. Time not allocated to planning goes to implementation. Planning comprises overall project planning, coordination with other groups, and planning individual tasks.!; 6"sE??????PTotal_Relevant_SW_Plans0!# ! "$f G??(???P sw_planningif sw_planning_index<1 and SW_Des_Tasks_2B_Completed>0 and OK_to_start_sw>0 then (sw_planning_pers_hours/40)*sw_planning_productivity else 0 >eT####>####e#######(# ## ### )This is the flow of plans being created.! "c @H???????????????Pimpact_of_sw_planningsw_planning_indexn??ə?333334?ٙ??333333?ffffff?陙??dm??n??QR?GzH??ffffff@\(@ =p @QR@ =p @Q@Gz$mnorm_sw_ta# ! "cI??????????I?????Pnorm_sw_tasks_per_week.25 ##?# JThis is the normal number of tasks that a designer can execute in a week.! "c/J??????԰J[????A?????Psw_planning_productivity01.5*norm_sw_tasks_per_week*impact_of_sw_burnout##?### ## BThis is the number of plans that a designer can create in a week.! "c K????????Psw_planning_index!Total_Relevant_SW_Plans/sw_totalKm ##K# This is a 0-1 measure of how complete your plans are. 0 indicates that you've done no planning. 1 indicates that you've done as much as you possibly could have given where you are in the project.! "cL??????????F?????Pfrac_sw_time_implmntng1-frac_sw_time_planning@ ### GThis is the fraction of the time spent writing code (versus planning).! " sS??@=EmR&Z????PCume__SW_Burnout0# [This is the accumulated burnout for designers. It comes as a result of too much overtime.! "_;@Y  *$?`d d@>IYour software developers are starting to feel the effects of long hours.%& *$?(  @  xUUUU@N@TYThe software team is on its last legs. Better think about cutting back their hours now.%&fU??@???Pinc_in_sw_burnoutsw_work_hours_per_week-40a #a#(# ! "c ?V??????$by?????????Pimpact_of_sw_burnoutCume__SW_Burnoutn@.@>@F@N@R@V@Z@@^@`@bdm??n??Gz?\(\?ffffff?p =q?ٙ?љ?Q?Q?zG{$mdissipatio# ! "f"W??@:Ui???Pdissipation_of_sw_brnot#Cume__SW_Burnout/time_to_dis_sw_bo  ## # ! "c+Y??H????Psw_planning_pers_hours,total_sw_person_hours*frac_sw_time_planning` #`## IThis is the number of person hours that are spent in planning in a week.! "ci@@??@@@@@@M???@?Ptime_to_dis_sw_bo5# NThis is about how long it takes a burnt out designer to get back up to speed.! "f.w??\???Pobsoleting_sw_plns/(completing_sw_des+sw_functionality_erosion)/2@?#@#?# ## ]This is the flow of plans becoming obsolete as tasks are completed and functionality eroded.! "gN??????"Hardware Design ! "gO??????#Competitiveness of Product ! "gP??????$Software Design ! "g"Q??????%"Integration, Testing, and Release ! "!c 6 @D@D??@G@D@D@D@D@D???@D?P& sw_st_msg7if OK_to_start_sw=0 then sw_work_hours_per_week else 0ea$ #e#####a# ## ! " vO;@D@D  *$?p@D@Don't start pushing your software team yet. They've won't even start working on your project until the hardware is further along.%&s%@Y@V@y?@y@Y@V@V@V1???@@Y?NHW_Des_Tasks_2B_Completedinitial_hw_tasks<)Rr*)#< 2This is the number of tasks remaining to be done.! "f5&??@?333333;???Nhw_functionality_erosion6pulse(HW_Des_Tasks_2B_Completed*frac_hw_func_to_drop)(Y(N#(#Y# ### (total_hw_person_hours*frac_hw_time_implmntng/40)*hw_des_prodT c(,#T# # #(# ## +This is the flow of tasks being completed.! "s [@4@4??@4@4@4@4@4@4,???@4?N HW_Designers20=T=# -This is the number of designers on the team.! "s\@!@y?@y@!@!@!'????NCompltd_HW_Des_Tasks0Ru*# (This is tasks that have been completed.! "S,]??????NHW Productivity- { Place right hand side of equation here } ! "c|??A????Nhw_attrit_frac0=# BThis is the fraction of people on the team that leave each month.! "c@Y@Y??@Y@Y@Y@Y@Y@Y4???@Y?Ninitial_hw_tasks100( #d 5This is the original number of tasks in the project.! "f ??+???N hw_attritionHW_Designers*hw_attrit_frac+;+ #+#;# ,This is the flow of people off of the team.! "s@[0@Y@i?@i@i@[0@[0,???@Y?PSW_Des_Tasks_2B_Completedinitial_sw_tasks\?Krc@?#\ -This is the remaining tasks to be completed.! "f5??9???Psw_functionality_erosion6pulse(SW_Des_Tasks_2B_Completed*frac_sw_func_to_drop)>b!>^#>#b# ### :This is the flow of tasks being dropped from the project.! "fL ?????Pcompleting_sw_desMOK_to_start_sw*(total_sw_person_hours*frac_sw_time_implmntng/40)*sw_des_prode`!l>B$ #e#`## #(# # ## ! "s @4@4??@4@4@4@4@4@4,???@4?P SW_Designers20]`]# -This is the number of designers on the team.! "s@i?@i@i????PCompltd_SW_Des_Tasks0K_v@# ! "S,??????PSW Productivity- { Place right hand side of equation here } ! "c.@[0@Y??@_fH( @Y@[0@Y@[0@[0V???@Y?P sw_total/Compltd_SW_Des_Tasks+SW_Des_Tasks_2B_CompletedB>_ #B#># WThis is the total number of tasks that need to be completed by the end of the project.! "s@I?@I}????NEroded_HW_Functionality0u)# ~This is the tasks which do not need to be complete because they are associated with functions dropped from the original spec.! "cE?ffffff?????ffffff?ffffff6????Nhw_frac_completeFCompltd_HW_Des_Tasks/(Compltd_HW_Des_Tasks+HW_Des_Tasks_2B_Completed),(e#,#,#(# # 7This is the fraction of all tasks which are completed.! "c#@@??@@@@@@@???@?Ntotal_hw_person_hours$HW_Designers*hw_work_hours_per_week+U* #+#U# AThis is the total number of person hours being applied per week.! "c@D@D??@T@D@D@D@D@DQ???@D? Nhw_work_hours_per_week40 T#( RThis is the average number of hours per week that people on the team are working.! 6"c???zG{???? Nfrac_hw_func_to_drop0)# Setting this slider lets you drop functionality from the hardware development plan thus reducing the amount of work to do. Setting the fraction to .5 means that half of the remaining functionality (and therefore half the work) will be dropped immediately.!& 6"c??=????Psw_attrit_frac0]# >This is the fraction of designers leaving the team each week.! "c@Y@Y??@Y@Y@Y@Y@Y@YE???@Y?Pinitial_sw_tasks100>#d FThis is the initial number of tasks involved in the software project.! "f ??+???P sw_attritionSW_Designers*sw_attrit_fracA[A #A#[# ,This is the flow of designers off the team.! "s@I?@I@I????PEroded_SW_Functionality0v?# This is the tasks that have been dropped because they are associated with functionality that has been dropped from the project.! "c????H????Psw_frac_completeCompltd_SW_Des_Tasks/sw_totalBK #B#K# IThis is the fraction of the total number of tasks that are already done.! " * ?  *$6@!"~NVH. Hn Hn?<pf"(H ?zGOK, your software's done.%&c#@@??@@@@@@J???@?Ptotal_sw_person_hours$SW_Designers*sw_work_hours_per_weekAa@ #A#a# KThis is the total number of person-hours applied to the project each week.! "c@D@D??@G@D@D@D@D@DQ???@D? Psw_work_hours_per_week40&`#( RThis is the average number of hours per week that people on the team are working.!% 6"c?????? Pfrac_sw_func_to_drop0?# Setting this slider lets you drop functionality from the hardware development plan thus reducing the amount of work to do. Setting the fraction to .5 means that half of the remaining functionality (and therefore half the work) will be dropped immediately.!' 6"f @@??@$@@@@???@Padd'l_sw_tasks!completing_hw_des*ad_tsks_per_hw*d> #*#d# This is new tasks being added to the software project which represents problems created in the hardware design. (Those problems are the result of poor planning on the part of the hardware group.)! "c ????????????????Pad_tsks_per_hwhw_planning_index c??ə?333334?ٙ??333333?ffffff?陙????ffffff?ffffff?Q?Q?\(?zG?p =q??Q# ! ")cP??????POK_to_start_swQif hw_frac_complete+hw_planning_index >=1.2 or hw_frac_complete>=1 then 1 else 0R @&D#R# # ##?33#3333##R######### This is the go ahead for the software team. When the hardware is either done, or started and well planned, the software team can begin. When the variable equals 0 the team is on hold.! "  ?  *$R?ffff?ٙYour hardware development has gone well. The software team is now starting their planning and implementation work. When they are done, the integration and testing team will get rolling.%&s@Y@Y@y?@y@y@Y@Y,???@Y?QITR_Des_Tasks_2B_Completedinitial_itr_tasksjklh#j -This is the remaining tasks to be completed.! "f5?????Qcompleting_itr_des6OK_to_start_ITR*itr_completion_capacity*(1-released?)rotgi#r#o# ##t# # ! "s@y?@y@y$????QCompltd_ITR_Des_Tasks0kh# %This is the tasks that are complete.! "c@Y@Y??@Y@Y@Y@Y@Y@Y*???@Y?Qinitial_itr_tasks100g#d +This is the initial tasks to be completed.! "cH????H????Qint\test_frac_compltICompltd_ITR_Des_Tasks/(Compltd_ITR_Des_Tasks+ITR_Des_Tasks_2B_Completed)igwy#i#i#g# # IThis is the fraction of integration and testing tasks that are complete.! " ?  *$V?^ xSummer@*A~ Post Messa?+You're done. Ship it now!!!%&f$??k???Qadd'l_itr_tasks%completing_sw_des*ad_tsks_per_sw_tsk@mg #@#m# lThis is the flow of tasks being added to the integration and testing process due to poor software planning.! "c ????????????????Qad_tsks_per_sw_tsksw_planning_indexl??ə?333334?ٙ??333333?ffffff?陙????zG{?\(\?\(? =p ?У =p?ǮzG?p =q??Q# ! "c@$@$??@$@$@$@$@$@$T???@$?Qitr_completion_capacity10h# UThis is the number of integration and testing tasks that can be completed in a week.! "c?????? Orelease_switch0qx~# ! 6"f C?????O hw_snapshotDpulse(hw_frac_impl)*release_enable*(1-released?)*(release_switch>0)uytpzs8#u####y# ##t# # #p### ! "cL ??????QOK_to_start_ITRMIf HW_Des_Tasks_2B_Completed=0 and SW_Des_Tasks_2B_Completed=0 then 1 else 0(>h4 #(###>#### ### ## This is the go ahead for integration and testing. The assumption is that if there are any hw or sw tasks remaining, integration and testing can not start.! "s ??Q????O HW_Features0tq# RThis is the fraction of hardware features that make it into the released product.! "c  ??_????O released?if HW_Features>0 then 1 else 0shqx$ #s###### ## `This indicates whether your product has been released. It equals 0 before release and 1 after.! "c j ???????????O hw_frac_implkif Compltd_HW_Des_Tasks=0 then 0 else Compltd_HW_Des_Tasks/ (Compltd_HW_Des_Tasks+Eroded_HW_Functionality),Nq4 #,###### ##,#,#N# # ! "c j ??????O sw_frac_implkif Compltd_SW_Des_Tasks=0 then 0 else Compltd_SW_Des_Tasks/ (Compltd_SW_Des_Tasks+Eroded_SW_Functionality)B^z4 #B###### ##B#B#^# # ! "c ???????Oqualityint\test_frac_compltk|??ə?333334?ٙ??333333?ffffff?陙???Q? =p?(\)??\(\??=p =?Q?#k ! "/c S??9????O already_relTIf release_switch >0 and delay(release_switch,dt,0)=0 and released?=1 then 1 else 0pt\#p###p##########t######### :This posts a message if you try to release a second time.! " ?  *$"?Pv>$?)You have already released the product!!!%&c) ??\????Orelease_enable*if int\test_frac_complt >.5 then 1 else 0kq~, #k#>#?### ### ## ]This says you can't release until you are at least half way through integration and testing.! "f 0 ?????O sw_snapshot1if hw_snapshot>0 then pulse(sw_frac_impl) else 0qv|{0 #q### ##v#### ## ! "s ??Q????O SW_Features0z# RThis is the fraction of software features that make it into the released product.! "f+# ?????Oquality_snapshot,if sw_snapshot>0 then pulse(quality) else 0zw}0 #z### ##w#### ## ! "s$??-????OProduct_Quality0|# .This is the quality of your released product.! "%c7' ??b????O can't_do8If release_switch >0 and release_enable=0 then 1 else 0py4 #p###y#### ### ## cThis just posts a message if you try to release before you've done enough testing and integration.! "  ?  *$V?ffff?ٙProduct not released. You have not yet done enough integration and testing work to release. (Integration and testing begins when hardware and software are complete.) Try again later.%&f<9?????comp's_hw_snapshot=pulse(comp's_hw_frac_complete,Competitor's_Release_Date,999)###### ! "/c?:?Ƨ-????Ƨ-?Ƨ-?Ƨ-????comp's_hw_frac_completetime@@$@.@4@9@>@A@D@F@I@K@N@P@@Q@R@T@U@@V@W@Y? =p?\(?zG?????????????????## ! "^'??  *$7@/!!!!??Good news: Your cousin is a disgruntled secretary in your competitor's hw development group and is helping you to monitor competitive progress. Bad news: Your competitor is off to a good start.%& *$7@HL L?ٙYour spy tells you that your competitor is really cracking the whip and is almost half way through their hardware development effort.%& *$7@HL L?陙Your competitor has a working prototype. Their team has been pulling some long hours and is slowing down. Still, they are on schedule to complete their hardware design work in just a few weeks.%& *$>7@HL L?zGThe bad guys have completed their hardware work and have "thrown it over the wall" to the software group. Your competitive info from here on will be sketchy.%&(c?;??????comp's_sw_frac_completetime@@$@.@4@9@>@A@D@F@I@K@N@P@@Q@R@T@U@@V@W@Y?Q??QR?? =p??(\)?????????## ! "Z ?  *$7@!"~sNVH. Hn Hn?<pf"(H ?Your competitor has run into some snags. They are working around some microcode issues in software. They seem to be about 1/2 way thru software design.%& *$:7@h33Hn T,?ffffffDespite problems, your competitor seems to be nearly through development. They are likely to have a protracted period of i&t due to incompatibility issues that arose from poor planning.%& *$2 ?zG{Your competitor's begun integration and testing. It seems that they may have had to hack off some software functionality to preserve their schedule.%&c?<??????comp's_itr_frac_completetime@@$@.@4@9@>@A@D@F@I@K@N@P@@Q@R@T@U@@V@W@Y?\(?Q??p =q?\(???## ! "  ?  *$??????Competitor's_Release_Date0# ?This is the randomly selected release date for the competitor.! "f? @w??@v͝@wF???picking_release_datepulse(Normal(84,6),1,999)( #T######### GThis is the selection of the competitor's release date...it is random.! "s@??@????Comp's_HW_Features0# AThis is the fraction of hw features in the competitor's product.! "  ?  *$r??!"~NVH. Hn Hn?<pf"(H ?Q}Your competitor just released their new product. It looks pretty good. You can view the specs on the market control panel.%&sA??@????Installed_Base_of_Comp_Product0# AThis is the total number of units that your competitor has sold.! "c  ?B?????? quality_2comp's_itr_frac_complete??ə?333334?ٙ??333333?ffffff?陙???Q? =p?(\)??\(\??=p =?Q?# ! "sC??8????Installed_Base_of_Your_Product0# 9This is the total number of products that you have sold.! "fBE ?????comp's_sw_snapshotCif comp's_hw_snapshot>0 then pulse(comp's_sw_frac_complete) else 00 #### ###### ## ! "sF??@????Comp's_SW_Features0# AThis is the fraction of sw features in the competitor's product.! "c/H ??????attractiveness_of_your_product0100*Product_Quality*(HW_Features+SW_Features)/2}s{$ #d#}# #s#{# # ## This is a 0-100 metric of how attractive your product is to the market place. It is a function of features (hw and sw) and quality.! "f4J ?????comp's_quality_snapshot5if comp's_sw_snapshot>0 then pulse(quality_2) else 00 #### ###### ## ! "sK??0????Comp's_Prod_Quality0# 1This is the quality of the competitor's product.! "cBR ??????attractiveness_of_comp_productC100*Comp's_Prod_Quality* (Comp's_HW_Features+Comp's_SW_Features)/2$ #d## ### # ## This is a 0-100 metric of how attractive your competitor's product is to the market place. It is a function of features (hw and sw) and quality.! "f,T??8???your_wom_sales-Installed_Base_of_Your_Product*your_wom_mult ### 9This is the flow of sales you get through word of mouth.! "f,V??J???comp_wom_sales-Installed_Base_of_Comp_Product*comp_wom_mult ### KThis is the flow of sales that your competitor gets through word of mouth.! "c  ?X?0bM?0bM???0bM?0bM?0bM?0bM?0bM?0bM????0bM?your_wom_multattractiveness_of_your_product@$@4@>@D@I@N@Q@T@V@Y?0bM?s*0U2b?zG{?Q?9XbM??"a?Q?zG{? =p ?# ! "c  ?Z??????comp_wom_multattractiveness_of_comp_product@$@4@>@D@I@N@Q@T@V@Y?tzG{?zG{?Q?zG{??Q?Q?zG{? =p ?# ! "fl??3???your_other_salesbase_demand*your_fract ### 4This is the flow of sales you get from base demand.! "fn??@???comp_other_salesbase_demand*comp_fract ### AThis is the flow of sales your competitor gets from base demand.! "c C @4o??\???? base_demandDMax(attractiveness_of_comp_product, attractiveness_of_your_product)@$@4@>@D@I@N@Q@T@V@Y@ffffff@!333333@(ffffff@.@1@2@3@3fffff@4@4#### ]This is a baseline level of demand which exists as soon as there is a product on the market.! "c  ?r?????? your_fractrel_attrac_of_your_prod??ə?333334?ٙ??333333?ffffff?陙???zG{?? =p ?Gz??GzH?Q?333333?zG?# ! "c s??????????????? comp_fract 1-your_fract ### ! " c{??????rel_attrac_of_your_prodif attractiveness_of_your_product>0 or attractiveness_of_comp_product>0 then attractiveness_of_your_product/ (attractiveness_of_comp_product+attractiveness_of_your_product) else 0 D############# # ### This is a measure of how attractive your product is relative to your competitor's. .5 means you are equal. 0 means that both products have not yet been released.! "cc ??B????your_frac_of_inst_systmsdInstalled_Base_of_Your_Product/(Installed_Base_of_Comp_Product+Installed_Base_of_Your_Product+.001)$ #### #+#?PbM## # CThis is the fraction of all installed systems which you have sold.! "c ??N???? your_sales your_other_sales+your_wom_sales ### OThis is your total sales, some from a base demand and some from word of mouth.! "c ??&???? comp_sales comp_other_sales+comp_wom_sales ### 'This is your competitor's total sales.! "c( ??3????your_mkt_share)your_sales/(your_sales+comp_sales+.0001)$ #### #+#?6#C-# # 4This is the fraction of total sales that are yours.! " <  l\\ O  p+\'a PX>NX>;6 ()Hardware Design*This is the process of designing hardware. In managing the process, you will be given choices about how to allocate time, how hard to push your team, and whether or not to drop functionality from the specs in the interest of getting to market more quickly.+, 6'PO @yH  !"#()Competitiveness of Product*yThe competitiveness of the product is a function of hardware functionality, software functionality, and product quality.+, 6'PzcPzuG]}!()Software Design*GThis is the process of designing software. In managing the process, you will be given choices about how to allocate time, how hard to push your team, and whether or not to drop functionality from the specs in the interest of getting to market more quickly. Decisions made in hardware design can add to the software workload.+, 6'C@l Panelsr(zz)*+, 6'N4mD4mS% ,e[-()*+-TT n;AHn n .&Z;(! 6/Click to Continue >>0, 6'C@ ml(utu)*+, 6'POQ"O7=2?#()"Integration, Testing, and Release*=This is the process of bringing the hardware and software together and making them work properly. Decisions made in hardware and software development will add to the amount of work that needs to be done to get to market. You can choose to release before ITR is complete, but that will compromise product quality.+, 6'C`5@ Hu(PP)*+, 6'Cn@  ()*+, 6'C@ O ( WW)*+, 6'PA AF 9N$() Competitor*Your competitor is racing you to the market. They are trying to build a comparable product with the same resources...and they are serious!+, 6'PAk Is$"()Market*Once you or your competitor bring a product to market the people will start buying. They will compare the competitiveness of the two products. There is advantage in getting to market sooner.+, 6'D T @  4 t()* Dev Progress+ , 6'Re @ ] n Z()*+1hh RW??023&! ! , 6' tk%@)k%E$ OcM,()*ORe-engineering the rules by which critical decisions are made is an often overlooked or avoided area for process improvement. In part, this is true because it is easier said than done. Changing decision rules means modifying the way people process information. Modifying these rules is especially difficult when decisions are being made under pressure. In such situations, people tend to rely on instinct. This model illustrates the powerful role that a management flight simulator can play in disciplining "the gut." The concept is not unique: Military and civilian pilots are trained by being put through a variety of simulated, high-pressure flying situations. Making the right (and wrong) decisions, albeit in a low-risk environment, effectively imprints a disciplined decision rule in the mind of the decision maker. Practice makes perfect. The decisions addressed in this model are those involved in managing a hardware/software system development effort. The model is used to understand the interdependencies in such a process, as well as to allow decision makers to "fly the process."+, 6' t@j>r()*>Re-engineering Decision Rules in a System Development Context+, 6'N (D ( q   y()*+- AGn n .&/Back0, 6'N HD +X  3`()*+- AN;n n .&/Pause0, 6'N/D/9Q'AY()*+- Ar;~;H, n .&/?IClick on ?s for more explanation. Click on a triangle to see the model.0, 6' t@GU@Y]()*@Product Development Management Flight Simulator: Model Overview+, 6' t<@(< ` z4 h()*In both hardware and software development, you have three decisions to make: The fraction of the team's time that should be spent planning. The number of hours per week to work the team. The fraction of remaining functionality to drop from specs. Use the sliders to implement these decisions on the control panel above. Clicking ?s provides more info. Click on the "Sys Dev Progress" button and you'll see a graph which shows your progress. More details can be found by clicking on the "Details" button. The "Planning Index" shown above gives you an idea of how much planning you've done relative to the maximum possible planning at any point in time. (It is on a 0 to 1 scale.) Planning makes you more productive, and helps keep teams "in sync." Even projects that are well-planned up front require more planning along the way as you progress with a design. To "fly" the process, click on the run button below. Pause when you want to change any of the decisions. Grabbing a slide bar will pause the simulation automatically. Occasionally the simulation will automatically pause to send you a message. IMPORTANT: First focus on managing the hardware team, then worry about the software team. On this project the software team can't even get started until the hardware development/plans are well along. When hardware and software are complete you will start integration and testing. After you have done sufficient integration and testing and are ready to release your product, advance to the next page (right arrow button). Don't be shy about experimenting. After you beat the competitor (who's not very smart), don't rest on your laurelstry again to get more market share. +, 6'N^7@^7Y V/a()*+-  ;n n .&/Button0, 6'N -HD - r  % z()*+- A;n n .&/Pause0, 6'W@ ()*+1?RW?p?0p23&! ! , 6'N D V/ ^7()*+- A2;>;dP n .&/ithink Analyst FeatureseThis model was built with the Analyst version of ithink software and uses Space Compression Objects.0, 6'ND(Y 0a()*+-b;A$n;n n .&Z;! 6/Model Overview0, 6'N D + 3()*+- A;n n .&/Run0, 6'J',oeh= -()*+1@D@T@D@DRW?U?0U23&! ! , 6'ND +  3()*+- A;n n .&/Run0, 6' t ,@ ( b  0 j()*Hardware Planning Index+, 6' t? @? c a 7 k i()*Software Planning Index+, 6' t @  g  o()*Control Panel+, 6'N Y,D Y+  Q3()*+- A.:n n .&/Stop0, 6'Cj@!+( 33)*+, 6'C  @"b"cde(j)*+, 6'C@#()*+, 6'C,  @/1y$Afgh()*+, 6'J& rh% =< ()*+1@D@T@D@DRW?a?0a23&! ! , 6'Jd,xn&>hz -()*+1?RW?Y?0Y23&! ! , 6'Jc vl'= =y ()*+1?RW?b?0b23&! ! , 6'R- ,@(% 6 Y()*+1RW? ?0 23&! ! , 6' t?@?)7()*Post Flight Debrief+, 6'D+@ *<()*Details+ , 6' t@/ + 7()*Planning is key to success in this development effort. Having complete plans does two things for you: It increases productivity as you implement and it also creates fewer downstream problems. A poorly planned hardware project means slow hardware progress, as well as a pile of problems that software engineers are going to have to clean up. Interestingly, the fastest way to get through the hardware project is to blast ahead with little planning. That's more or less what your competitor did. However, doing so really slows you down in software development and later in testing and integration. The way to get product to market most quickly is to take time planning in both hardware and software. This stretches out the hardware schedule, but more than makes up for it downstream. It's a clear case of conflict between local and global goals. You may also have noticed the unintended consequences of "cracking the whip." If you push your team with long hours, it helps in the short run, but over time they get burned out and that kills their productivity. You may want to review the model structure (click on the Model Overview button), and then go back and experiment with the strategies (both bad and good) to better understand the dynamics. +, 6'R@ ,@()*+1RW??023&! ! , 6' t)@) -x!()*xClick on the button below to release product. You can only release it once. Releasing early will compromise quality.+, 6'N D +E .3M()*+-:A~I n n .&Z;! 6/ Continue >>0, 6'R@ /3()*+1RW?}?0}23&! ! , 6'R@ 03()*+1RW?s?0s23&! ! , 6'R@ 1)()*+1RW??023&! ! , 6'R@ 2)()*+1RW??023&! ! , 6'R@ 3)()*+1RW??023&! ! , 6'R@ 43()*+1RW?{?0{23&! ! , 6' t@ 5()*Yours+, 6' t@ M6U()*Market Results+, 6'DF @ 79d()*Market Results+ ,, 6' tL@L6 8D>()*Your Market Share+, 6'N D   9  ()*+- A:n n .&/Run0, 6'J,GM?:h -()*+1?RW??023&! ! , 6'J ; = ()*+1?RW??023&! ! , 6'N t,D t  < l ()*+- AR:n n .&/Stop0, 6' tW@Wq =&Oy()*& 1997 High Performance Systems, Inc.+, 6' t@ > ()*Released Product Ratings+, 6'ND ?()*+- A:n n .&/Run0, 6' t@* @ 2()* Competitor+, 6'N HD  G A  O()*+- A:n n .&/Pause0, 6'NHD' B/()*+- A:n n .&/Pause0, 6'N<D<^C4#f()*+- A *:6:2 n .&/?3Concentrate on hardware development at the beginning. DON'T WORRY ABOUT YOUR SOFTWARE TEAM AT THE OUTSET. You'll be notified when they are ready to start. Later, when you're ready to release the new product, pause the simulation and then click on the right arrow to proceed to the Market control panel. 0, 6'NDDD D< ()*+-Z:Af:n n .&Z;e0! 6/Sys Dev Progress0, 6'N D  [ E  c()*+-2HA9n n .&Z;x(! 6/Details0, 6'N@NFV()*VV*'I4'I:'IYXޔ634o/FFgG3'I4 o/:'IFgT4Dg*5Dg gD Dg0!<_"]#777777":#:#IIIIII1#:]IIIIII &'4Y2&'5Y,Arial (21Back%+- An n .&/Back0, 6'N D ' j G / r()*+-:AH n n .&Z;! 6/ Continue >>0, 6'NADA' H9/()*+-V:A* n n .&Z;! 6/ << Return0, 6'N )D )* I!2()*+-:A* n n .&Z;(! 6/ << Return0, 6'N D &+ J.3()*+-:A9n n .&Z;! 6/>>0, 6'ND&> K.F()*+-R:A9n n .&Z;! 6/<<0, 6'N.&D.&Ms*L&U{()*+- A::fxx n .&/AuthorsgOriginal model by: Phil Odence with support from: Paul Kucera Updated by: Steve DeMello Matt Mayberry0, 6'N D #  M+ ()*+-:A:#n n .&Z;(! 6/#To Table of Your Variable Settings0, 6'DUz@NHjs()* Table 1+ >, 6'NV DV v Z ON ~ b()*+- AnGn n .&/Back0, 6'ND g P o()*+-An n .&Z;G! 6/Hardware Development Details0, 6'ND( l Q0 t()*+-_An n .&Z;! 6/Software Development Details0, 6'NKDKq o RCy w()*+-An n .&Z;X! 6/Integration Details0, 6'N^ D^  < SV  D()*+-AZ*n n .&Z;(! 6/Back0, 6'DK@T>i()* Graph 1+ R, 6'N""D""A` UIh()*+- A"*n n .&/Back0, 6'N!}D!}C VuK()*+- A~*n n .&/Run0, 6'N"HD"D WL%()*+- ARn n .&/Pause0, 6'D@X()* Graph 2+ `, 6'NDW Y_()*+- An n .&/Back0, 6'NoDo Zg()*+- An n .&/Run0, 6'NHD [()*+- Av*n n .&/Pause0, 6 drmd" 6plwh&k6plwh&6plwh&6plwh&}6plwh&Z6plwh&`  W   `'g~ P ~ v~() Competitor*+, 'g& & w&()Market*+, 'cH2@ *UH()*+, 'ab3@ b3FV()*+, ' t`.P@ `.j@ 7X&rH()*7Click on the up arrow above to retract this submodel.+, ' tIN@ ]IS 7A[()*7Click on the up arrow above to retract this submodel.+, 'doN@ ]gitofx()*+, 'd_9N@ ]7 Downlo%()*+, 'c_]R} $>()*+, 'cc] V#"()*+, 's!] l2 2()*+, 'd$  N ] -)()*+, 'f3Z]  RKi 214(#(#)*(;7;+, 'ct^] g.!()*+, 'c]1()*+, 'c+]_.()*+, 'c<N ]1()*+, 'c ]j !()*+, 'ctX ]g!"=()*+, 'c!TN ]E?0()*+, 's{ ]!uR),()*+, 'dN ]()*+, 'f ] (()*(+, 'cy ]l_$,-()*+, 'fC]'', |R)+(g)*(v.+, 'dN ],' ()*+, 'aF/N N6 ]j^Hr1 KS()*+, 'a|N} ] \()*+, 'aN&9I ]"?= 1()*+, 'aRN . ] *7S()*+, 'a N~ ]\x"^WtW()*+, 'aNY+ ] N>()*+, 'a NyO ] XJ Y#()*+, 'aN #l ] '!She()*+, 'a NS ]"TU\r()*+, 'a N/.G ].#GCa()*+, 'aN5Y ]5$YVv()*+, 'sm(%L~"53()*+, 'f~)&f@~8( nnHH)*( nnRR+, 'c~UN ]??l'E"(()*+, 'a#'N(R ]4(I()*+, 'a[NyX ] |)=Iw()*+, 'c26]no*%P^+()*+, 'aU*N|d4 ]??lr+-?()*+, 'aqN[& ] M,-kF()*+, 'clN ]-;.()*+, 'a,-Ny2C ]`M.@1j()*+, 'cI]/<g/0#()*+, 'a;N/w" ]u0#A ()*+, 'aAN y ]1kY-()*+, 'av N C' ]Rd2"*a?()*+, 's@%(N]3q4()*+, 'a_\3N d) ]^?8e4)4.wU()*+, 'ag%NPM QNf5HlUi()*+, 'f~\*6f|\ 7>?@(nn)*(ll+, 'co6*N ]7be;()*+, 'c&)N ]8{<()*+, 'f2]9Q D:;<("")*(44+, 'd 9N] half wa:(()*+, 'as7N9JA ]KZ;6.i()*+, 'a]8N9l) ]{<2()*+, 'cN@ H=@()*+, 'aN6@ ]?>()*+, 'aK]N6Qf@ >S?e|bM()*+, 'a;=N6@ ?@ve.()*+, 'dWP@ gitoA()*+, 'd&_wP@ 7 DownloB/()*+, 'coCbZ`e~()*+, 'cmD`pc()*+, 's Es1a()*+, 'd%GPF.(()*+, 'f3[GR2X F_oqtv(#'#)*("$"+, 'c}lHp<`b()*+, 'cIQZ^()*+, 'cRJ ~^_m()*+, 'cK abst()*+, 'cy[,LBc()*+, 'c6`P EM){Td()*+, 'g"$N,()Hardware Design*+, 'g$U#$UrOMz$U()Competitiveness of Product*+, 'g!.$!.LP&T!.()Software Design*+, 'g V%" V rQNz V()"Integration, Testing, and Release*+, ' tdl@O R& Wd()*& 1997 High Performance Systems, Inc.+, 's!uSrhk()*+, 'dUPT()*+, 'fUTg()*(+, 'crVe_ekl()*+, 'fg'',W?dXhjA(G)*(D+, 'd?WP,'X6H()*+, 'cF Y9d@dpq()*+, 'aIPCQ& QZ&i()*+, 's:+[Z()*+, 'sk, \J|  ()*+, 'S -;]?()tx<5 '*-/3789: !"#$()+,.0124;<>*+, 'aXIPJ= ^;M()*+, 'aJPGB _??/X()*+, 'ayaHPCm \x`h~f()*+, 'aEPK:  Wpa5"()*+, 'aKPH?i  @bws()*+, 'aDPL) c9_w()*+, 'anMPYDC OEdB&C()*+, 'aVPC5C 5eC_q()*+, 'c aP ??lf( g()*+, 'afPUX Yg()*+, 'aSPWqb  hWn()*+, 'ci noi A6j()*+, 'akiPWit ??lx^jMd()*+, 'aSPVA: ~Kk3x()*+, 'cVP l^m()*+, 'axlPJ$ 8 m-T()*+, 'cXeP nu6zo()*+, 'a\nPGB7 ">o?8E}Y()*+, 'a DPY'[ $)pWCi()*+, 'a*YPG`: *VqB7SX()*+, 'cKP 0r)s()*+, 'arPK% 0+s$()*+, 'abKPG tZ-()*+, 's>P8ubhv()*+, 'aoluPG_= av?-by()*+, 'f5!wT-5x{}B(%%%)*(%%"+, 'd"-wPx$+6()*+, 'c @P y?}()*+, 'cy?P [zl={()*+, 'aXzPw" {2u()*+, 'c;|;()*+, 'a1yPw% }, .()*+, 'aCP@ V~>()*+, 'c5<8(B()*+, 'f =+.(&)*(&+, 'sr>Q*,u()*+, 'f?yiz( q)*( q+, 'aP,r .fm4bH()*+, 'fy@ Vyy~(qq)*(rr+, 'sA()*+, 'sr B QA ()*+, 'S CQ3H)/()tz<6ABCDEFGHIJKLMSTUVWXYfilnruwxyzZ^_`abcdeghjkmopqstv{}~*+, 'aP=9@ ~=/~ ()*+, 'c%LP@ ^C()*+, 'cKQ@ ^n()*+, 'agPK0@ 9.9K.|g()*+, 'aQhq@ gu}()*+, 'cS^P@ H56`()*+, 'a|rP,@ ,VA[|s()*+, 'cC9P@ %PG()*+, 'cG\K%8%[)ITp,r()*+, 'anP<WB@ 66=WBH#Lm()*+, '''sPN()*+, 'c`P@ 9@S~()*+, 'c0&@#N()*+, 'aTPS#@ P$-YU()*+, 'aHPU@ 23X)K()*+, 'cJ\R,3W5()*+, 'ad\NhL hMfGcif()*+, ''dN ()*+, 'a [NJ+ T&2()*+, 'a^|NR  { P.=@()*+, 'cTx()*+, 'a:[NbF5 f>:,?()*+, 'aPN67U K9SyUP()*+, 'cU '()*+, 'aNZ DV()*+, ''''''''''''cCEYD<%Pv()*+, 'aH|N&7  ;IAC()*+, ''''''arPgL hJfGbwn()*+, '''''''''''''''c1=[$O^()*+, '''c8\8+E()*+, 'ft]L3t(T)*(  T+, 's]^4 ()*+, 'cE_'R()*+, 'a5PZ2; R@F0Is@()*+, 'dLP C U()*+, 'aPy\ zN { ()*+, 'a7cPG%  { P>& >,m=c()*+, 'c`% pM()*+, 'a2PHw Js!5()*+, 'ahP)q K's|rh()*+, 'caf()*+, 'aPT! DT!()*+, ''c+[bD<:I()*+, 'aGP=H  9I\&M()*+, 'dscP jZ|lrc()*+, 'fc>Qihc(pkp)*(qkq+, ''c6P ()*+, 'aPV {Tz()*+, 'cTd5y()*+, ''aP/K /K{W()*+, 'cP" <()*+, ''ce9-E n()*+, ''aP- :_()*+, 'aP "|()*+, ''''''aPIQf KNm}()*+, ''sqgP\()*+, 'ak/QK LcF*pl/()*+, 'f{hP'(k/k)*(s/s+, 'sr)i Q]()*+, 'c7j8*D+()*+, 'cHk*uU4()*+, 'alQK LcFql()*+, 'dpQ gzyr()*+, 'fl>QiU(pp)*(qq+, ''cma()*+, ''aQZ" Z!()*+, 'cQ H @ ()*+, 'aQH Gy()*+, 'c o@()*+, 'aQ} x()*+, 'c]p?j)6()*+, 'dO  ()*+, 'fcqc  5()*(+, 'cr<s()*+, 'ssw]()*+, 'aQI Hn?<M~()*+, 'sF%Q ()*+, 'sQ 2()*+, 'aQ1L /0;BK()*+, 'aQD3 PO`pI/()*+, 'sO < z()*+, 's\O  {()*+, 's$O  {5()*+, 'scO 2 Bt()*+, 'a.\4Oaz =` ~,*\()*+, 'c_0tY(_ R#}V57()*+, 'c!uK?()*+, 'a O H, mf()*+, 'a O 2R n0f()*+, 'c<$v /ZB!()*+, 'a' !O9 P 9f">(()*+, 'a] !O@ lr@f;b]()*+, 'cw& ()*+, 'aO #4fb+()*+, 'cJx2(,W67()*+, 'a,OX Xf'],()*+, 'cW)yJuH(()*+, 'aODH 8 FFW.g()*+, 'aeOk lf`fe()*+, 'cNO qA|l()*+, 'aO& (AX#()*+, 'dO ()*+, 'fez-e !%()*(+, 's{^()*+, 'aOM E FMd()*+, 'a@XOJ2 EH!2 $7]BW()*+, 'dc#O "Zla()*+, 'fr|#Z'p"%&(bb)*(``+, 'sa3}$@rW_()*+, 'aO# .%fsC()*+, 'aO#0J 2&Gn()*+, 'c6_~4p')KTp()()*+, 'afWO'5/ `4(03+SXgX()*+, 'aO'U#n S')e9c`()*+, '''aP Lf,vJvW()*+, ''''''''c%O PO4T ()*+, 'aA Olh mg5ch0@()*+, 'aO+F 16?D\()*+, 'a7 O9+ ?f7'Ng(;()*+, 'dI9 8@RF()*+, 'fX9-fHV8GNQ(HH@)*(FF@+, 'cr#:eyQ()*+, 'cJ#;P()*+, 'c#< O()*+, 'sF,=%WhN()*+, 'dJ? >ASD()*+, 'fXi?@w U>(HH)*(EE+, 'sGT@&%X`()*+, 'sAfZ\()*+, 'c;B&PMO()*+, 'sCvCW()*+, 'deE D\ne()*+, 'fEeDGLP(])*(]+, 'sFa()*+, 'a9E= EG?U?()*+, 'cv} OH cdeiw|()*+, 'dgJ I^pf()*+, 'fJgILM(_)*(^+, 'sKb()*+, 'aGEJ" (LU()*+, 'a6BJ[: Y=M45()*+, 'av=9e ]bNJ<kP()*+, 'al<B] ]O4l()*+, 'a';E? @S<P""H'()*+, 'ao:9= ,_QTlp()*+, 'cmpatibilRL fghjx}()*+, 'dT S()*+, 'fTSWY()*(+, 'dV Uy()*+, 'fPVsPU[\(z')*(z'+, 'aCTG" ~RW ()*+, 'cXYi()*+, 'aXTS [,UY()*+, 'c_vZ;[j()*+, 'a+ZVr> [,q[ARn)()*+, 'a7AV 3HO\ H7()*+, 's34 ]DQe()*+, 'sg4   |^FxQd()*+, 's4$   |_|Xc()*+, 's5"@ \`FYh()*+, 'si&F aHzUg()*+, 's&K bzUf()*+, 'aT_"H ? @*fc0CoT()*+, 'a$^"H&S @6fd?lCs5()*+, 'a]"H%2n @>fe^>Cx()*+, 'ab$R" @ff()*+, 'aa$R. @fg(f()*+, 'a~'`$RF @fhA8y()*+, 'aHXb -)bfi()*+, 'afJRZxq xfjqXfJ()*+, 'dml @kdvm()*+, 'f@lm@kpt(e)*(e+, 'dn m()*+, 'fnsmqu()*(+, 'cotpqyz()*+, 'aolW3\ JfpA()*+, 'aonM )q()*+, 'c&rDtv~()*+, 'c(chsuv()*+, 'arla5 )a5t?'()*+, 'asn1 )u5()*+, 'a6rs$D ?)v=!0()*+, 'cXH L|w:=ey()*+, 'cER 9x8Rz()*+, 'aHwo hours_pey^xD()*+, 'axon 2zoD()*+, 'ct {Vw|}~()*+, 'a|H{V& yU|'z~{()*+, 'aR{}" ~}"{()*+, 'ah{r2 2f~-mh()*+, 's0A _iA()*+, 'c]4P{()*+, 'aI -VH()*+, 'a| d{()*+, 'sC  > ()*+, 'c?.()*+, 'aTzJ D:}I()*+, 'a6l 96()*+, 'c 4:()*+, 'aFV) *$KG()*+, 'anG6 B:()*+, 'cI  +V0()*+, 'cG:e()*+, ''a['! )5GY()*+, '''cF Q </]()*+, 'a#Q*i  !vJ()*+, ''''''aV%N&I3 G#k49vJ()*+, drmd +66?:f :g D99::OZ; BO: 7ZZfO:O:O:@c@Z+ Development Progress89BRW?RO:@iz0RBg09RW?_O:@iz0_Bg09RW?kO:@iz0kBg0! 6 +E:?:b o;j;'.9:9::OZ;*BO:A 7O:O:O:@Z@Z+  Hardware89RW?(&O:?QR\0(Bg09RW?,2O:?QR\0,Bg09RW?N >O:@QR\0NBg09RW? JO:@k\0 Bg07O:bO:nO:@Z@Z+  Software89RW?> zO:?QR\0>Bg09RW?BO:?QR\0BBg09RW?^ O:@QR\0^Bg09RW?O:@k\0Bg07O:O:O:@Z@Z+ ITR8 9RW?gO:?QR\0gBg09RW?iO:?QR\0iBg0!* 6 +/::#**::'Z;7BO: 7O:6O:rO:@c@J@c+ ,Market Results89RW?~O:?GzH@i0Bg09RW?O:?GzH@i0Bg09RW?O:@hp?0Bg09RW? ':@hp?0Bg0!7 6 +#/::0K lN9Z9::'jZ;NBO: :bb:'"R':^':?T2J/:+ >Variable Values0;<"RW?0 <RW?U0U <RW?Y0Y <RW?0 <RW?a0a <RW?b0b = !N 6 +n J E 1HH:*Z;TBO: 7@cϤ@c+ RSoftware Progress89RW?>0>9RW?B0B9RW?^ 0^9RW?0!T 6 +:l7#:OZ;XBO: 7_B6@cϦ(@c+ `Integration Tasks89RW?g0g9RW?k 0k9RW?o   0o9RW?i 0i!X 6 % Y~X WzW?b':':O:j:*:>:  >':z': p s   drmd N > >':.': p > z   drmd ~  >':': p    drmd >':v:: p?7:=T@bb:::::F L(ABC #D0!: 6D0!; 6D0U! 6D0Y!& 6D0a!% 6D0b!' 6D0p! 6 Ev2EF G @}G@yH mG3+ HO,+ H/$u`+ >H?+=+ ,HVLp8+ RH?6Y"+ `