All language subtitles for Engineering Management Lec. 8

af Afrikaans
ak Akan
sq Albanian
am Amharic
ar Arabic Download
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bem Bemba
bn Bengali
bh Bihari
bs Bosnian
br Breton
bg Bulgarian
km Cambodian
ca Catalan
ceb Cebuano
chr Cherokee
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
ee Ewe
fo Faroese
tl Filipino
fi Finnish
fr French
fy Frisian
gaa Ga
gl Galician
ka Georgian
de German
el Greek
gn Guarani
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ia Interlingua
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
rw Kinyarwanda
rn Kirundi
kg Kongo
ko Korean
kri Krio (Sierra Leone)
ku Kurdish
ckb Kurdish (Soranî)
ky Kyrgyz
lo Laothian
la Latin
lv Latvian
ln Lingala
lt Lithuanian
loz Lozi
lg Luganda
ach Luo
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mfe Mauritian Creole
mo Moldavian
mn Mongolian
my Myanmar (Burmese)
sr-ME Montenegrin
ne Nepali
pcm Nigerian Pidgin
nso Northern Sotho
no Norwegian
nn Norwegian (Nynorsk)
oc Occitan
or Oriya
om Oromo
ps Pashto
fa Persian
pl Polish
pt-BR Portuguese (Brazil)
pt Portuguese (Portugal)
pa Punjabi
qu Quechua
ro Romanian
rm Romansh
nyn Runyakitara
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
sh Serbo-Croatian
st Sesotho
tn Setswana
crs Seychellois Creole
sn Shona
sd Sindhi
si Sinhalese
sk Slovak
sl Slovenian
so Somali
es Spanish
es-419 Spanish (Latin American)
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
tt Tatar
te Telugu
th Thai
ti Tigrinya
to Tonga
lua Tshiluba
tum Tumbuka
tr Turkish
tk Turkmen
tw Twi
ug Uighur
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
wo Wolof
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:20,430 --> 00:00:20,870 Silla 2 00:00:20,870 --> 00:00:23,469 Harrah's. 3 00:00:23,649 --> 00:00:24,889 Salaam alaikum. 4 00:00:26,409 --> 00:00:29,129 He had he and Mahadara 5 00:00:29,889 --> 00:00:32,769 named Mahadara Madda and 6 00:00:33,729 --> 00:00:35,289 engineering management. 7 00:00:38,399 --> 00:00:40,279 Hadim, Hadra and 8 00:00:40,279 --> 00:00:43,119 Howard and Charlamagne. 9 00:00:43,889 --> 00:00:45,369 And 10 00:00:45,809 --> 00:00:47,649 and. 11 00:00:53,559 --> 00:00:55,079 No, I'm in a Kitaba. 12 00:01:11,078 --> 00:01:13,478 So in this lecture we 13 00:01:13,518 --> 00:01:15,278 are going to discuss. 14 00:01:16,728 --> 00:01:17,888 The schedule management plan for a 15 00:01:17,888 --> 00:01:19,368 construction project. 16 00:01:20,718 --> 00:01:23,038 And we will start by 17 00:01:23,038 --> 00:01:25,158 discussing the contents. 18 00:01:26,648 --> 00:01:29,368 Of the schedule management plan, we 19 00:01:29,768 --> 00:01:32,568 emphasize more on 20 00:01:32,568 --> 00:01:34,168 construction projects. 21 00:01:36,008 --> 00:01:38,528 But everything we say 22 00:01:38,528 --> 00:01:41,328 here. Would also 23 00:01:41,328 --> 00:01:43,968 be applicable for other 24 00:01:43,968 --> 00:01:45,368 types of projects. 25 00:01:46,888 --> 00:01:49,368 So as we've seen 26 00:01:49,368 --> 00:01:52,318 before. The first thing that we 27 00:01:53,438 --> 00:01:56,157 care of in the 28 00:01:56,157 --> 00:01:59,007 beginning. Is to start 29 00:01:59,007 --> 00:02:01,527 by the initiation, so 30 00:02:02,167 --> 00:02:04,607 we start by something in the initiation 31 00:02:04,727 --> 00:02:05,447 phase. 32 00:02:07,527 --> 00:02:10,527 Because actually. Planning 33 00:02:10,807 --> 00:02:13,007 for the schedule management 34 00:02:13,687 --> 00:02:16,047 doesn't really start in the planning 35 00:02:16,047 --> 00:02:18,807 phase. It actually 36 00:02:18,807 --> 00:02:20,447 starts during the initiation of the 37 00:02:20,447 --> 00:02:23,357 project. But by 38 00:02:23,357 --> 00:02:24,037 then. 39 00:02:26,207 --> 00:02:28,647 This type of planning is called. 40 00:02:31,007 --> 00:02:33,407 High level planning, which means that 41 00:02:33,567 --> 00:02:36,127 it's not the sort of detailed 42 00:02:36,127 --> 00:02:38,647 planning, rather it's some sort 43 00:02:38,727 --> 00:02:41,406 of. Non 44 00:02:41,406 --> 00:02:44,406 detailed or really 45 00:02:44,446 --> 00:02:46,606 manually type of 46 00:02:47,126 --> 00:02:50,006 assessment of the 47 00:02:50,206 --> 00:02:53,006 needs of the project. And here 48 00:02:53,006 --> 00:02:54,406 when we talk about the needs of the 49 00:02:54,406 --> 00:02:57,406 project when it comes to schedule, we 50 00:02:57,406 --> 00:03:00,246 talk about the timing needs of the 51 00:03:00,246 --> 00:03:01,646 scheduling needs. 52 00:03:03,526 --> 00:03:06,406 So maybe certainly in the project 53 00:03:06,406 --> 00:03:08,446 initiation, we'll start by 54 00:03:08,806 --> 00:03:10,926 defining the project objectives, 55 00:03:10,926 --> 00:03:13,766 scope and deliverables. And we have 56 00:03:13,766 --> 00:03:16,046 seen this before. We've talked about the 57 00:03:16,446 --> 00:03:19,366 objectives. We have to set the objectives 58 00:03:19,366 --> 00:03:22,246 of the project then. 59 00:03:23,996 --> 00:03:26,635 We have to set the scope and then 60 00:03:27,315 --> 00:03:30,235 we go to the deliverables. Certainly 61 00:03:30,235 --> 00:03:33,035 all of this depends on the identification 62 00:03:33,035 --> 00:03:35,595 of stakeholders as we have seen 63 00:03:35,795 --> 00:03:38,435 before and based on the 64 00:03:38,435 --> 00:03:40,755 identification of the stakeholders. 65 00:03:42,645 --> 00:03:45,565 Would come into the objectives and. 66 00:03:47,365 --> 00:03:49,205 The list of requirements. 67 00:03:50,605 --> 00:03:53,445 Based on which we go into the scope and 68 00:03:53,445 --> 00:03:55,125 then the deliverables and we have seen 69 00:03:55,125 --> 00:03:58,035 this. In the previous lectures. 70 00:04:01,635 --> 00:04:04,435 Certainly this comes here when you talk 71 00:04:04,435 --> 00:04:05,755 about the identification of the 72 00:04:05,755 --> 00:04:08,605 stakeholders. And then we 73 00:04:08,605 --> 00:04:11,524 have to include the team members who 74 00:04:11,804 --> 00:04:14,524 would do this task of a stakeholder 75 00:04:14,564 --> 00:04:16,404 identification and specially 76 00:04:16,684 --> 00:04:19,004 the key stakeholders. 77 00:04:20,764 --> 00:04:22,084 Why we talk about the key stakeholders, 78 00:04:22,084 --> 00:04:24,804 as mentioned before, because 79 00:04:24,884 --> 00:04:27,124 we would rather concentrate 80 00:04:27,204 --> 00:04:30,204 on the top priorised. 81 00:04:31,154 --> 00:04:31,874 Main 82 00:04:33,594 --> 00:04:35,834 objectives and 83 00:04:36,274 --> 00:04:39,204 requirements. So that we 84 00:04:39,204 --> 00:04:41,724 can work on them and in 85 00:04:41,724 --> 00:04:44,724 this we use the 8020 rule 86 00:04:44,724 --> 00:04:47,674 or the Pareto rule. Aid to 87 00:04:47,674 --> 00:04:50,474 concentrate more on the top 88 00:04:50,834 --> 00:04:53,714 most important 20% 89 00:04:53,714 --> 00:04:56,633 of the stakeholders requirements. 90 00:04:59,423 --> 00:05:02,023 Part of the stakeholders and key 91 00:05:02,023 --> 00:05:04,663 stakeholders will be the suppliers and 92 00:05:04,663 --> 00:05:06,943 the regulatory bodies. 93 00:05:10,073 --> 00:05:12,593 Being done with the roject initiation. 94 00:05:12,793 --> 00:05:15,553 Then we go 95 00:05:15,553 --> 00:05:18,113 into the second part which is the 96 00:05:18,113 --> 00:05:19,873 resource identification. 97 00:05:21,573 --> 00:05:24,493 For the project to be accomplished 98 00:05:24,493 --> 00:05:26,973 and to accomplish the project 99 00:05:26,973 --> 00:05:29,413 objectives and. 100 00:05:31,163 --> 00:05:33,923 Attain the accepted, verified and 101 00:05:33,923 --> 00:05:36,483 validated deliverables. As we have seen 102 00:05:36,483 --> 00:05:39,243 before, we certainly need 103 00:05:40,323 --> 00:05:42,602 a list of resources. So we have to 104 00:05:43,722 --> 00:05:46,282 identify the resources 105 00:05:46,282 --> 00:05:48,682 needed. In this phase, we 106 00:05:48,682 --> 00:05:50,922 concentrate on the resource 107 00:05:50,962 --> 00:05:52,202 identification. 108 00:05:53,782 --> 00:05:56,662 So we have to acquire a list of all 109 00:05:56,702 --> 00:05:59,142 necessarily necessary 110 00:05:59,262 --> 00:06:01,782 resources, including 111 00:06:02,342 --> 00:06:05,312 Person. Equipment 112 00:06:05,592 --> 00:06:06,992 and materials. 113 00:06:09,302 --> 00:06:11,662 Certainly financial 114 00:06:11,662 --> 00:06:14,622 needs would be there, but then 115 00:06:14,622 --> 00:06:17,302 all of the financial needs will be 116 00:06:17,302 --> 00:06:19,672 assigned. Whether to 117 00:06:19,672 --> 00:06:22,432 personnel, equipment or 118 00:06:22,432 --> 00:06:24,672 materials in most of the cases. 119 00:06:31,031 --> 00:06:31,951 In this 120 00:06:33,231 --> 00:06:36,031 phase we have also to evaluate the 121 00:06:36,031 --> 00:06:38,391 availability and the 122 00:06:38,391 --> 00:06:40,551 constraints of each 123 00:06:40,831 --> 00:06:43,761 resources. Why do we 124 00:06:43,761 --> 00:06:46,561 concentrate on or care 125 00:06:46,561 --> 00:06:48,481 much about the evaluation of the 126 00:06:48,481 --> 00:06:51,281 availability and the? 127 00:06:52,121 --> 00:06:53,841 Constraints of the issue of the 128 00:06:53,841 --> 00:06:56,641 resources. That's 129 00:06:56,641 --> 00:06:59,471 because. Not all 130 00:06:59,471 --> 00:07:02,191 the resources would be always 131 00:07:02,231 --> 00:07:05,151 available for the project at any 132 00:07:05,151 --> 00:07:05,791 time. 133 00:07:07,441 --> 00:07:09,841 Rather, we have to plan. 134 00:07:11,911 --> 00:07:13,430 The different. 135 00:07:16,150 --> 00:07:18,590 That are part of the 136 00:07:19,270 --> 00:07:21,710 as we see down the WB and we have 137 00:07:21,710 --> 00:07:24,430 discussed the before or the 138 00:07:24,590 --> 00:07:27,550 web breakdown structure, OK. 139 00:07:27,830 --> 00:07:30,510 And then we coordinate with 140 00:07:30,510 --> 00:07:33,030 the project management office or what 141 00:07:33,030 --> 00:07:35,670 we call PMO to 142 00:07:35,670 --> 00:07:38,190 make sure that the 143 00:07:38,190 --> 00:07:40,990 resources. That 144 00:07:40,990 --> 00:07:43,750 we need for different. 145 00:07:46,320 --> 00:07:48,400 Parts of the project are different, where 146 00:07:48,400 --> 00:07:50,200 packages different. 147 00:07:52,1000 --> 00:07:55,160 Activities of the project would be 148 00:07:55,160 --> 00:07:58,080 available on the time that we 149 00:07:58,080 --> 00:08:00,829 need them. Then we 150 00:08:00,829 --> 00:08:03,669 also have to assess the. 151 00:08:04,919 --> 00:08:07,709 Constraints. So the constraints 152 00:08:08,229 --> 00:08:10,709 as we have seen before are always there 153 00:08:10,709 --> 00:08:13,269 in rojects and also are 154 00:08:13,349 --> 00:08:15,829 also there when it comes to 155 00:08:15,829 --> 00:08:18,759 resources. So we have 156 00:08:18,759 --> 00:08:20,239 to assess the 157 00:08:20,239 --> 00:08:22,479 constraints 158 00:08:22,919 --> 00:08:25,479 related to the resources. 159 00:08:25,479 --> 00:08:28,479 So all of these constraints have 160 00:08:28,479 --> 00:08:30,839 to be identified 161 00:08:31,279 --> 00:08:33,799 and we have to work within 162 00:08:34,279 --> 00:08:37,239 the constant constraints 163 00:08:37,519 --> 00:08:39,079 that are related to. 164 00:08:40,589 --> 00:08:41,509 Different 165 00:08:41,949 --> 00:08:44,598 resources. That 166 00:08:44,598 --> 00:08:45,878 we identify. 167 00:08:48,708 --> 00:08:51,708 Then comes the word breakdown structures 168 00:08:51,708 --> 00:08:54,068 of the WBS. We have discussed this 169 00:08:54,068 --> 00:08:56,028 before, but let's again. 170 00:08:57,798 --> 00:08:59,478 Take some look at it. 171 00:09:01,828 --> 00:09:03,908 Forgot one or two minutes. 172 00:09:04,788 --> 00:09:07,748 So what the WBS means? Will it breakdown 173 00:09:07,748 --> 00:09:10,468 selection so we have to break down the 174 00:09:10,708 --> 00:09:13,588 project into smaller manageable 175 00:09:13,588 --> 00:09:16,508 tasks?And we have 176 00:09:16,508 --> 00:09:19,468 discussed before that we 177 00:09:19,988 --> 00:09:21,908 have what we call the 178 00:09:21,908 --> 00:09:24,428 granularity and we have 179 00:09:24,428 --> 00:09:26,948 discussed how deep we have to go 180 00:09:27,548 --> 00:09:30,517 into. This 181 00:09:30,517 --> 00:09:33,467 granularity. Or to 182 00:09:33,467 --> 00:09:35,867 what level we have to go? 183 00:09:37,677 --> 00:09:38,957 And we agreed. 184 00:09:40,987 --> 00:09:42,347 That rule of 185 00:09:42,987 --> 00:09:45,747 545 meaning 186 00:09:45,747 --> 00:09:48,707 that we have to go only to the 187 00:09:48,707 --> 00:09:49,787 4th of. 188 00:09:51,917 --> 00:09:53,517 5th level of granularity. 189 00:09:55,237 --> 00:09:57,277 Nipples going beyond this level would 190 00:09:57,277 --> 00:09:59,717 make it more difficult 191 00:10:00,237 --> 00:10:03,037 to manage and behave, will 192 00:10:03,157 --> 00:10:05,637 rather be invested like this, 193 00:10:05,637 --> 00:10:08,557 like a new shape. 194 00:10:08,597 --> 00:10:09,957 Meaning that it will be harder for us. 195 00:10:10,427 --> 00:10:12,907 People manage the art 196 00:10:13,187 --> 00:10:14,667 or the. 197 00:10:17,396 --> 00:10:19,156 Work break the the 198 00:10:19,956 --> 00:10:22,876 packages or the web packages assigned. 199 00:10:24,836 --> 00:10:27,756 Or that are part of the project. 200 00:10:31,056 --> 00:10:34,026 Getting all of this done. We have 201 00:10:34,026 --> 00:10:36,426 to assign responsibilities to team 202 00:10:36,426 --> 00:10:39,186 members based on their skills 203 00:10:39,226 --> 00:10:42,066 and expertise. All of this will be 204 00:10:42,066 --> 00:10:44,906 assigned to the manageable task for the 205 00:10:44,946 --> 00:10:47,506 to the web package level and we 206 00:10:47,506 --> 00:10:49,466 discussed before that 207 00:10:50,386 --> 00:10:51,826 when it comes to timing. 208 00:10:53,356 --> 00:10:56,036 They will use the 818 year rule, which is 209 00:10:56,036 --> 00:10:56,756 different from. 210 00:10:58,476 --> 00:11:01,315 1820 rule that 211 00:11:01,515 --> 00:11:03,675 the weight packages 212 00:11:04,195 --> 00:11:06,635 were needed time in between one 213 00:11:06,755 --> 00:11:09,305 working day. To 214 00:11:09,305 --> 00:11:12,065 something like 2 215 00:11:12,065 --> 00:11:14,825 weeks or 10 working days. 216 00:11:19,405 --> 00:11:21,405 After finishing with the Work Breakdown 217 00:11:21,405 --> 00:11:24,085 structure, we go into 218 00:11:24,085 --> 00:11:26,205 the task sequence. 219 00:11:27,185 --> 00:11:29,785 What does this mean?May 220 00:11:29,825 --> 00:11:32,145 only work breakdown structure, then we 221 00:11:32,145 --> 00:11:33,305 have also two. 222 00:11:35,225 --> 00:11:36,985 Find the path. 223 00:11:38,665 --> 00:11:41,465 That should be a dog during 224 00:11:41,465 --> 00:11:44,225 the all of the new project phases. 225 00:11:45,715 --> 00:11:48,634 And we have also to sequence all of 226 00:11:48,634 --> 00:11:51,634 these paths and the their 227 00:11:51,634 --> 00:11:54,514 right sequence. And 228 00:11:54,514 --> 00:11:56,954 what should be done? Says and then what 229 00:11:56,954 --> 00:11:57,874 comes after? 230 00:12:00,024 --> 00:12:02,264 This is very important because there is 231 00:12:02,264 --> 00:12:04,344 what we call dependency. 232 00:12:06,194 --> 00:12:08,634 Some of the tasks might be dependent. 233 00:12:10,314 --> 00:12:12,994 On some predecessor. 234 00:12:15,434 --> 00:12:18,114 Or preceding pass. OK, 235 00:12:18,394 --> 00:12:21,114 so we cannot do some of the tasks 236 00:12:21,114 --> 00:12:23,914 without getting some previous or 237 00:12:23,914 --> 00:12:26,434 proceeding tasks done. 238 00:12:27,474 --> 00:12:29,714 So we have to determine the sequence in 239 00:12:29,714 --> 00:12:32,033 which tasks need to be executed. 240 00:12:34,763 --> 00:12:37,403 We have also to identify the 241 00:12:37,403 --> 00:12:40,003 dependencies between tasks 242 00:12:40,083 --> 00:12:42,603 to ensure a logical flow, 243 00:12:42,883 --> 00:12:44,563 so that's what I've been talking about, 244 00:12:44,563 --> 00:12:45,803 the independence. 245 00:12:49,783 --> 00:12:52,663 Logic is there between task and what 246 00:12:52,663 --> 00:12:55,143 sort of dependency is there. 247 00:12:55,663 --> 00:12:58,463 OK and most of the cases we have what 248 00:12:58,463 --> 00:13:01,183 we call finish to start. This in 249 00:13:01,183 --> 00:13:03,183 most of the cases actually we have. 250 00:13:04,953 --> 00:13:07,953 Four types of dependency we have start 251 00:13:07,953 --> 00:13:10,673 to start, start to finish, 252 00:13:11,273 --> 00:13:14,073 finish to start and finish to finish. 253 00:13:15,423 --> 00:13:18,262 But the mostly 254 00:13:18,262 --> 00:13:20,982 used logic is to 255 00:13:21,302 --> 00:13:24,182 is finish to start. What 256 00:13:24,182 --> 00:13:26,782 does finish to start mean? OK, I'll not 257 00:13:26,782 --> 00:13:29,262 go in all of the details of the four 258 00:13:29,262 --> 00:13:32,222 types of dependency. 259 00:13:33,992 --> 00:13:36,352 But I'd rather just discuss this. Finish 260 00:13:36,352 --> 00:13:38,352 to start, Finish to start means that we 261 00:13:38,352 --> 00:13:40,632 have to finish the activity to 262 00:13:40,632 --> 00:13:43,032 start. This 263 00:13:44,752 --> 00:13:46,112 next activity. 264 00:13:48,182 --> 00:13:49,622 An example of this. 265 00:13:50,462 --> 00:13:53,022 Would. We have 266 00:13:53,022 --> 00:13:54,422 to finish. 267 00:13:55,662 --> 00:13:56,182 Follow. 268 00:13:58,022 --> 00:14:00,382 Before going 269 00:14:00,782 --> 00:14:03,461 into the slaves. So 270 00:14:03,461 --> 00:14:05,141 we cannot have a slab 271 00:14:06,021 --> 00:14:08,061 without having columns. 272 00:14:12,611 --> 00:14:15,171 Then after finishing the task 273 00:14:15,171 --> 00:14:18,011 sequencing, we go into 274 00:14:18,891 --> 00:14:20,331 duration estimation. 275 00:14:22,871 --> 00:14:25,591 And how this is done? This is done by the 276 00:14:25,591 --> 00:14:28,351 project team and sometimes we go 277 00:14:28,351 --> 00:14:31,031 into getting advice from 278 00:14:32,551 --> 00:14:34,031 some experts. 279 00:14:35,591 --> 00:14:37,951 OK, which is called expert judgement. 280 00:14:39,631 --> 00:14:42,231 To estimate the duration of different 281 00:14:42,231 --> 00:14:44,751 paths. So when it comes to duration, 282 00:14:44,871 --> 00:14:46,751 you're estimating the duration of the 283 00:14:46,751 --> 00:14:48,630 different tasks that have been 284 00:14:49,190 --> 00:14:52,070 sequenced. In the 285 00:14:52,070 --> 00:14:54,950 right logic above 286 00:14:54,950 --> 00:14:57,880 here in #4. So we have to 287 00:14:57,880 --> 00:15:00,280 estimate the time required for each task. 288 00:15:01,280 --> 00:15:03,760 Why do we do so? Because if we 289 00:15:03,760 --> 00:15:06,480 aggregate all the estimates 290 00:15:06,680 --> 00:15:09,040 of the duration, then we'll be 291 00:15:09,040 --> 00:15:11,800 getting what we call the schedule 292 00:15:11,800 --> 00:15:13,800 baseline, which 293 00:15:14,800 --> 00:15:17,240 is a baseline defining 294 00:15:17,360 --> 00:15:19,1000 the duration of the whole 295 00:15:20,160 --> 00:15:23,080 project. This can be 296 00:15:23,080 --> 00:15:25,440 done after the analysis of what we call 297 00:15:25,440 --> 00:15:28,110 the critical path. This. We'll see just 298 00:15:28,110 --> 00:15:30,820 in a minute. During 299 00:15:30,820 --> 00:15:33,340 the duration estimation, we 300 00:15:33,340 --> 00:15:36,299 also consider factors such as. 301 00:15:37,749 --> 00:15:40,189 Weather, holidays and any 302 00:15:40,269 --> 00:15:43,029 potential risks. So this means that we 303 00:15:43,029 --> 00:15:45,429 cannot enter duration 304 00:15:45,429 --> 00:15:48,429 estimation without really going 305 00:15:48,429 --> 00:15:51,389 on to into risk identification 306 00:15:51,389 --> 00:15:53,949 and risk analysis, OK 307 00:15:54,669 --> 00:15:57,269 and then assessing 308 00:15:57,269 --> 00:15:59,909 the impact of. 309 00:16:00,419 --> 00:16:01,819 Different types 310 00:16:03,499 --> 00:16:05,659 of potential risk. 311 00:16:07,309 --> 00:16:10,269 And their effect on the 312 00:16:10,509 --> 00:16:13,469 duration estimation of all 313 00:16:13,469 --> 00:16:14,549 of the tasks. 314 00:16:17,419 --> 00:16:19,738 Then comes the critical path analysis. 315 00:16:19,778 --> 00:16:22,178 What does critical path analysis mean? 316 00:16:23,708 --> 00:16:25,068 We try to assign some. 317 00:16:26,938 --> 00:16:29,698 A whole lecture long whole literature for 318 00:16:29,698 --> 00:16:32,298 the critical path analysis. But for the 319 00:16:32,298 --> 00:16:35,258 time being we'll just go into identifying 320 00:16:35,258 --> 00:16:37,778 why? What do we mean by critical path, 321 00:16:38,218 --> 00:16:39,498 Critical path when you talk about 322 00:16:39,498 --> 00:16:42,018 critical path, is that that path 323 00:16:42,498 --> 00:16:45,418 on which all activities 324 00:16:45,418 --> 00:16:46,778 are critical? 325 00:16:48,468 --> 00:16:50,748 So it is the longest path. 326 00:16:52,218 --> 00:16:53,058 And the. 327 00:16:55,218 --> 00:16:57,978 Which contains the 328 00:16:58,658 --> 00:17:01,338 critical activities. 329 00:17:01,658 --> 00:17:03,538 It should contain the critical 330 00:17:03,578 --> 00:17:06,497 activities. So 331 00:17:07,217 --> 00:17:10,217 we have to identify this path 332 00:17:10,217 --> 00:17:12,657 which contains all the critical 333 00:17:12,657 --> 00:17:15,097 activities. Which we 334 00:17:15,097 --> 00:17:18,067 cannot. Actually make shorter. 335 00:17:18,627 --> 00:17:21,267 If we sum all the durations 336 00:17:21,267 --> 00:17:24,027 of all of these activities of the 337 00:17:24,027 --> 00:17:26,707 critical path, we get 338 00:17:26,947 --> 00:17:29,867 the right estimation of the project. 339 00:17:30,387 --> 00:17:32,587 So we identify the critical path 340 00:17:33,147 --> 00:17:36,057 which represent. Represents the 341 00:17:36,057 --> 00:17:38,497 sequence of tasks that must be 342 00:17:38,497 --> 00:17:41,457 completed on time for the project 343 00:17:41,457 --> 00:17:43,137 to finish as scheduled. 344 00:17:45,177 --> 00:17:47,497 Why we do so? Because we have to 345 00:17:47,497 --> 00:17:50,057 focus on critical tasks 346 00:17:50,496 --> 00:17:53,256 to avoid delays on the overall 347 00:17:53,256 --> 00:17:54,336 project timeline. 348 00:17:56,096 --> 00:17:58,216 Because those 349 00:17:58,216 --> 00:18:01,216 thoughts which are on the critical 350 00:18:01,216 --> 00:18:03,976 path, if they get delayed 351 00:18:03,976 --> 00:18:06,456 then the overall project will 352 00:18:06,456 --> 00:18:09,266 get delayed. Other tasks 353 00:18:09,266 --> 00:18:11,106 which are not only critical. 354 00:18:12,616 --> 00:18:15,376 Navigate delayed by some considerable 355 00:18:15,376 --> 00:18:18,306 amount of time. They 356 00:18:18,306 --> 00:18:20,666 might not affect the overall project 357 00:18:20,666 --> 00:18:23,266 timeline or the project 358 00:18:23,266 --> 00:18:23,826 schedule. 359 00:18:26,556 --> 00:18:28,276 We will assign some 360 00:18:29,516 --> 00:18:31,636 whole lecture for the critical path 361 00:18:31,636 --> 00:18:34,476 analysis, but not not in 362 00:18:34,476 --> 00:18:37,255 this lecture. Just I want you to 363 00:18:37,255 --> 00:18:39,815 know the basics of the critical path 364 00:18:40,295 --> 00:18:42,975 for. The tie. 365 00:18:46,085 --> 00:18:49,085 Getting all of this done, we 366 00:18:49,085 --> 00:18:51,325 go into the schedule development. 367 00:18:52,045 --> 00:18:54,525 OK, now we're able to develop a schedule. 368 00:18:55,045 --> 00:18:57,645 So based on all the previous 369 00:18:57,645 --> 00:19:00,165 activities, we're able to develop a 370 00:19:00,165 --> 00:19:02,965 detailed project schedule using 371 00:19:03,205 --> 00:19:05,165 project management software. 372 00:19:06,345 --> 00:19:08,785 Some of the prominent software is used in 373 00:19:08,865 --> 00:19:11,825 project management. Primavera 374 00:19:12,305 --> 00:19:13,905 and Microsoft 375 00:19:13,905 --> 00:19:15,545 projects. 376 00:19:17,585 --> 00:19:20,305 Some project management software 377 00:19:20,305 --> 00:19:22,944 are still available, but these 378 00:19:22,944 --> 00:19:23,984 are the 379 00:19:25,184 --> 00:19:27,944 famous. These two Primavera 380 00:19:27,944 --> 00:19:29,144 and Ms. Project. 381 00:19:32,054 --> 00:19:33,934 During this scheduled development, we 382 00:19:33,934 --> 00:19:36,414 have to clearly define milestones 383 00:19:36,734 --> 00:19:39,414 and deadlines for each phase of 384 00:19:39,414 --> 00:19:42,254 the project. What do you mean by 385 00:19:42,254 --> 00:19:45,134 mine? Schools Mindsoles 386 00:19:45,814 --> 00:19:47,774 are major or 387 00:19:48,574 --> 00:19:49,494 prominent. 388 00:19:50,924 --> 00:19:52,964 Activities or 389 00:19:52,964 --> 00:19:54,004 Deliverables? 390 00:19:55,734 --> 00:19:57,974 That we expect to get. 391 00:19:59,614 --> 00:20:01,534 When we go further with the. 392 00:20:06,334 --> 00:20:08,413 Then we go into resource leveling. 393 00:20:09,333 --> 00:20:11,973 As mentioned before, not all of the 394 00:20:11,973 --> 00:20:14,773 resources will be available. 395 00:20:16,093 --> 00:20:18,453 Or readily available whenever we're 396 00:20:18,453 --> 00:20:18,973 required. 397 00:20:21,383 --> 00:20:24,223 That's why we have to ensure that 398 00:20:24,383 --> 00:20:26,743 we do what is called resource 399 00:20:26,743 --> 00:20:28,743 leveling. Make sure that. 400 00:20:31,053 --> 00:20:33,053 We efficiently use the 401 00:20:33,053 --> 00:20:35,493 resources so ensure that 402 00:20:35,493 --> 00:20:37,653 resources are allocated 403 00:20:37,693 --> 00:20:40,173 efficiently to prevent 404 00:20:40,253 --> 00:20:43,133 overloading of any team member 405 00:20:43,133 --> 00:20:45,893 or weapon. Because if we 406 00:20:45,893 --> 00:20:48,333 don't do resource leveling. 407 00:20:49,973 --> 00:20:52,373 We would be into one of either 408 00:20:52,373 --> 00:20:55,302 cases. Case one 409 00:20:55,822 --> 00:20:58,822 is that some of the resources will be 410 00:20:59,102 --> 00:21:00,462 overloaded at 411 00:21:00,662 --> 00:21:03,582 sometimes of the project. 412 00:21:04,562 --> 00:21:07,442 While other resources are almost 413 00:21:07,482 --> 00:21:10,362 idle or not being efficiently utilized 414 00:21:10,962 --> 00:21:13,762 and then vice versa, these 415 00:21:13,762 --> 00:21:16,762 resources which are being overloaded 416 00:21:16,762 --> 00:21:19,642 now might be at some other time of 417 00:21:19,642 --> 00:21:21,042 the project might not. 418 00:21:22,772 --> 00:21:24,892 Be efficiently allocated 419 00:21:25,332 --> 00:21:26,812 or utilized? 420 00:21:28,282 --> 00:21:30,722 OK, and other resources might be 421 00:21:31,802 --> 00:21:34,602 overloaded. So we use resource 422 00:21:34,602 --> 00:21:36,962 leveling techniques and we'll discuss 423 00:21:36,962 --> 00:21:38,841 this later what techniques we use for 424 00:21:38,841 --> 00:21:40,721 resource labeling. But for the time being 425 00:21:40,921 --> 00:21:43,881 just we have to know that we we have to 426 00:21:43,881 --> 00:21:45,881 do what's called resource living. 427 00:21:48,891 --> 00:21:51,691 Then we have to adjust 428 00:21:51,771 --> 00:21:54,571 the schedule as needed to 429 00:21:54,571 --> 00:21:57,211 balance resource utilization. 430 00:21:58,041 --> 00:22:00,881 So based on what we do here, we adjust 431 00:22:00,881 --> 00:22:03,841 the schedule. As needed to 432 00:22:03,841 --> 00:22:06,441 balance resource utilization. 433 00:22:09,881 --> 00:22:12,281 Then we have to go into risk 434 00:22:12,321 --> 00:22:15,281 management, OK, to manage the risk. As we 435 00:22:15,281 --> 00:22:18,241 have mentioned above, we have to 436 00:22:18,241 --> 00:22:20,681 identify potential risks that would 437 00:22:20,681 --> 00:22:22,321 impact the project schedule. 438 00:22:24,380 --> 00:22:26,540 Then this, all this identification we 439 00:22:26,540 --> 00:22:29,260 have to do risk and misses 440 00:22:29,940 --> 00:22:32,420 and we then develop 441 00:22:32,420 --> 00:22:35,300 contingency or contingency plans 442 00:22:35,300 --> 00:22:37,740 for high impacts to 443 00:22:37,740 --> 00:22:39,660 minimize delays. 444 00:22:41,120 --> 00:22:43,640 We will not go deep into risk 445 00:22:43,640 --> 00:22:46,280 analysis for now, but we have to know 446 00:22:46,280 --> 00:22:48,680 that we have to do some sort of 447 00:22:48,920 --> 00:22:51,850 risk analysis. And 448 00:22:52,010 --> 00:22:54,930 risk management to help 449 00:22:55,010 --> 00:22:57,720 us. Really develop a 450 00:22:57,720 --> 00:23:00,200 contingency plan or contingency 451 00:23:00,200 --> 00:23:03,080 plans for high impact risk 452 00:23:03,480 --> 00:23:05,760 and we do so to minimize the 453 00:23:05,800 --> 00:23:07,480 delays that. 454 00:23:10,489 --> 00:23:11,409 Might affect the. 455 00:23:16,399 --> 00:23:18,439 Then we have the communication. 456 00:23:20,729 --> 00:23:22,569 Plan by communication plan we need how to 457 00:23:22,569 --> 00:23:24,489 communicate the information. 458 00:23:26,089 --> 00:23:28,889 For. All involved 459 00:23:28,889 --> 00:23:29,689 parties. 460 00:23:31,489 --> 00:23:34,169 Stakeholders. So establish a clear 461 00:23:34,169 --> 00:23:36,329 communication plan to keep all 462 00:23:36,329 --> 00:23:39,089 stakeholders informed of project 463 00:23:39,249 --> 00:23:41,409 progress and this 464 00:23:41,729 --> 00:23:42,689 includes. 465 00:23:44,479 --> 00:23:47,319 And we have to have regularly 466 00:23:47,919 --> 00:23:50,599 update or we have to regularly 467 00:23:50,639 --> 00:23:53,279 update the schedule and 468 00:23:53,279 --> 00:23:55,078 communicate any changes 469 00:23:55,518 --> 00:23:58,398 promptly. We don't have to delay. 470 00:24:00,168 --> 00:24:02,168 In conveying the required 471 00:24:02,248 --> 00:24:05,008 information. For all 472 00:24:05,008 --> 00:24:07,648 the parties 473 00:24:07,648 --> 00:24:09,888 or stakeholders. 474 00:24:16,278 --> 00:24:18,398 Monitoring and control. We have two 475 00:24:18,398 --> 00:24:20,638 monitors for the 476 00:24:20,638 --> 00:24:23,478 achievements and we have to implement the 477 00:24:23,478 --> 00:24:26,478 robust monitoring system to 478 00:24:26,478 --> 00:24:28,918 track progress against the schedule to 479 00:24:28,918 --> 00:24:31,718 make sure that we do not go 480 00:24:32,518 --> 00:24:35,478 delete or be behind schedule. 481 00:24:37,088 --> 00:24:38,848 We use Key Performance Indicators to 482 00:24:38,848 --> 00:24:40,727 measure project performance. 483 00:24:42,207 --> 00:24:43,607 I'll not talk about these key performance 484 00:24:43,607 --> 00:24:45,557 indicators for now. And 485 00:24:45,557 --> 00:24:48,247 maybe. In the next or 486 00:24:48,407 --> 00:24:50,927 the next to the next lecture, I'll be 487 00:24:50,927 --> 00:24:53,087 talking more about the key performance 488 00:24:53,087 --> 00:24:56,047 indicators of what we 489 00:24:56,047 --> 00:24:58,927 call APIs that help us measure 490 00:24:58,927 --> 00:25:01,287 the project performance 491 00:25:01,567 --> 00:25:04,327 and anticipate any 492 00:25:04,367 --> 00:25:05,127 really. 493 00:25:07,647 --> 00:25:09,807 That might affect the project 494 00:25:09,807 --> 00:25:12,247 schedule. This 495 00:25:12,687 --> 00:25:15,447 would then help us take action 496 00:25:15,967 --> 00:25:18,687 for remedy and correcting 497 00:25:19,007 --> 00:25:21,797 the. Making 498 00:25:22,397 --> 00:25:25,237 corrective measures to bring the 499 00:25:25,237 --> 00:25:27,796 project back into 500 00:25:27,796 --> 00:25:28,796 schedules. 501 00:25:31,436 --> 00:25:33,996 Then continuous improvement 502 00:25:34,436 --> 00:25:37,396 based on what we do on the monitoring and 503 00:25:37,396 --> 00:25:40,396 control we have to improve. So 504 00:25:40,396 --> 00:25:42,836 we collect regular reviews to identify 505 00:25:43,116 --> 00:25:45,716 areas for improvement in the schedule 506 00:25:45,716 --> 00:25:48,366 management process. And we 507 00:25:48,366 --> 00:25:51,206 incorporate lessons into 508 00:25:51,206 --> 00:25:54,046 future projects. So this 509 00:25:54,046 --> 00:25:56,566 we just do our best 510 00:25:56,886 --> 00:25:58,046 to improve. 511 00:25:59,646 --> 00:26:02,446 Learning from the lessons or 512 00:26:02,446 --> 00:26:04,926 from the thoughts that we have been. 513 00:26:08,866 --> 00:26:11,785 So by integrating these elements and your 514 00:26:11,785 --> 00:26:13,505 schedule management plan. 515 00:26:14,765 --> 00:26:16,165 Will be well equipped to ensure the 516 00:26:16,165 --> 00:26:18,965 successful and timely completion of your 517 00:26:19,285 --> 00:26:21,565 construction projects for these 518 00:26:21,565 --> 00:26:24,365 elements. If we take 519 00:26:24,365 --> 00:26:26,835 care of. And 520 00:26:27,475 --> 00:26:29,635 if we integrate a 521 00:26:30,475 --> 00:26:33,405 proper. Manners. Then 522 00:26:33,405 --> 00:26:36,405 we will guarantee that our project will 523 00:26:36,405 --> 00:26:39,165 be successful and will not be 524 00:26:39,245 --> 00:26:41,955 deleted. But 525 00:26:41,955 --> 00:26:44,395 then it's very important. If you have any 526 00:26:44,395 --> 00:26:46,635 specific details or preferences you'd 527 00:26:46,635 --> 00:26:49,475 like to incorporate, feel free to 528 00:26:49,475 --> 00:26:52,315 provide them for further customization. 529 00:26:53,765 --> 00:26:56,045 This can be I mean different for 530 00:26:56,045 --> 00:26:58,364 different from 1 project to the 531 00:26:58,884 --> 00:27:01,444 other. So if we feel that something 532 00:27:01,444 --> 00:27:04,284 special is there about your project and 533 00:27:04,284 --> 00:27:07,124 some other details might be of 534 00:27:07,124 --> 00:27:09,884 benefit then you have to 535 00:27:10,204 --> 00:27:12,964 add these details so. 536 00:27:13,234 --> 00:27:16,034 That your schedule will 537 00:27:16,034 --> 00:27:18,874 not be affected and you 538 00:27:18,954 --> 00:27:20,434 prevent any 539 00:27:21,034 --> 00:27:23,154 anticipated delay. 540 00:27:27,474 --> 00:27:30,154 I will. I'd rather stop here at this 541 00:27:30,154 --> 00:27:32,564 point. And 542 00:27:32,724 --> 00:27:35,724 continue with more discussion 543 00:27:35,844 --> 00:27:38,084 in the next lecture 544 00:27:38,604 --> 00:27:40,724 about some of the details. 545 00:27:42,563 --> 00:27:44,923 Related to different points within this 546 00:27:45,203 --> 00:27:48,123 schedule management plan. 547 00:27:49,633 --> 00:27:52,473 Wish you were the rest of life and see 548 00:27:52,473 --> 00:27:53,913 you next time. 549 00:27:56,393 --> 00:27:57,713 Next lectures. 550 00:28:00,043 --> 00:28:00,803 Thank you and goodbye. 33930

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.