All language subtitles for 5. WBS Methods

af Afrikaans
sq Albanian
am Amharic
ar Arabic Download
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bn Bengali
bs Bosnian
bg Bulgarian
ca Catalan
ceb Cebuano
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
tl Filipino
fi Finnish
fr French
fy Frisian
gl Galician
ka Georgian
de German
el Greek
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
km Khmer
ko Korean
ku Kurdish (Kurmanji)
ky Kyrgyz
lo Lao
la Latin
lv Latvian
lt Lithuanian
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mn Mongolian
my Myanmar (Burmese)
ne Nepali
no Norwegian
ps Pashto
fa Persian
pl Polish
pt Portuguese
pa Punjabi
ro Romanian
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
st Sesotho
sn Shona
sd Sindhi
si Sinhala
sk Slovak
sl Slovenian
so Somali
es Spanish
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
te Telugu
th Thai
tr Turkish
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
or Odia (Oriya)
rw Kinyarwanda
tk Turkmen
tt Tatar
ug Uyghur
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 1 00:00:00,780 --> 00:00:02,940 So how do you structure the categories 2 2 00:00:02,940 --> 00:00:03,993 of the WBS? 3 3 00:00:05,090 --> 00:00:09,210 The classic method is called hierarchical decomposition, 4 4 00:00:09,210 --> 00:00:11,420 where you break the project up into pieces, 5 5 00:00:11,420 --> 00:00:14,850 then those into pieces, and those into pieces, and so on 6 6 00:00:14,850 --> 00:00:16,210 until you get down to deliverables 7 7 00:00:16,210 --> 00:00:18,613 that can be allocated to single individuals. 8 8 00:00:19,650 --> 00:00:21,370 For very large projects, you can end up with 9 9 00:00:21,370 --> 00:00:23,623 as many as six levels, sometimes more. 10 10 00:00:25,090 --> 00:00:28,630 However, this classic approach does not always work 11 11 00:00:28,630 --> 00:00:31,870 for smaller projects, or areas of projects 12 12 00:00:31,870 --> 00:00:34,323 with substantial cross-functional process work. 13 13 00:00:35,480 --> 00:00:37,230 So let's look at some alternatives. 14 14 00:00:39,230 --> 00:00:41,830 Other ways to structure the WBS categories include 15 15 00:00:41,830 --> 00:00:44,883 by phases and using a combined approach. 16 16 00:00:46,240 --> 00:00:49,370 A lot of people prefer the phased approach, 17 17 00:00:49,370 --> 00:00:51,890 where the categories capture the various phases 18 18 00:00:51,890 --> 00:00:52,733 of the project. 19 19 00:00:53,720 --> 00:00:57,400 The WBS does not have to show any chronological information, 20 20 00:00:57,400 --> 00:00:58,980 but this approach by nature does tend 21 21 00:00:58,980 --> 00:01:01,460 to show deliverables that happen earlier on the left 22 22 00:01:01,460 --> 00:01:03,920 and those later on the right. 23 23 00:01:03,920 --> 00:01:06,640 Although, even then, there are usually exceptions. 24 24 00:01:06,640 --> 00:01:07,990 For example, there could be plans 25 25 00:01:07,990 --> 00:01:10,070 in the first planning category that are not started 26 26 00:01:10,070 --> 00:01:12,133 until midway in the actual schedule. 27 27 00:01:14,010 --> 00:01:17,070 Some people prefer a combined approach, 28 28 00:01:17,070 --> 00:01:18,830 where they use hierarchical decomposition 29 29 00:01:18,830 --> 00:01:21,210 for parts of the project, for example, 30 30 00:01:21,210 --> 00:01:23,970 to capture hardware and software components, 31 31 00:01:23,970 --> 00:01:26,300 and some phase-oriented categories to capture elements 32 32 00:01:26,300 --> 00:01:28,943 like testing, training, implementation, and support. 33 33 00:01:30,540 --> 00:01:34,340 The bottom line is: Use either hierarchical decomposition, 34 34 00:01:34,340 --> 00:01:37,963 or phasing, or a combination as convenient. 35 35 00:01:39,030 --> 00:01:41,730 You want to try to collect related deliverables together 36 36 00:01:41,730 --> 00:01:44,310 in any categories that make sense for the project, 37 37 00:01:44,310 --> 00:01:46,520 whatever seems most clear. 38 38 00:01:46,520 --> 00:01:48,833 There is never a right or a wrong way. 39 39 00:01:49,780 --> 00:01:52,120 Some ways might be more clear than others, 40 40 00:01:52,120 --> 00:01:54,980 and you get better with time; but it's the deliverables 41 41 00:01:54,980 --> 00:01:58,060 that are important, not the categories. 42 42 00:01:58,060 --> 00:02:00,460 Never get hung up on the categories. 43 43 00:02:00,460 --> 00:02:03,470 Stay focused on identifying all the deliverables 44 44 00:02:03,470 --> 00:02:05,860 and feel free to rearrange the categories 45 45 00:02:05,860 --> 00:02:08,783 however makes sense as the WBS develops. 46 46 00:02:10,490 --> 00:02:12,250 Let's take a look at a couple of examples 47 47 00:02:12,250 --> 00:02:13,300 that make this point. 48 48 00:02:15,960 --> 00:02:18,010 Let's look at two work breakdown structures 49 49 00:02:18,010 --> 00:02:20,610 that illustrate the point it's the deliverables 50 50 00:02:20,610 --> 00:02:23,280 that are important, not the categories. 51 51 00:02:23,280 --> 00:02:26,210 These both have exactly the same deliverables, 52 52 00:02:26,210 --> 00:02:27,653 just organized differently. 53 53 00:02:29,210 --> 00:02:32,450 Here is a WBS for a typical system integration project 54 54 00:02:32,450 --> 00:02:35,750 that is organized hierarchically, for example, 55 55 00:02:35,750 --> 00:02:38,470 collecting all the hardware and software together 56 56 00:02:38,470 --> 00:02:39,683 in separate categories. 57 57 00:02:40,830 --> 00:02:43,350 So the software plan, design, builds, reviews, 58 58 00:02:43,350 --> 00:02:45,753 and tests are all in one category. 59 59 00:02:47,540 --> 00:02:49,380 Now to make the point, you should not get hung up 60 60 00:02:49,380 --> 00:02:50,590 on the categories. 61 61 00:02:50,590 --> 00:02:52,680 Let's look at exactly the same project 62 62 00:02:52,680 --> 00:02:54,870 and exactly the same deliverables, 63 63 00:02:54,870 --> 00:02:56,313 just organized another way. 64 64 00:02:58,070 --> 00:03:01,180 Here's a WBS for the same system integration project 65 65 00:03:01,180 --> 00:03:02,820 with exactly the same deliverables, 66 66 00:03:02,820 --> 00:03:05,910 just organized differently in this version 67 67 00:03:05,910 --> 00:03:07,113 largely by phasing. 68 68 00:03:08,330 --> 00:03:10,530 So now the software deliverables are spread 69 69 00:03:10,530 --> 00:03:13,540 across the WBS with the software plan 70 70 00:03:13,540 --> 00:03:16,630 in the planning branch, the design under design, 71 71 00:03:16,630 --> 00:03:19,560 the builds under build, the reviews under PM, 72 72 00:03:19,560 --> 00:03:21,083 and the tests under test. 73 73 00:03:22,180 --> 00:03:24,930 Exactly the same project, same deliverables, 74 74 00:03:24,930 --> 00:03:26,280 just organized differently. 75 75 00:03:27,240 --> 00:03:29,630 You might prefer one way over another, 76 76 00:03:29,630 --> 00:03:31,650 and either one might be more appropriate 77 77 00:03:31,650 --> 00:03:32,913 for a given project. 78 78 00:03:34,290 --> 00:03:37,550 The key point is that neither way is incorrect 79 79 00:03:37,550 --> 00:03:40,300 and either will work because the important thing 80 80 00:03:40,300 --> 00:03:42,943 is the deliverables are identified. 81 81 00:03:44,180 --> 00:03:47,440 There are probably other ways to organize the WBS as well, 82 82 00:03:47,440 --> 00:03:49,250 and some may be better than either of these 83 83 00:03:49,250 --> 00:03:51,230 for certain situations. 84 84 00:03:51,230 --> 00:03:54,700 They key point is to not get hung up on the categories 85 85 00:03:54,700 --> 00:03:58,380 because it could be a huge time sink, preventing you 86 86 00:03:58,380 --> 00:03:59,610 from focusing on the important part 87 87 00:03:59,610 --> 00:04:03,413 in your WBS creation meetings: identifying the deliverables. 88 88 00:04:04,780 --> 00:04:08,210 The purpose of the categories is to help spark the memory, 89 89 00:04:08,210 --> 00:04:10,820 help you find all the deliverables, 90 90 00:04:10,820 --> 00:04:13,200 and provide a convenient way to collect them. 91 91 00:04:13,200 --> 00:04:15,100 They are not the point of the process. 92 92 00:04:16,040 --> 00:04:17,853 This is really important. 93 93 00:04:18,710 --> 00:04:21,490 I have seen teams in a WBS planning session 94 94 00:04:21,490 --> 00:04:24,700 spend an hour arguing over the categories 95 95 00:04:24,700 --> 00:04:26,993 and not come up with a single deliverable. 96 96 00:04:28,200 --> 00:04:30,480 If you ever encounter this kind of dynamic 97 97 00:04:30,480 --> 00:04:33,060 as the project manager, simply say 98 98 00:04:33,060 --> 00:04:35,460 let's get as many of the deliverables as possible, 99 99 00:04:35,460 --> 00:04:38,470 stick them up there anywhere with Post-It notes, 100 100 00:04:38,470 --> 00:04:40,173 and organize them later. 101 101 00:04:41,440 --> 00:04:43,870 That's how you break the logjam. 102 102 00:04:43,870 --> 00:04:46,340 The categories will become a lot easier to agree 103 103 00:04:46,340 --> 00:04:48,800 once your flip chart is filled up with deliverables 104 104 00:04:48,800 --> 00:04:50,850 and the patterns become a lot more clear. 105 105 00:04:51,880 --> 00:04:54,173 The deliverables are what matters. 9249

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