ࡱ> @kg?  !"#$%&'()*+,-./0123456789:;<=>BPODEFGHIJKLMNSQRUVWXYZ[\]^_`abcdefghijmnopqrstuvwxyz{|}~Root Entry":tOG1yA< 19 @2y@2yProps fxTBkndCal @2y@2ybxbx|@TBkndTask,TBkndRsc,TBkndCal,TBkndAssn,TBkndCons,TBkndOutlCode@DHS-PMO@@@'@@ @z!:@Basic Project Plan Template: @Basic Project Plan Template @ @Basic Project Plan Template, Project Schedule, MS Project Plan, MS Project Shedule@Standard@@$@@@@@@@@@@@@@@` @  @ !@'$@%@&@^'@(@P)@{5A524131-584D-5054-244C-2556522F6F3A}*@+@,@-@.@/@0@1@2@3@4@5@6@7@8@9@:@;@<@=@>@?@A@B@C@D@E@F@G@K@M@N@O@P@Q@ R@S@ T@U@V@W@ X@Y@ Z@[@\@]@^@ @@ @@@@@@Ox` ` ` x` ` ` x` ` ` x` ` ` x` ` ` @@@@@@@@@@"t3@! V@  @ @ d@ (db@ d@ (d@ "d"@ (d@ (d@ "d \@ d@@ d@ (d@ (dG@ (d @ "d @ (d @ (d@ (dR@ (d@ (d @ "d@ dm@ (dx@ "d @ d@@ (d@ d @ (d @ (d @ (d }@ "d@ d@ (d@ (d ~@ "d@@ d@ d@ (dy@ "dz@ "d@ (d@ (d {@ "d@|@ "d @ (d &@ " '@ " d@ * c@ * @ " @ " @ "$ @ ( @ * @ (, @ (. @ 2 @ 6 @ (: @ (< @ (@ @ (B @ (F @ (J @ (N @ (P @ (R @ (V @ (X #@ (\ $@ (` )@ hd *@ hh +@ hl ,@ hp @ (t e@ (x @ (z @ (| !@ (~ @ ( @ ( ]@  @  q@  r@  @ ` %@ " (@ " @ ( @  @ h @ (e @ (e @ (e @ (e @ (e @ (e @ (e @ e @ (e @ e @ e @ (e@ @ @ e@ e@ e@ e@ e@  @  @ J @  p@  @ 3@ 6@ 9@ <@ ?@ B@ C@ D@ E@ F@ 4@ 5@ 7@ 8@ :@ ;@ =@ >@  @@ !A@ "@ #@ $@ %@ &@ '@ ( @ )!@ *"@ +#@ ,s@ -W@ .X@ /Y@ 0Z@ 1[@ 2.@ 3/@ 40@ 51@ 62@ 7g@ 8@ 9h@ :@ ;i@ <@ =@ >Q@ ?@ @R@ A@ BS@ C@ DT@ E@ FU@ G@ HV@ I@ JW@ K|@  L@ HM@ @Nv@ O@ P @ Q @ R @ S @ T @ U@ V@ W@ X@ Y@ Z=@ [>@ \?@ ]@@ ^A@ _B@ `C@ aD@ bE@ cF@ dG@ eH@ fI@ gJ@ hK@ iL@ jM@ kN@ lO@ mP@ n3@ o4@ p5@ q6@ r7@ s8@ t9@ u:@ v;@ w<@ xu@ y@ z@ {@ |@ }@ ~@ @ @ @ @ @ @ H@ I@ J@ K@  L@ @M@ N@ O@ P@  Q@  $@  %@  &@  @'@ (@ )@ *@ +@ ,@ -@ @ @ @ @  @ @@ @ @ @  @  @  @  @  @@ @ @ @ @ @ @ @ j@ ek@ el@ e@ e@ e@ e@ e@ e@ e@ e@ @ X@ Y@ Z@ [@ \@ i@ j@ k@ l@ m@ @ @ ^@ @ @ @ @ zz @ @  @ Q@ d@ (d"@ d@ dR@ (d]@ (d ;@ (d*@ (dT@ d@ d@ (d<@ (d Q@ (d@S@ (d F@ ( G@ 8 @ ( @ ( 8@  9@ h :@ h @ 8$ @ 8, @ (f4 @ e< @ eD @ (eL @ eT @ 8e\ @ ed &@ el '@ et (@ e| @ f @ 0e @ 0e @ 8e @ 0e /@ 0e 0@ 0e 1@ 0e@ U@ @ @  @ #@ @ +@  7@  @   @  @  @  @ a@ b@ c@ d@ e@ @ @ @ @ @ @ @ @ @ @ @ @  @ !@ "@ #@ $@ %@ &@ '@ (f@ )g@ *h@ +i@ ,j@ -@ .@ /@ 0@ 1@ 2k@ 3l@ 4m@ 5n@ 6o@ 7@ 8@ 9@ :@ ;@ <p@ =q@ >r@ ?s@ @t@ A@ B@ C@ D@ E@ F@ G@ H@ I@ J@ K@ L@ M@ N@ O@ Pu@ Qv@ Rw@ S@ T@ U@ V@ W@ X@ Y@ Zx@ [y@ \z@ ]@ ^@ _@ `@ a@ b@ c@ d@ ,eW@ f@ g@ h@ i@ j@ k@ l@ m@ n@ o@ p@ q@ r@ s@ t@ u@ v!@ w#@ x%@ y'@ z)@ ~@ @ @ @  @ @@ @ @ @  @  @  @  @  @@ @ @ @ @ @ @ >@ ?@ @@ A@  B@ @C@ D@ E@ F@  =@  G@  H@  I@  @J@ K@ L@ M@ N@ O@ P@ {@ |@ }{@ e~|@ e}@ e@ e@ e@ e@ e@ e@ e@ e=@ >@ ?@ @@ A@ D@ E@ @   @ 4 @  @ ( @ @ d@ (d@ (d@ (d @ d@ @ @  4.@l @ D@ d@(d@ d(@(d)@(d*@(dH@(d I@(d@@(dL@(dN@(dS@ d T@ d @(d F@ d@(dK@(d@ d @(d @(d @(d  @( @( @( @( @( @( 7@( @(" P@($ @(( @(, @(0 Q@`4 @(6 @(f> @(eF @(eN @(eV @(e^ @(ef @(en @(ev @ e~ @(e @(e @e @e@e@e@eG@1@@ 2@ 3@ 4@ 5@ W@6@X@Y@Z@[@\@]@^@_@`@a@@@@@@@@ @!@"@#@$@%@&@'@(@)@*@+@,@-b@.c@/d@0e@1f@2@3@4@5@6@7g@8h@9i@:j@;k@<@=@>@?@@@Al@Bm@Cn@Do@Ep@F@G@H@I@J@K@L@M@N@O@P@Q@R@S@T@Uq@Vr@Ws@X@Y@Z@[@\@]@^@_t@`u@av@b@c@d@e@f@g@h@i@$j@k@l@m@n@o@p@q@r@s@t@u@v@w @z@  {@ |@ }@ ~@  @ @@ @ @ @  @  @  @  @@ @ @ @ @ @ @ x@@yA@zC@{@|@}@@ ~@@w@ex@ey@e@e@e@e@e@e@e@e 4@ @ @ d@ d @( @( @( @( @( @P @  @ @ d@ d@ d@ (d@ (d @  @ ( @ (@ @ VarMeta Var2DataFixedData8FixedMetaL $%&'()*+,-./0123456789:;<=CDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmopxy{Standard8 O,Gd TBkndRsc @2y@2yVarMetaVar2Data FixedData C(@ '' ' \& ' G@ (d @ "d @ (d @ (d@ (dR@ (d@ (d@ "d@ dm@ (dx@ "d @ d@@ (d@  *) ) B* f+ + + >, R- - V/ / 0 1 2 3 3 4 4 5 h5 5 d6 6 7 z8 $9 ~9 0: |: :; |; < < = = >> ? T@ A A D D 6E NF F G zH H I 2J J K K K L L HM M N N N O JP P jQ R RKSKN $T T ZU VK^ `V V C?C@CABCCCDCECCCCCCCCKC LC(MC0N8OC@PCpproach and scope.Identify anizational units.zPlan the Business Systems Analysis and development effort(s) ''' ' \& ' G@ (d @  dm@ (dx@ "d @ d@@ (d@  *) ) B* f+3450: |: :; |; < < = = >> ? T@ A A D D 6E NF F G zH H IVK^ `V V '@LALALA?'@LALALA@'@LALALAA'@LALALAE'@LALALAF'@LALALAG'@LALALAH'@LALALA'@LALALA'@LALALA'@LALALA'@LALALA'@LALALA'@LALALA'@LALALA'@LALALA'@LALALA'@LALALAjZ       8    T    p          6    R   n 0  0  0  0  0 4 0  0 P 0  0 l0 0 00 0 20 0 N0 0 j0 0 0 0 0 00 0 L0 0 h0 0 0 0 0 .0 0 J0 0 f0 0 0 0 0 , 0  0 H!0 !0 d"0 "0 #0 $0 $0 *%0 %0 F&0 &0 b'0 '0 ~(0  )0 )0 (*0 *0 D+0 +0 `,0 ,0 |-0  .0 .0 &/0 /0 B00 00 ^10 10 z20 30 30 $40 40 @50 50 \60 60 x70 80 80 "90 90 >:0 :0 Z;0 ;0 v<0 =0 =0  >0 >0 b &?c ?d ?e ,@f @g @h fAi nBj Bk ZCl Cm XDn Do Dp Et >Hu Hw ,Kx hKy Lz "M| M} O}KO}n V xW X Y Y Z [ [ ] ] ^ _ _Ms 6` zb c d `e :f f gKg g h xi i j k l l ,m Tm m m m $n Nn i j k l l ,m Tm m m m $n NnInitiate - Obtaining agreement on the business requirement and chartering the project BDevelop the Business Requirement 2Charter the Project Team TProject Approved for Planning by Sponsors    zPlan - Creation of the Core work plan and facilitating plans 6Develop the Core Work Plan JOrganize Project & Staff Acquisition$"Execute - Definition of the required work activities to define, construct, pilot, and implement the product scope or selected system functions." nCreate and obtain agreement on the Product DescriptionfCreate and obtain agreement on the Project CharterjDetermine the Project Feasibility and Recommendation:Develop the Project Schedule Devekop the WBS8Develop the Scope StatementXDevelop the Facilitating Plans for Controls HDescribe the Change Management PlanDDescribe the Risk Management Plan`Integrated Plan & Schedule Approved by Sponsors    JAssemble the Integrated Project Plan\Describe the Issue & Decision Management Plan@Describe the Time Tracking Plan@Describe the Communication PlanDescribe the Project standards, Approval process, Document ControlsHDevelop the Integrated Project Plan You should add or remove these as appropriate for your project, an example of an add would be Budget/cost Plan or Training Plan2Perform data conversionsMake data set (files, data bases, tables) ready for the start of production.2Perform environment testEnsure that the changed software operates without disrupting the production environment.:Complete system installation\Put the changed software into production use.>Post Implementation Evaluation 'HConduct a system performance review Evaluate the performance of the changed system in terms of resource use, usability, and the degree to which it met user expectations.{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fcharset0 Tahoma;}{\f1\fswiss\fprq2\fcharset0 Arial;}} \viewkind4\uc1\pard\f0\fs17 Note: This review should be held after sufficient use of the system to provide adequate data for analysis.\par \f1\fs16\par } >Conduct a change impact reviewact reviewEvaluate the user environment to determine if expected benefits were achieved.{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fcharset0 Tahoma;}{\f1\fswiss\fprq2\fcharset0 Arial;}} \viewkind4\uc1\pard\f0\fs17 Note: This review should be held after users have become familiar with the system and after the system has been in use for enough time to accurately determine if it has provided expected benefits. It should not be confused with a project evaluation.\par \f1\fs16\par } XControls - Ensuring the project performance FThese task are the ongoing management of the facilitating plans, if you added budget/cost planning in the plan section, then you should add budget management here4Risk Management - ongoing8Change Management - ongoingfProject Document Review and Organization - ongoignFCommunication Management - OngoingTContract/Procurement Management - ongoingNQuality Assurance Management - ongoing0Time Tracking - ongoingPIssue and Decision Management - ongoing|Close - Evaluate the achievement and turn-over to maintenance &Project Evaluation fPrepare, Conduct, and Present a project evaluationFPlan for Maintenance and Turn-over BCoordinate maintenance Turn-overNProject Complete and Maintenance Ready    >Schedule system implementationSpecify when the system will be introduced into the production environment and when the user will be expected to begin testing and actual use.<Accept the Unmodified Product 'Note: When the modifications are to be performed by in-house or contractor staff rather than by the product vendor s staff, the modification of acquired software should not begin until the base software (the unmodified product) has been accepted.0Where there are multiple vendors products being integrated, acceptance test each product independently. Integration testing is part of the next phase.(Receive the productTake delivery of the hardware and software and install for testing.6Perform acceptance test(s)Exercise the product s components to validate that they perform according to acceptance criteria.BExercise the integrated product..Identify deficiencies.,Correct deficiencies.Accept or reject the components and product (the contract should allow for return of the product if it does not pass the tests).&Modify the Product '>Design new software componentsRIdentify program structures and modules.dProvide a detailed specification for programming.`Program changes to existing software componentsrDetermine the exact location for the changes to be made.DImplement the changes identified..Program new componentsHConstruct or generate new programs.\Unit test (including necessary reprogramming)Ensure that changed and new components perform according to specifications.Note: A walk-through of the unit test plan should be held to ensure that the plan covers all required tests.TImplementation  Transition to Production ' Develop or revise user documentation, operations and support documentation, and trainingDevelop new materials or make changes to existing documentation and training materials.TTrain users, operators, and support staffEnsure that all users, operators, and support staff are able to use the changed system.RSystem test (including necessary rework)Ensure that the changed system(s) operate according to specifications using the plan developed.Ensure that the changed system performs as expected under volume and exception conditions.Note: A walk-through of the system test plan should be held before the test to ensure that the plan covers all required tests.System testing can be broken down into levels of testing to include volume test, usability test, etc. Acceptance testProvide the user and/or sponsor with proof that the changed system works according to expectations.JPrepare for transition to productionEnsure that the production environment (including users, operations, personnel, and support staff) is prepared for the start of production.Install required new hardware, system software, and communications systems.6Note: For applications to be run by centralized computer operations groups, all forms must be filled out and submitted as required by current procedures.Evaluate each proposal with respect to pre-established selection criteria.jIdentify modification requirements for each product.2Conduct benchmark tests.BSelect vendor(s) and product(s).(Negotiate contractsDefine the terms and conditions of acquisition, delivery and support, including acceptance criteria and methods.PObtain management and sponsor approval.Determine or reaffirm overall approach, scope, and project planEnsure that previous estimates and schedules are refined to reflect actual costs and delivery arrangements.Identify any scope changes that have been made as a result of the selection process and contract negotiations.d Execute contract(s) and/or purchase agreement(s)Approve the selection(s), contract terms, costs, and schedules.2Plan for Implementation 'Note: The plan for implementation will need to be adapted if the development/and maintenance is intended to be performed off-site.RNote: All or part of the specifications for modifications, capacity impact, support, etc., referred to in this phase may be determined as part of the selection processdDefine modifications and development requirementsSpecify overall implementation plan approach, i.e big bang, pilot, rolling.Identify the functions that must be added to the selected product.Identify programming changes that must be made to the selected product.Identify non-programming installation requirements (tailoring via parameters and tables).Define impact/interface requirements on other systems and obtain agreements regarding development and/or modification efforts.~Estimate storage, telecommunications, and/or processor impactsDetermine the impact of processing and storage volumes on the hardware (data storage, processor capacity) and on communications resources.hSchedule delivery (ies) and initial installation(s)RSet delivery schedule(s) with vendor(s).@Set site preparation schedules.Set telecommunications line and service installation schedules.8Set installation schedules.vIdentify support and operations roles and responsibilitiesDescribe the operations and support functions (LAN manager, back-up and recovery, technical support, etc.) that will be required.hIdentify staff and organizational responsibilities.|Plan for file/database conversions (including initialization)DIdentify conversion requirements.Determine the way the conversion will be performed (what programs, what controls, etc.).@Schedule the conversion effort.B Develop test strategy and plansEnsure that the test plans for all levels of testing are available to validate the new system and all systems being affected by it.Develop recovery plan if acceptance criteria cannot be met or there is a need to go back.Note: Unit test planning is not included in this activity; it is part of the Modify phase. Testing should first validate the unmodified product and then the product as it is to be installed for use.Develop user/operator training and documentation development planIdentify required user, support staff, and/or operator documentation and training, based on a review of delivered documentation.\Note: Documentation includes Help screen contents, tutorials, training materials, quick reference cards, and manuals. Documentation may be in paper and/or electronic form.8 Review Implementation PlanjEnsure that all required implementation activities have been identified and scheduled. Ensure that there is a defined installation process, indicating who is responsible for what.HReaffirm or revise the project planEnsure that the project plan is accurate, given the information determined during this phase.Feasibility Study  Note: Requirements definition is an extension of the process started in the Feasibility Study. Please see the Feasibility Lifecycle model to determine if all or some of the steps are necessary.* Define Requirements 'When acquiring specialized (e.g., payroll package) application software (as opposed to generic applications such as word processors or spreadsheets), the degree of detail of requirements definition is roughly the same as it is for a development project. When the selection process is to be used as a means to define requirements, these activities will not be performed to the level of detail that is required when the analysis is to result in a full statement of requirements.Specific deliverables depend on the tools and techniques used by the development staff and on the existing data documentation. The deliverables listed below are examples of possible deliverables.In some cases the business performs the majority of these tasks, either formally or informally. If such is the case the project should review, and determine if any additional critical tasks need completed or revised.Identify and describe the business areas to be affected by the new system zDefine in detail the procedures, high-level data requirements, existing reports and documents, roles and responsibilities, and organization of the user areas to be impacted by the product.Describe in detail the business procedures and their data requirements.fDescribe existing computer systems and their data.Ensure that all required data elements have been identified in the data analysis.Ensure that the sources and destinations of the data are known.Identify and prioritize candidates for procedural change and automation.ZDefine data requirements (data model, consisting of entities, data elements, transactions, etc.) Identify and describe the business areas to be affected by the new system Ensure that all entities of consequence to the application area have been identified.Identify and define the data elements to be used, changed, or created (attributes analysis).~Determine the source of data elements in the business process.Identify the business functions and/or existing computer systems that use each data element.p Identify and describe the functions of the new system Identify the functions to be included in the new system and their data requirements.Note: The degree of detail required for this activity and the previous activities depends on the type of product and whether the selection process is to be used as a primary source for requirements.Identify and describe constraints (e.g., critical time restrictions, etc.) Ensure that all operational and delivery requirements (e.g., response times, product delivery deadlines, maximum number of users, volume restrictions, frequency of use, expected product life span, other expectations, etc.) are known.nPrepare and submit Requirements Specification DocumentDocumentation of the requirements that can be validated by users, sponsors, IT management, and developers.Obtain formal user and sponsor concurrence with requirements specificationsEnsure that users, sponsors and IT management authorize continued work on the project.@Acquire the System and Services ':Establish selection criteriaZIdentify the criteria (specific product, vendor, or service characteristics, such as price, number and type of features, stability, etc.) upon which selection will be made.vWeight each criterion with respect to relative importance.Prepare Request(s) for Proposal (RFP) or Request(s) for Information (RFI)*State the requirements and request proposals from prospective vendors (either for information only or for the purpose of making a vendor selection).Provide guidelines for vendors that will enable them to. present proposals that are useful to decision makers.\Establish schedules for receipt of proposals..Set bidders meetings.$Solicit proposals<Identify prospective vendors. Send out RFP s.$Obtain proposals.@Select vendor(s) and product(s)&Meet with vendors.~Interview and/or visit current clients of prospective vendors.y{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fcharset0 Tahoma;}{\f1\fswiss\fprq2\fcharset0 Arial;}} \viewkind4\uc1\pard\f0\fs17 When acquiring specialized (e.g., payroll package) application software (as opposed to generic applications such as word processors or spreadsheets), the degree of detail of requirements definition is roughly the same as it is for a development project. \par \f1\fs16\par \f0\fs17 When the selection process is to be used as a means to define requirements, these activities will not be performed to the level of detail that is required when the analysis is to result in a full statement of requirements.\par \f1\fs16\par \f0\fs17 Specific deliverables depend on the tools and techniques used by the development staff and on the existing data documentation. The deliverables listed below are examples of possible deliverables.\par \f1\fs16\par \f0\fs17 In some cases the business performs the majority of these tasks, either formally or informally. If such is the case the project should review, and determine if any additional critical tasks need completed or revised.\par \f1\fs16\par } p{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fcharset0 Tahoma;}{\f1\fswiss\fprq2\fcharset0 Arial;}} \viewkind4\uc1\pard\f0\fs17 Note: The degree of detail required for this activity and the previous activities depends on the type of product and whether the selection process is to be used as a primary source for requirements.\par \f1\fs16\par }       !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFG[JKLMNOPQRSTUVWXYZ]^d_`abcefijklmnopqrstuvwxyz{|}~'%'  ' '''  ' '''  ' '''  ' ''2   ''>'  ' ''J'  ' ' 'V '  ' ' 'z 5'  ' '#'$!'z  ' '$'&(#'z  ' '% 'z-&'  ' '& 'n%''  ' '' 'b&('  ' '( 'V'$'  ' '-'z/%'  ' '.'-5/'  ' '/'-.-'  ' '0'661   '1'602'  ' '2'-13'  ' '3'-24'  ' '4'-35'  ' '5'-4.'  ' '6'70'  ' ':'-;9' 1 ' ''65'''''''''65''''''''''''''''''' 5''''5'''''''''5'''''''' ''  ' ' '  :'1N ' ' '   '\  ' ' ' 'f  ' '' " 'f  ' '' .'f  ' '' :'p  ' '' F"'p  ' '' R!'p  ' '' ^#"'p  ' '' '  ' '''  ' ''"86'  ' ''"'  ' ''.97'  ' ''.   'j'W5'''k'''''l' 5'''m'''''n''''' m'5'''!n' ''''"o'5'''#p'"''''$q'"''''%r'"''''&s'"'''''t'"''''(u' 5''')v'(5'''*w')''''+x')'''',y'(5'''-z',''''.{',''''/|'(5'''0}'/''''1~'(5'''2'1''''3'(''''6' 5'''7'65'''8'7''''9'65''':'9'''';'65'''<';''''=';''''>'6''''?';''''@'65'''A'@''''E'65'''F'E''''G'E''''H'6''''K@'''''LA'''''MB'''''NC'''''OD'5'''PE'O''''QF'O''''RG'5'''SH'R''''TI'R''''UJ'5'''VK'U''''WL' 5'''XM'W''''YN'W''''ZM'W5'''[N'Z''''\O'Z'''']P'Z''''^Q'Z''''_R'Z''''`S'W5'''aT'`''''bU'W5'''cV'b''''dW'b''''eX'b''''fY'b''''gZ'W5'''h['g''''i\'g''''j]'W5'''k^'j''''l_'j''''m`'j''''na'W5'''ob'n''''pc'n''''qd'W''''td'W5'''ue't''''vf'W''''wf'W5'''xg'w''''yh'W5'''zi'y''''|' ''''}' 5'''~'}'''''}'''''}'''''}'''''}5'''''''''''''''''' '''''!'''''"'''''#'}5'''$'''''%'''''&'''''''''''('}5''')'''''*'}''''*'}5'''+''''','}5'''-'''''.'}5'''/'''''0' 5'''1'5'''2'''''3'''''4'5'''5'''''6'''''7'''''8'''''9'5''':''''';'''''<'''''='5'''>'''''?'''''  ' '' 'b&(  ' '-'z/%'%'  ' '''  ' 'FixedMetaI6"TBkndOutlCode@2y@2yVarMeta>Var2Data C C(C0C8#@CHCPCXC` Ch Cp Cx C CCCCC#CCCCCCCCCCCC C!C "C(#C0$C8%C@&H'CP(CX)C`*Ch+Cp,Cx-C.C/C012C34C5#6C7C8C9C:C;C<C=C?C@CACBC CC(DC0EC8FC@GCHHCPICXJC`KChLCpMCxNCOCPCQCRCSCTCUCVCWCXCYCZC[C\C]C^C`CaCbCcC dC(eC0fC8gC@hCHiCPjCXkC`lChmCpnCxoCpCqCrCsCtCuCvCwCxCyCzC{C|C}C~CCCCCC C(C0C8C@CHCPCXC`ChCpCxCCCCCCCCCCȚCЛC؜CCCCCCCCC C(C0C8C@CHCPCXC`ChCpCxCCCCCCCCCCȻCFixedData!?*FixedMeta@8 29 S2@2yo2yCEdl %@2y@2y* ($$1"@&&@&@& &Gantt Chart@& &Entry6@&'@&(@&*@&@+@&K-@&T$@& `9:BGJ_@&@ @ @ @ #@ "1@&C:\Documents andVarMetaA Var2Data$&B FixedData'nFixedMetaq Settings\pcrites\PMO_PC\role & growth\My PMO Tasks\WIP\SDLC Models\basic_schedule_application_acquisition_sdlc_template_pc.mpp!H5@& `9:BGJ_TJ=@&&9L_r 1"@&&@&g@& &Gantt Chart@& &Entry6@&'@&(@&*@&1+@&j-@&3T$@& |}W(6 "1@&C:\Documents and Settings\pcrites\PMO_PC\role & growth\My PMO Tasks\WIP\SDLC Models\basic_schedule_application_acquisition_sdlc_template_pc.mpp!@&@ @ @5@& |}W(6 %67/1679;@E :KLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqtuvwxyz !"#$%&'()*+,-./01236789:;<=>?@AEFGH @1"@&&@&g@& &Gantt Chart@& &Entry6@&'@&(@&*@&1+@&j-@&3T$@& |}W(6 "1@&C:\Documents and Settings\pcrites\PMO_PC\role & growth\My PMO Tasks\WIP\SDLC Models\basic_schedule_application_acquisition_sdlc_template_pc.mpp!@5@& |}W(6 %67 @&@ @ @ ?@ !!@ 5  @ !"@ Et  @ CMap #-*@2y@2yVarMetarVar2Data)+FixedData,FixedMetasCUdm /@2y@2yVarMetatVar2Data.0FixedData1FixedMetauCVba (4@2y@2yProps h555f@CV_iew,CFilter,CTable,CReport,CUdm,CEdl,CCommandBar,CMap,CVba,CGrouping"@@Arial ArialTasks\WIP\SDLC Models\basic_schedule_application_acquisition_sdlc_template_pc.mpp@5@5Q@ R@S@ T@U@V@W@ X@Y@ Z@[@\@@5@5@@5@@5@5 @5@{00000000-0000-0000-0000-000000000000}LALA'@LALALA@@@@@@j@&Gantt Chart?H0u5zi rjy pj@@xHFG 00hٙ0`` @ @ @ @@@@ @@@@@@@@@@@@@@ @!@  @z# @  @ (hl @ (@ ( n @"(p @"(r @"(@ @"@" @n& @  @ (hl @ (@ ( @ @n$ @  @ (hl @ (@ ( @ @v* @  @ (hl @ (@ ( n @#(@  @# @p, @  @ (hl @ (@ ( n @'(@  @@ @ ( @ (hl @ (@ ( n @&(r @&(t @&(x @&(| @&( @&( @&( @&( ;@&(@ :@&E@8N @) @)D      @nk @  @ (hl @ (@ ( @       @    x  @n @  @ (hl @ (@ ( @ CTable3>6o2yo2yVarMetav Var2Data57wFixedData8zn 4!"#@ !"$@ !"/@   1@   Task Name&Entryn N J F F %@"@  c @" &Entry @" &All TasksFixedMeta|CV_iew;o2yo2yVarMeta}(Var2Data:<~  @"dD @"@   ! dd@ X!Standard #@ $@ 1@  #@ $@ )@ w@ #@ #@ #@ #@ $@ #@ $@ #@ $@ #@ #@  )@ w@  #@ $@  #@ $@  #@ #@  #@ # @ @ #@ $@ TaskSplitProgressMilestoneSummaryRolled Up TaskRolled Up SplitRolled Up MilestoneRolled Up ProgressExternal TasksProject SummaryExternal MilestoneDeadline*Group By Summary@" &No Group8@"{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl {\f0\fswiss\fprq2\fcharset0 Arial;}} {\colortbl ;\red0\green0\blue0;} \uc1\pard\qc\tx720\cf1\f0\fs16 Page &P\par } {\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl {\f0\fswiss\fprq2\fcharset0 Arial;}} {\colortbl ;\red0\green0\blue0;} \uc1\pard\tx720\cf1\f0\fs16 Project: &p\par Date: &D\par } &Gantt Chartzect <#: &DdFixedData=zFixedMetaCFilter9H@o2yo2yVarMeta Var2Data?AFixedDataBnFixedMetaCReportEo2yo2ytasks&All Tasksnx<VarMetaVar2DataDFFixedDataGFixedMetaCGroupingCMJo2yo2yVarMeta(Var2DataIKxFixedDataL88&No Group&No GroupnFixedMeta"CCommandBarOo2yo2yVarMetaFixedDataNPFixedMetaQ2a400000_ffffffff$Props9CompObjRTqTSBCBB @59,0,2000,0224@59,0,2000,0224@ @5C:\Documents and Settings\pcrites\PMO_PC\role & growth\My PMO Tasks\WIP\SDLC Models\basic_schedule_application_acquisition_sdlc_template_pc.mpp@5@5Q@ R@S@ T@U@V@W@ X@Y@ Z@[@\@@5@5@@5@@5@5 @5 @58Department of Human :tOMicrosoft Project 9.0MSProject.MPP9MSProject.Project.99qOh+'0l px , @ L XdBasic Project Plan TemplateBasic Project Plan Templateasi2Basic Project Plan Template, Project Schedule, MSPasiasi27i MSProjectec@NSI@SummaryInformation(UDocumentSummaryInformation86gH@.y՜.+,D՜.+, X`l|  kDHS-PMO  Fri 6/24/05 Fri 6/24/051d?0h$0.000%0% StartFinish DurationWorkCost % Complete% Work Complete'7GSgs % CompleteCost DurationFinishStartWork% Work Complete0%o % Completel$0.00leCostle1d? Durationel@lyFinishn@dxStartn0hrWorkn0%k% Work Complete Services