82:. Project planning is inherently uncertain as it must be done before the project is actually started. Therefore, the duration of the tasks is often estimated through a weighted average of optimistic, normal, and pessimistic cases. The critical chain method adds "buffers" in the planning to anticipate potential delays in project execution.
106:
and project duration to comply with the project objectives. Once established and agreed, the project schedule becomes what is known as the baseline schedule. Progress will be measured against the baseline schedule throughout the life of the project. Analyzing progress compared to the baseline
55:
255:
118:
and the concept proposal. The outputs of the project planning phase include the project requirements, the project schedule, and the
34:
to plan and subsequently report progress within the project environment. Project planning can be done manually or by the use of
362:
310:
285:
217:
71:
99:
87:
51:
27:
326:
161:
141:
50:
is defined and the appropriate methods for completing the project are determined. Following this step, the
136:
35:
98:
for each activity can be allocated to each resource, giving the total project cost. At this stage, the
83:
47:
86:
or slack time in the schedule can be calculated using project management software. Then the necessary
75:
59:
119:
108:
206:
176:
79:
8:
151:
103:
23:
234:
367:
306:
281:
213:
62:. Project planning is often used to organize different areas of a project, including
171:
115:
208:
Project
Management: A Systems Approach to Planning, Scheduling, and Controlling
201:
356:
16:
Aspect of project management which uses schedules to plan and report progress
166:
131:
63:
181:
146:
31:
67:
91:
275:
156:
58:
necessary to complete the work are listed and grouped into a
256:"Definition of project planning methodologies with examples"
102:
may be optimized to achieve the appropriate balance between
95:
347:
342:
70:
and the management of teams and individuals. The logical
114:
The inputs of the project planning phase 2 include the
280:(2nd ed.). Wiley-IEEE Computer Society Press.
205:
354:
305:(Third ed.). Project Management Institute.
200:
343:International Project Management Association
276:Richard H. Thayer, Edward Yourdon (2000).
329:, PM Hut (Last accessed 8 November 2009).
348:Association for Project Management (UK)
300:
278:Software Engineering Project Management
355:
232:
78:that enables identification of the
74:between tasks are defined using an
13:
14:
379:
336:
235:"PROJECT MANAGEMENT DEMYSTIFIED"
303:Earned Value Project Management
319:
294:
269:
248:
226:
194:
41:
26:, which relates to the use of
1:
363:Schedule (project management)
187:
162:Project Management Institute
142:Enterprise resource planning
7:
233:Heße, Robert (2023-04-08).
137:Dependency structure matrix
125:
36:project management software
10:
384:
327:Project Planning Overview
301:Fleming, Quentin (2005).
76:activity network diagram
60:work breakdown structure
212:(8th ed.). Wiley.
120:project management plan
109:earned value management
107:schedule is known as
177:Project stakeholders
152:Operations research
24:project management
325:Filicetti, John,
375:
330:
323:
317:
316:
298:
292:
291:
273:
267:
266:
264:
262:
252:
246:
245:
243:
242:
230:
224:
223:
211:
198:
172:Project slippage
100:project schedule
54:for the various
20:Project planning
383:
382:
378:
377:
376:
374:
373:
372:
353:
352:
339:
334:
333:
324:
320:
313:
299:
295:
288:
274:
270:
260:
258:
254:
253:
249:
240:
238:
231:
227:
220:
199:
195:
190:
128:
116:project charter
46:Initially, the
44:
17:
12:
11:
5:
381:
371:
370:
365:
351:
350:
345:
338:
337:External links
335:
332:
331:
318:
311:
293:
286:
268:
247:
225:
218:
202:Harold Kerzner
192:
191:
189:
186:
185:
184:
179:
174:
169:
164:
159:
154:
149:
144:
139:
134:
127:
124:
104:resource usage
43:
40:
15:
9:
6:
4:
3:
2:
380:
369:
366:
364:
361:
360:
358:
349:
346:
344:
341:
340:
328:
322:
314:
312:1-930699-89-1
308:
304:
297:
289:
287:0-8186-8000-8
283:
279:
272:
257:
251:
236:
229:
221:
219:0-471-22577-0
215:
210:
209:
203:
197:
193:
183:
180:
178:
175:
173:
170:
168:
165:
163:
160:
158:
155:
153:
150:
148:
145:
143:
140:
138:
135:
133:
130:
129:
123:
121:
117:
112:
110:
105:
101:
97:
93:
89:
85:
81:
80:critical path
77:
73:
69:
65:
64:project plans
61:
57:
53:
49:
48:project scope
39:
37:
33:
29:
25:
21:
321:
302:
296:
277:
271:
259:. Retrieved
250:
239:. Retrieved
228:
207:
196:
167:Project plan
132:Cost overrun
113:
72:dependencies
45:
32:Gantt charts
19:
18:
237:(in German)
182:Scope creep
147:Megaproject
42:Description
22:is part of
357:Categories
241:2023-06-11
188:References
92:estimated
88:resources
68:workloads
52:durations
28:schedules
368:Planning
261:24 April
204:(2003).
126:See also
30:such as
157:PRINCE2
90:can be
309:
284:
216:
96:costs
84:Float
56:tasks
307:ISBN
282:ISBN
263:2014
214:ISBN
94:and
359::
122:.
111:.
66:,
38:.
315:.
290:.
265:.
244:.
222:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.