1 Technical Risks Requirements Specifications Technology Complexity Interfaces Performance Quality Safety Security 2 External Risks Contractors Sub-contractors Suppliers Regulatory Market Customer Weather 3 Organizational Risks Project dependencies Resources Funding Prioritization Org. Breakdown Str Resp. Assigned Matrix 4 Proj Mgmt Risks Estimating Planning Controlling Resource Utilization Communication Information Health/Safety RISK REGISTER Project Name: Description of Risks Identified Risks/Triggers Impact (+ ve or - ve) on Project Objectives Environment 5 Commercial Risks Contractual Financial Regulatory Consents Reputation Project Phase DELIVERABLES CEO Major deliverable/WP deliverables Responsibility Assignment Matrix - RAM NAME OF THE PROJECT Control Qualitative Analysis TIME QUALITY SCOPE I/E VH/H/M/L/VL Risk Owner Project Manager: Impact (+ ve or - ve) on Project Objectives Project Manager A B C D E PERMORMING ORGANIZATION Sr.Mgmt % P Consequence Risk %P x I Thresholds Time period (hr/dy) Cost/Res hrs Date of Review: Risk Buffer Ph-1 I/c Ph-2 I/c Ph-3 I/c Ph-4 I/c Function Hd-1 Function Heads PERMORMING ORGANIZATION Phase Incharges Priority/ Resource Buffer Ranking EV VAC-1 VAC-2 VAC-3 CPI SPI Date of Review: Risk Buffer TRENDS CEO Sr. Proj Function Hd-2 Function Hd-3 mgmt mgr Function Heads PERMORMING ORGANIZATION Function Heads Origination Organization List of potential Common Risk Responses Causes Positive Risk Strategies Avoid/Transfer/Mitigate/Accept Date of Review: Contingency Plans Phase Team Members Incharges Function Heads Origination Organization Negative Risk Strategies Avoid/Share/EnhanceAccept STATUS REPORT & ACTION PLAN Date of Review: Contingency Plans Performing Organization Team Members Fallback (backup) Plan Workaround Plan Results Results Date of Review: WP-D DAY A B C Total %C EV AC Rate M.Hr. M.Hr. M.Hr. M.Hr. A.MHr. Rs. 1 8 8 75% 6 8 2 8 8 3 8 10 18 4 8 10 6 24 5 8 10 6 24 6 10 6 16 7 10 6 16 8 6 6 9 6 6 10 6 6 BAC= Planned %P 6.1% SV= EV-PV -2 CV= EV-AC -2 Completed %C 4.5% SPI= EV/PV 0.75 CPI= EV/AC 0.75 SV% SV/PV -25% CV% CV/EV -33% VAC-1 BAC-EAC VAC-2 BAC-EAC PHASE -A: BACph PVph WP BAC %P PV %C EV AMHr A 500 80% 400 60% 300 375 500 400 B 600 75% 450 50% 300 325 1100 850 C 450 50% 225 45% 202.5 250 1550 1075 D 132 6.1% 8 4.5% 6 8 1682 1083 E 400 2082 F 350 2432 G 300 BAC= 2732 Actuals Activities Cummulative Planned %Pph 39.6% SV= EV-PV -274.5 CV= EV-AC -149.5 Completed %Cph 29.6% SPI= EV/PV 75% CPI= EV/AC 84% SV% SV/EV -25% CV% CV/EV -18% VAC-1 BAC-EAC VAC-2 BAC-EAC PROJECT -A: BACp PHASE PV %Pph PVp %Cph EV AMHr A 2732 39.6% 1083 29.6% 809 958 2732 B 3550 6282 C 2880 9162 D 3850 13012 Planned %P 8.3% SV= EV-PV -274.5 CV= EV-AC -149.5 Completed %C 6.2% SPI= EV/PV 0.747 CPI= EV/AC 0.844 SV% SV/PV -25% CV% CV/EV -18% VAC-1 BAC-EAC VAC-2 BAC-EAC Calculating Risk in Project Network based on PERT calculation ACTIVITY Predecessor Optimistic Most LikelyPessimistic Time EstimateVariance Std Dev Start (o+4m+p)/6 A Start 10 22 22 20 4 2 B Start 20 20 20 20 0 0 C Start 4 10 16 10 4 2 D a 2 14 32 15 25 5 E b,c 8 8 20 10 4 2 Cummulative F b,c 8 14 20 14 4 2 G b,c 4 4 4 4 0 0 H c 2 12 16 11 5.4 2.33 I g,h 6 16 38 18 28.4 5.33 J d,e 2 8 14 8 4 2 Finish j,i,f 43 33 5.745 Assume Project Manager has commited 50 days to the customer, what are the chances of meeting the dead lines? We need to calculate the value of 'Z' Z = (D-u)/Std Deviation D = Desired Project Completion Date = 50 days u = The critical time of the project = 43 days Z= 1.22 Std Deviation of the critical path = 5.745 Z = The number of Std Deviations of a normal distribution Refer Table A below, The probability Z of 1.22 (column 1.2 and .02) occurs .8888 or say 89% We can also calculate backwards: What deadline is consistent with a 95% probability of on-time completion? Here the 'Z' value associated with 0.95 is 1.645 We know that u is 43 days and Std Deviation is 5.745 D = u + Std Dev ( correspondence value of Z) 52.45 What are the chances that the non-critical Path c-h-I will make the project late? Now D = 43, so we have Z= (43-39)/6.155 = 0.65 Now Z = .65 is associated with 0.74 of being on time, or 1-.74 = 0.26 chances of delaying the project Duration Variance Std Dev Project Duration = Refering non-critical path C, H, I 39 37.9 6.155 Z= 0.65 Assuming that these two paths (a-b-j and c-h-I) are independent. What is the probability that both paths will be complated on time. The probability is 0.50 x 0.74 = 0.37 TABLE - A: Cummulative (Single Tail) Probabilities of the Normal Probability Distribution Z 0.00 0.01 0.02 0.03 0.04 0.05 0.06 0.07 0.0 0.5000 0.5040 0.5080 0.5120 0.5160 0.5199 0.5239 0.5279 0.1 0.5398 0.5438 0.5478 0.5517 0.5557 0.5596 0.5636 0.5675 0.2 0.5793 0.5832 0.5871 0.5910 0.5948 0.5987 0.6026 0.6064 0.3 0.6179 0.6217 0.6255 0.6293 0.6331 0.6368 0.6406 0.6443 0.4 0.6554 0.6591 0.6628 0.6664 0.6700 0.6737 0.6772 0.6808 0.5 0.6915 0.6950 0.6985 0.7019 0.7054 0.7088 0.7123 0.7157 0.6 0.7257 0.7291 0.7324 0.7357 0.7389 0.7422 0.7454 0.7486 0.7 0.7580 0.7611 0.7642 0.7673 0.7704 0.7734 0.7764 0.7794 0.8 0.7881 0.7910 0.7939 0.7967 0.7995 0.8023 0.8051 0.8078 0.9 0.8159 0.8186 0.8212 0.8238 0.8264 0.8289 0.8315 0.8340 1.0 0.8413 0.8438 0.8461 0.8485 0.8508 0.8531 0.8554 0.8577 1.1 0.8643 0.8665 0.8686 0.8708 0.8729 0.8749 0.8770 0.8790 1.2 0.8849 0.8869 0.8888 0.8907 0.8925 0.8944 0.8962 0.8980 1.3 0.9032 0.9049 0.9066 0.9082 0.9099 0.9115 0.9131 0.9147 1.4 0.9192 0.9207 0.9222 0.9236 0.9251 0.9265 0.9279 0.9292 1.5 0.9332 0.9345 0.9357 0.9370 0.9382 0.9394 0.9406 0.9418 1.6 0.9452 0.9463 0.9474 0.9484 0.9495 0.9505 0.9515 0.9525 1.7 0.9554 0.9564 0.9573 0.9582 0.9591 0.9599 0.9608 0.9616 1.8 0.9641 0.9649 0.9656 0.9664 0.9671 0.9678 0.9686 0.9693 1.9 0.9713 0.9719 0.9726 0.9732 0.9738 0.9744 0.9750 0.9756 2.0 0.9772 0.9778 0.9783 0.9788 0.9793 0.9798 0.9803 0.9808 2.1 0.9821 0.9826 0.9830 0.9834 0.9838 0.9842 0.9846 0.9850 2.2 0.9861 0.9864 0.9868 0.9871 0.9875 0.9878 0.9881 0.9884 2.3 0.9893 0.9896 0.9898 0.9901 0.9904 0.9906 0.9909 0.9911 2.4 0.9918 0.9920 0.9932 0.9925 0.9927 0.9929 0.9931 0.9932 2.5 0.9938 0.9940 0.9941 0.9943 0.9945 0.9946 0.9948 0.9949 2.6 0.9953 0.9955 0.9956 0.9957 0.9959 0.9960 0.9961 0.9962 2.7 0.9965 0.9966 0.9967 0.9968 0.9969 0.9970 0.9971 0.9972 2.8 0.9974 0.9975 0.9976 0.9977 0.9977 0.9978 0.9979 0.9979 2.9 0.9981 0.9982 0.9982 0.9983 0.9984 0.9984 0.9985 0.9985 3.0 0.9987 0.9987 0.9987 0.9988 0.9988 0.9989 0.9989 0.9989 3.1 0.9990 0.9991 0.9991 0.9991 0.9992 0.9992 0.9992 0.9992 3.2 0.9993 0.9993 0.9994 0.9994 0.9994 0.9994 0.9994 0.9995 3.3 0.9995 0.9995 0.9995 0.9996 0.9996 0.9996 0.9996 0.9996 3.4 0.9997 0.9997 0.9997 0.9997 0.9997 0.9997 0.9997 0.9997 Projects 6 6 6 6 6 6 6 6 A B C D E F G H Total Hrs. Experience Verification - Reporting Months BACKUP DOCUMENT BEFORE FILLING EXPERIENCE VERIFICATION FORM (6 years if graduate; and 8 years if non-graduate from the date you apply for PMP certification) PROJECTS A B C D E F G List major deliverables for each project work that you personally undertook: How to prepare for PMP certification: Assumption: Study @ 2 effort hrs per day only week # 1 Definitions - PMBOK 2 Understanding Input-Output relationship : refer to PMCC Handouts 3 Mug-up Input-Output relationship : refer to PMCC Handouts 4 Understand Generic Management & Project Initiation 5 Understand Project Scope mgmt 6 Understand Project Time & Cost mgmt 7 Understand Project Quality, HR and Communication mgmt 8 Understand Project Risk mgmt & perform PMKQ practice GO FOR PMP CERTIFICATION Controlling Closing Proj Total hrs: Initiation Planning Execution PV EV AC M.Hr. M.Hr. M.Hr. 8 6 8 16 34 58 82 98 114 120 126 132 ETC= BAC-EV 126 To complete balace work EAC-1 AC+ETC 134 To complete total work EAC-2 BAC/CPI 176 To complete total work -2 -44 EVph ACph 300 375 600 700 802.5 950 808.5 958 Cummulative Cummulative ETC= BAC-EV 1924 To complete balace work EAC-1 AC+ETC 2882 To complete total work EAC-2 BAC/CPI 3237 To complete total work -149.5 -505.18 PVp EVp ACp 1083 808.5 958 ETC= BAC-EV 12204 To complete balace work EAC-1 AC+ETC 958 To complete total work EAC-2 BAC/CPI 15418 To complete total work 12054 -2406.1 Cummulative Assume Project Manager has commited 50 days to the customer, what are the chances of meeting the dead lines? D = Desired Project Completion Date = 50 days u = The critical time of the project = 43 days Std Deviation of the critical path = 5.745 Z = The number of Std Deviations of a normal distribution Assuming that these two paths (a-b-j and c-h-I) are independent. What is the probability that both paths will be complated on time. TABLE - A: Cummulative (Single Tail) Probabilities of the Normal Probability Distribution 0.08 0.09 0.5319 0.5359 0.5714 0.5753 0.6103 0.6141 0.6480 0.6517 0.6844 0.6879 0.7190 0.7224 0.7517 0.7549 0.7823 0.7582 0.8106 0.8133 0.8365 0.8389 0.8599 0.8621 0.8810 0.8880 0.8997 0.9015 0.9162 0.9177 0.9306 0.9319 0.9429 0.9441 0.9535 0.9545 0.9625 0.9633 0.9699 0.9706 0.9761 0.9767 0.9812 0.9817 0.9854 0.9857 0.9887 0.9890 0.9913 0.9916 0.9934 0.9936 0.9951 0.9952 0.9963 0.9964 0.9973 0.9974 0.9980 0.9981 0.9986 0.9986 0.9990 0.9990 0.9993 0.9993 0.9995 0.9995 0.9996 0.9997 0.9997 0.9998 @1200 hr/y Total 6 6 6 6 7200 hrs 5040 30% effective Utilization 4680 35% effective Utilization Total 4500 37.5% effective Utilization Experience Verification - Reporting Months BACKUP DOCUMENT BEFORE FILLING EXPERIENCE VERIFICATION FORM (6 years if graduate; and 8 years if non-graduate from the date you apply for PMP certification) PROJECTS H hrs List major deliverables for each project work that you personally undertook: Assumption: Study @ 2 effort hrs per day only Understanding Input-Output relationship : refer to PMCC Handouts Mug-up Input-Output relationship : refer to PMCC Handouts APPLY FOR PMP CERTIFICATION Understand Project Quality, HR and Communication mgmt Understand Project Risk mgmt & perform PMKQ practice 1 IT PROJECT 2 BUSINESS OPPORTUNITY 3 INITIATE BUSINESS OPPORTUNITY 4 Start Project 5 Create Opportunity/Problem Statement 6 Develop Initial Project Team 7 GATHER SUPPORTING DATA 8 Gather High Level Business Requirements 9 Conduct Management/Business Survey 10 Analyze Survey Findings and Business Functions 11 Develop High Level Scope, Objectives, and Constraints 12 ANALYZE CURRENT SYSTEM 13 Assess Current System Capacity/Functionality 14 Assess Current System Cost/Benefit 15 ASSESS ALTERNATIVES 16 Define General Systems Requirements 17 Define Potential Build vs. Buy Alternatives 18 Evaluate Technical Implications of Alternatives 19 Estimate Cost/Benefit/Risk of Alternatives 20 Compare Potential Solutions with Project Objectives 21 PRESENT ALTERNATIVES 22 Review Findings on Alternatives with Project Sponsor 23 Obtain Sponsor Approval 24 Determine Project Priority 25 DEVELOP PROJECT PLAN 26 Finalize Project Definition/Scope Statement 27 Determine Project Staffing Needs - User and Technical 28 Develop Project Plan/Schedule 29 FUNCTIONAL REQUIREMENTS AND LOGICAL DESIGN 30 DESIGN FUNCTIONAL SYSTEM 31 Conduct JAD to Define and Document Detailed Functional Requirements 32 Develop Conceptual Design 33 Document Business Process Flows 34 Define Logical I/O Format 35 Define Processing Requirements 36 Define Logical Data Structures 37 Develop Screen Dialogs 38 Develop Overall System Flow 39 Identify Acceptance Testing Criteria 40 Hold Design Walkthru with User and Technical Analyst(s) 41 PREPARE USERS DOCUMENTS 42 Determine User Operations/Data Entry Procedures 43 Determine User Training & Education Requirements 44 Identify Security Requirements 45 Prototype Business Process SAMPLE PROJECT FOR DEVELOPING PROJECT PLAN For a typical IT Project, the deliverables upto level-2 has been given below. You are required to eloborate further 2 levels of deliverables upto "Work Packages". You are then required to list down the activities for each Work Package. Inter-Link Work Packages . 46 REVIEW LOGICAL DESIGN 47 Prepare Presentation for Project Sponsor 48 Obtain Sponsor Approval of Logical Design 49 INTERNAL REQUIREMENTS AND PHYSICAL DESIGN 50 DEVELOP DETAILED SPECIFICATIONS 51 Outline Programs, Files, Jobs, Tables 52 Identify Data Elements 53 Define/Document Program Specifications 54 Define/Document Job Specifications 55 Define/Document File Specifications 56 Define/Document Table Specifications 57 Define/Document Detailed Screen Layout and Report Specifications 58 Define/Document Security Specifications 59 Hold Specification Walkthru with Technical Analyst(s) 60 FINALIZE TECHNICAL REQUIREMENTS 61 Define System Control Considerations 62 Define System Backup/Recovery Needs 63 Determine Data Retention Requirements 64 Review Memory Requirements 65 Review Peripheral Equipment 66 Review Workstation Requirements 67 Review Disk Space Requirements 68 Review CPU Requirements 69 Determine Technical Training Requirements 70 REVIEW PHYSICAL DESIGN 71 Prepare/Conduct Management Review of Physical Design 72 Obtain Sponsor Approval of Physical Design 73 CODING AND TESTING 74 ESTABLISH PROGRAM TEST STRATEGY 75 Review Physical Testing Environment 76 Schedule and Prioritize Test Shifts 77 Establish Test File Sources 78 Establish Test Sequence 79 Determine Software Testing Requirements 80 Determine Operations Requirements 81 Test Strategy Complete 82 CODE AND UNIT TEST PROGRAMS 83 Code and Unit Test Required Program #1 84 Code and Unit Test Required Program #2 85 Code and Unit Test Required Program #3 86 Code and Unit Test Required Program #4 87 Code and Unit Test Required Program #5 88 Code and Unit Test Required Program # n 89 OUTLINE TEST SPECIFICATIONS 90 Develop System Test Plan 91 Develop Stress Test Plan 92 Develop Acceptance Test Plan 93 Develop Parallel Test Plan 94 SYSTEM TEST 95 Execute System Tests 96 Perform Stress Testing 97 Review Results with User and Operations 98 Complete System Test 99 ACCEPTANCE TEST 100 Finalize Acceptance Test Criteria 101 Review Acceptance Test Plan 102 Perform Acceptance Test 103 Complete Acceptance Test 104 PARALLEL TEST 105 Review Parallel Test Plan 106 Perform Parallel Test 107 Complete Parallel Test 108 IMPLEMENTATION 109 PLAN AND COMMIT COMPUTER SERVICES 110 Prepare Site in User Location(s) 111 Order Computer Supplies 112 Review Test Controls 113 Review Site Operation 114 Review Personnel Requirements 115 Establish System Security 116 SYSTEM DOCUMENTATION 117 Complete Operations Documentation 118 Complete Program Documentation 119 Complete User Guide 120 PREPARE ORGANIZATION & FINALIZE USER PROCS 121 Finalize User Documentation 122 Finalize Data Input Procedures 123 Finalize Data Output Documents 124 Review Manual User Procedures 125 Review Business Recovery Plans 126 Perform Hardware Testing 127 COMPLETE USER EDUCATION AND TRAINING 128 Train Trainers 129 Train Installation Team 130 Train User Personnel 131 INVENTORY SOFTWARE/REVISE DOCUMENTATION 132 Prepare Software Libraries 133 Build Documentation Library 134 DEVELOP SYSTEM CONVERSION REQUIREMENTS 135 Develop Conversion Plan/Schedule 136 Design Conversion Programs/Procedures 137 Hold Conversion Strategy Walkthru 138 Execute Mock Conversions 139 Execute Data Conversion 140 Data Conversion Complete 141 CUTOVER 142 Set Up Environment 143 Install Data Bases 144 Move from Test to Production 145 Monitor and Certify the System 146 OBTAIN SPONSOR SIGN-OFF 147 Secure Sponsor Sign-off on System 148 Secure Sponsor Sign-off on User Guides 149 INITIATE NEW SYSTEM OPERATION 150 Transfer Operational Responsibility to User 151 Establish Change Control Procedures 152 Transfer System Responsibility to Technical Maintenance Function 153 System Implementation Complete 154 CLOSE DOWN OLD SYSTEM 155 Establish Programs Retention Period 156 Archive System Documentation 157 Archive Master Data Files 158 Re-Allocate Computer Resources 159 Archive Programs 160 CONDUCT EVALUATION 161 Develop/Distribute Customer Questionnaire 162 Evaluate Customer Responses 163 Hold Lessons Learned Meeting 164 End Project 165 PROJECT ADMINISTRATION 166 Project Administration 167 Project Planning and Control 168 Project Meetings 169 Staff Administration - Non-Project Related 170 Staff Activities 171 Staff Meetings 172 Production Support and Maintenance WBS ID WBS DESCRIPTION 1 Power & Utilities Simulation Model - PWUS 1.1 REQUIREMENTS PHASE 1.1.1 Discover User NEEDS 1.1.1.1 Prepare Preliminary User Needs / Requirements 1.1.1.1.1 Establish Project Objectives & Management Concerns 1.1.1.1.2 Get functional requirements 1.1.1.1.3 Get information on external interface 1.1.1.1.4 Get operating environment requirements 1.1.1.1.5 Get performance requirements 1.1.1.1.6 Get standard requirements 1.1.1.1.7 Get special user requirements 1.1.1.1.8 Prepare Prototype 1.1.1.1.9 Evaluate Prototype 1.1.1.1.10 Conduct feed back session 1.1.1.1.11 Document User Needs and Preliminary Requirements 1.1.1.2 Technically Analyze Requirements 1.1.1.2.1 Develop process model 1.1.1.2.2 Develop logical data 1.1.1.2.3 Verify Requirements 1.1.1.2.4 Set up data dictionary 1.1.1.3 Obtain Approval of Customer needs and requirements 1.1.2 Prepare Preliminary Project Planning 1.1.2.1 Develop Preliminary Project Plan 1.1.2.1.1 Prepare Preliminary Scope statement 1.1.2.1.2 Prepare WBS upto level-1 of project life cycle 1.1.2.1.3 Prepare Milestone Chart 1.1.2.1.4 Prepare RAM, Comm Plan, Sch., Scope, Cost & Risk Mgmt Plan 1.1.2.1.5 Prepare change control system 1.1.2.1.6 Prepare Resource estimation and project schedule 1.1.2.1.7 Prepare Preliminary Project Plan 1.1.2.2 Prepare High-level project Cost and Schedule Budget 1.1.2.2.1 Estimate high-level project cost and prepare budget 1.1.2.2.2 Prepare high-level Milestone Schedule of project life cycle 1.1.2.2.3 Document project constraints and assumptions 1.1.2.3 Obtain Preliminary Project Plan Approval 1.1.3 Finalize Project Requirements 1.1.3.1 SRS finalization 1.1.3.1.1 Prepare SRS 1.1.3.1.2 Obtain Approval of SRS 1.1.3.2 Test Case Preparation 1.1.3.2.1 Prepare Test case 1.1.3.2.2 Obtain Approval of Test case 1.1.3.3 Obtain Customer Approval 1.2 DESIGN PHASE 1.2.1 Standards & Checklists Preparation 1.2.1.1 Top Down Design Standards & Checklists 1.2.1.1.1 Top Down Design Standards & Checklists Preparation 1.2.1.1.2 Top Down Design Standards & Checklists Review 1.2.1.1.3 Top Down Design Standards & Checklists Fixation 1.2.1.1.4 Top Down Design Standards & Checklists Verification 1.2.1.1.5 Top Down Design Standards & Checklists SQA Review 1.2.1.1.5 Top Down Design Standards & Checklists Baseline and Release 1.2.1.2 Coding Standards & Checklists 1.2.1.2.1 Coding Standards & Checklists Preparation 1.2.1.2.2 Coding Standards & Checklists Review 1.2.1.2.3 Coding Standards & Checklists Fixation 1.2.1.2.4 Coding Standards & Checklists Verification 1.2.1.2.5 Coding Standards & Checklists SQA Review 1.2.1.2.6 Coding Standards & Checklists Baseline and Release 1.2.1.3 Math Modeling Standards & Checklists 1.2.1.3.1 Math Modeling Standards & Checklists Preparation 1.2.1.3.2 Math Modeling Standards & Checklists Review 1.2.1.3.3 Math Modeling Standards & Checklists Fixation 1.2.1.3.4 Math Modeling Standards & Checklists Verification 1.2.1.3.5 Math Modeling Standards & Checklists SQA Review 1.2.1.3.6 Math Modeling Standards & Checklists Baseline and Release 1.2.1.4 Graphics Standard & Checklists 1.2.1.4.1 Graphics Standards & Checklists Preparation 1.2.1.4.2 Graphics Standards & Checklists Review 1.2.1.4.3 Graphics Standards & Checklists Fixation 1.2.1.4.4 Graphics Standards & Checklists Verification 1.2.1.4.5 Graphics Standards & Checklists SQA Review 1.2.1.4.6 Graphics Standards & Checklists Baseline and Release 1.2.2 Top Down Design 1.2.2.1 TDD Preparation 1.2.2.2 TDD Review 1.2.2.3 TDD Fixation 1.2.2.4 TDD Verification 1.2.2.5 SQA Review 1.2.2.6 TDD Baseline and Release 1.2.3 Math Modeling 1.2.3.1 MMN Preparation 1.2.3.2 MMN Review 1.2.3.3 MMN Fixation 1.2.3.4 MMN Verification 1.2.3.5 SQA Review 1.2.3.6 MMN Baseline and Release 1.3 DEVELOPMENT PHASE 1.3.1 Coding 1.3.1.1 Utility Boiler Coding 1.3.1.1.1 Coding 1.3.1.1.2 Code Review 1.3.1.1.3 Code review Fixation 1.3.1.1.4 Code Review Verification 1.3.1.1.5 SQA Review 1.3.1.1.6 Code Baseline and Release 1.3.1.2 Pressure Flow Network Coding 1.3.1.2.1 Coding 1.3.1.2.2 Code Review 1.3.1.2.3 Code review Fixation 1.3.1.2.4 Code Review Verification 1.3.1.2.5 SQA Review 1.3.1.2.6 Code Baseline and Release 1.3.1.3 Wet Gas Compressor Coding 1.3.1.3.1 Coding 1.3.1.3.2 Code Review 1.3.1.3.3 Code review Fixation 1.3.1.3.4 Code Review Verification 1.3.1.3.5 SQA Review 1.3.1.3.6 Code Baseline and Release 1.3.1.4 Turbine Coding 1.3.1.4.1 Coding 1.3.1.4.2 Code Review 1.3.1.4.3 Code review Fixation 1.3.1.4.4 Code Review Verification 1.3.1.4.5 SQA Review 1.3.1.4.6 Code Baseline and Release 1.3.1.5 Surface Condenser Coding 1.3.1.5.1 Coding 1.3.1.5.2 Code Review 1.3.1.5.3 Code review Fixation 1.3.1.5.4 Code Review Verification 1.3.1.5.5 SQA Review 1.3.1.5.6 Code Baseline and Release 1.3.2 Configuration 1.3.2.1 Instructor Station Confugration 1.3.2.1.1 Instructor Station Configuration Preparation 1.3.2.1.2 Instructor Station Configuration Review 1.3.2.1.3 Instructor Station Configuration Fixation 1.3.2.1.4 Instructor Station Configuration Verification 1.3.2.1.5 Instructor Station Configuration Baseline and Release 1.3.2.2 Operator Station Configuration 1.3.2.2.1 Operator Station Configuration Preparaton 1.3.2.2.2 Operator Station Configuration Review 1.3.2.2.3 Operator Station Configuration Fixation 1.3.2.2.4 Operator Station Configuration Verification 1.3.2.2.5 Operator Station Configuration Baseline and release 1.3.2.3 Graphics Development 1.3.2.3.1 Graphics Preparation 1.3.2.3.2 Graphics Review 1.3.2.3.3 Graphics Fixation 1.3.2.3.4 Graphics Verification 1.3.2.3.5 Graphics Baseline and Release 1.3.3 Unit Testing 1.3.3.1 Utility Boiler Unit Testing 1.3.3.1.1 Testing 1.3.3.1.2 Bug Fixing 1.3.3.1.3 Verification 1.3.3.2 Pressure Flow Network Unit Testing 1.3.3.2.1 Testing 1.3.3.2.2 Bug Fixing 1.3.3.2.3 Verification 1.3.3.3 Wet Gas Compressor Unit Testing 1.3.3.3.1 Testing 1.3.3.3.2 Bug Fixing 1.3.3.3.3 Verification 1.3.3.4 Turbine Unit Testing 1.3.3.4.1 Testing 1.3.3.4.2 Bug Fixing 1.3.3.4.3 Verification 1.3.3.5 Surface Condenser Unit Testing 1.3.3.5.1 Testing 1.3.3.5.2 Bug Fixing 1.3.3.5.3 Verification 1.3.4 User Manual Preparation 1.3.4.1 Preparation of User Manual 1.3.4.1.1 Review User manual 1.3.4.1.2 Fixation User manual 1.3.4.1.3 Verification user manual 1.3.4.1.4 SQA Review 1.3.4.1.5 Conversion of User Manual to Online Help 1.3.4.1.6 Review of Online Help 1.3.5 Integrating Testing 1.3.5.1 Integrated Dynamic Testing 1.3.5.1.1 Testing 1.3.5.1.2 Bug Fixing 1.3.5.1.3 Verification 1.3.6 Acceptance / Domain Testing 1.3.6.1 Acceptance / Domain Testing 1.3.6.1.1 Testing 1.3.6.1.2 Bug Fixing 1.3.6.1.3 Verification 1.4 PROJECT MANAGEMENT 1.4.1 Project EV Progress Meetings 1.4.1.1 Project & Risk Review Meetings 1.4.1.1.1 Project Kick-off meeting 1.4.1.1.2 Project Review Meeting #1 1.4.1.1.3 Project Review Meeting #2 1.4.1.1.4 Project Review Meeting #3 1.4.1.1.5 Project Review Meeting #4 1.4.1.1.6 Project Review Meeting #5 1.4.1.1.7 Project Review Meeting #6 1.4.1.1.8 Project Review Meeting #7 1.4.1.2 Milestone Meetings 1.4.1.2.1 Completion of Presales and Planning 1.4.1.2.2 Completion of Requirement PUSW SRS 1.4.1.2.3 Release of PUWS 1.4.1.2.4 Completion of Acceptance (PUWS) 1.4.2 Training 1.4.2.1 Domain Training 1.4.2.2 Domain Training 1.4.3 Project Metrics Report 1.4.3.1 December Project Meterics Report 1.4.3.2 January Project Meterics Report 1.4.3.3 February Project Meterics Report 1.4.3.4 March Project Meterics Report 1.4.4 Release Audit 1.4.4.1 Release to Acceptance 1.4.4.2 Product Release Establish Activity dependencie s. Identify activity attributes . Identify activity risks . Estimate Activity duration in Eff hrs Estimate Activity Resource reqmts. Identify WP Risks .