Develop a network diagram and identify the critical path. You may use Excel to develop the network diagram or draw this by hand. Create a schedule (gantt chart) using a scheduling tool such as Project Libre, MS Project or Project Plan 365 or similar. You may not use Excel for the development of the schedule and your schedule should demonstrate understanding of key scheduling tools, such as relationships, lags and leads, based on the activities list in Appendix 2. You have one new developer and one very experienced developer who may work on B3 File Validation module and B4 Desktop validation module. Assume that the very experienced developer can achieve 110% productivity, while the new developer is only able to achieve 45% productivity as he will need to ask a lot of questions. Apply threepoint estimation to B3 File Validation module and B4 Desktop validation module, The current estimations were based on previous similar projects (analogous estimates) and can be applied as the most likely duration. You have very experienced staff working on each remaining module so can safely accept the estimates based on similar previous development projects. Adjust your schedule to comply with the requirement to deliver the project within six weeks (you will note that the activities list has a total duration of eight weeks) so it is expected that you will apply and justify tools to compress the schedule appropriately. Create the Schedule management plan and include the components listed above within your schedule management plan

1 PCP DATA COLLECTION AND VALIDATION PROJECT Predecessor 2 A INFRASTRUCTURE 3 A1 confirm infrastructure requirements 5 days 4 A2 confirm infrastructure availability 5 days 3 5 A3 set up logins and passwords 3 days 4 6 A4 test logins and passwords 2 days 5 7 B DATA COLLECTION AND VALIDATION MODULES 8 B1 confirm requirements and process flow 3 days 3SS 9 B2 File pickup module 10 B2.1 create folders for errors and validation records 2 days 8 11 B2.2 develop batch header test code 3 days 10 12 B2.3 develop error log 1 day 11 13 B2.4 create emails 2 days 12 14 B2.5 system test 5 days 13 15 B2.6 release to test 0 days 14 16 B3 File validation module 17 B3.1 create folders for errors and desktop validation 3 days 8 18 B3.2 develop field data format base 3 days 17 19 B3.3 develop code to test data against field data format base 3 days 18 20 B3.4 develop code for data progression to desktop validation folder 4 days 19 21 B3.5 develop code for rejection actions 5 days 20 22 B3.6 create error logs, errors and confirmation emails 3 days 21 23 B3.7 system test 6 days 22 24 B3.8 release to test 0 days 23 25 B4 Desktop validation 26 B4.1 create folders for errors and upload to BiiP records 3 days 8 27 B4.2 develop desktop review module 28 B4.2.1 develop screens for view of data 4 days 8FS+1 day 29 B4.2.2 develop screens for view of attachments 6 days 28SS 30 B4.2.3 develop code to upload data for desktop validation 3 days 29SS 31 B4.5 develop code to upload accepted data to BiiP 4 days 28;29;30 32 B4.6 develop code to send rejected data to error folder 4 days 31SS 33 B4.7 create error logs, errors and confirmation emails 3 days 32 34 B4.8 system test 10 days 31;32;33 35 B4.9 Release to test 0 days 34 36 B5 DATA UPLOAD TO BiiP 37 B5.1 create folders for errors and confirmations 3 days 8 38 B5.2 develop integration code to upload data to BiiP 3 days 37 39 B5.3 develop code to flag failed uploaded data 2 days 38 40 B5.4 develop code to send failed data to error folder 3 days 39 41 B5.5 create error logs, errors and confirmation emails 5 days 40 42 B5.6 system test 10 days 41 43 B5.7 released to test 0 days 42 44 B6 INTEGRATION 45 B6.1 develop integration code for module 1 4 days 14 46 B6.2 develop integration code for module 2 4 days 23 47 B6.3 develop integration code for module 3 4 days 34 48 B6.4 develop integration code for module 4 4 days 42 49 B6.5 system test 8 days 14;23;34;42;45;46;47;48 50 B6.6 released to test 0 days 49 51 B7 Development complete 0 days 15;24;35;43;50 52 C TESTING 53 C1 Test Centre Setup 2 days 8 54 C2 onboard external test contractors 2 days 53 55 C3 develop test scripts 20 days 54 56 C4 develop test data 15 days 55 57 C5 Acceptance Testing 58 C5.1 test File pickup module 10 days 15 59 C5.2 test file validation module 10 days 24 60 C5.3 test desktop validation module 10 days 35 61 C5.4 test data upload module 10 days 43 62 C5.5 test integration 10 days 50 63 C5.6 prepare final test reports 2 days 62 64 C6 User Acceptance Testing 65 C6.1 User training 1 day 62 66 C6.2 User test file pickup module 5 days 65 67 C6.3 User test file validation module 5 days 66 68 C6.4 User test desktop validation module 5 days 67 69 C6.5 User test data upload module 5 days 68 70 C6.6 prepare final user test reports 2 days 69 71 C7 Live data testing 72 C7.1 acceptance test end to end using live datas 3 days 58;59;60;61;62 73 C7.2 user test end to end using live data 3 days 2;66;67;68;69;70 74 C7.3 prepare final test reports 2 days 63;70 75 C7.4 prepare acceptance reports 2 days 74 76 C8 Testing complete 0 days 75 77 D RELEASE TO PRODUCTION 78 D1 Release plan 79 D1.1 final documentation for support team 3 days 51;76 80 D1.2 final documentation for user training 3 days 76 81 D1.3 Change Control Board 1 day 79;80 82 D1.4 Schedule release 2 days 81 83 D1.5 Release to production. 1 day 82 84 Project completed 0 days 83