Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
Niidae Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Project planning
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Short description|Aspect of project management which uses schedules to plan and report progress}} '''Project planning''' is part of [[project management]], which relates to the use of [[Schedule (project management)|schedules]] such as [[Gantt chart]]s to plan and subsequently report progress within the project environment.<ref>{{cite book | author = Harold Kerzner | author-link = Harold Kerzner | year = 2003 | title = Project Management: A Systems Approach to Planning, Scheduling, and Controlling | url = https://archive.org/details/projectmanagemen0000kerz_h0w8 | url-access = registration | edition = 8th | publisher = Wiley | isbn = 0-471-22577-0}}</ref> Project planning can be done manually or by the use of [[project management software]].<ref>{{Cite web |last=HeΓe |first=Robert |date=2023-04-08 |title=PROJECT MANAGEMENT DEMYSTIFIED |url=https://richtig.media/projektmanagement-e-commerce/ |access-date=2023-06-11 |language=de-DE}}</ref> == Description == Initially, the [[scope (project management)|project scope]] is defined and the appropriate methods for completing the project are determined. Following this step, the durations for the various [[Task (projecting management)|tasks]] necessary to complete the work are listed and grouped into a [[work breakdown structure]]. Project planning is often used to organize different areas of a project, including [[project plan]]s, [[work load|workload]]s and the management of teams and individuals. The logical [[Dependency (project management)|dependencies]] between tasks are defined using an [[activity network diagram]] that enables identification of the [[critical path method|critical path]]. 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.<ref>{{cite web|title=Definition of project planning methodologies with examples|url=http://geekly-yours.blogspot.fr/2014/04/project-planning-top-10-interview-questions-for-project-managers.html|access-date=24 April 2014}}</ref> [[Float (project management)|Float]] or slack time in the schedule can be calculated using project management software.<ref>{{cite book | author = Richard H. Thayer, Edward Yourdon | year = 2000 | title = Software Engineering Project Management | edition = 2nd | publisher = Wiley-IEEE Computer Society Press | isbn = 0-8186-8000-8}}</ref> Then the necessary [[Resource (project management)|resources]] can be [[estimate]]d and [[cost]]s for each activity can be allocated to each resource, giving the total project cost. At this stage, the [[schedule (project management)|project schedule]] may be optimized to achieve the appropriate balance between [[Resource management|resource usage]] 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 schedule is known as [[earned value management]].<ref>{{cite book | first = Quentin | last = Fleming | year = 2005 | title = Earned Value Project Management | edition = Third | publisher = Project Management Institute | isbn = 1-930699-89-1}}</ref> The inputs of the project planning phase 2 include the [[project charter]] and the concept proposal. The outputs of the project planning phase include the project requirements, the project schedule, and the [[project management plan]].<ref>Filicetti, John, [http://www.pmhut.com/project-management-process-phase-2-planning-overview Project Planning Overview], PM Hut (Last accessed 8 November 2009).</ref> == See also == *[[Cost overrun]] *[[Dependency structure matrix]] *[[Enterprise resource planning]] *[[Megaproject]] *[[Operations research]] *[[PRINCE2]] *[[Project Management Institute]] *[[Project plan]] *[[Project slippage]] *[[Project stakeholders]] *[[Scope creep]] ==References== {{Reflist}} ==External links== *[http://www.ipma.world/ International Project Management Association] *[http://www.apm.org.uk/ Association for Project Management (UK)] {{DEFAULTSORT:Project Planning}} [[Category:Schedule (project management)]] [[Category:Planning]]
Summary:
Please note that all contributions to Niidae Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Encyclopedia:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Templates used on this page:
Template:Cite book
(
edit
)
Template:Cite web
(
edit
)
Template:Reflist
(
edit
)
Template:Short description
(
edit
)
Search
Search
Editing
Project planning
Add topic