PROJECT MGT
CITATIONS IN THE BUTTONS
CITATIONS IN THE BUTTONS
Smartsheet Contributor Kate Eby on May 29, 2018 (Last modified on Nov 24, 2021)
At the root of any successful project is a project manager (PM) worth his or her weight in gold. While some people think a project manager’s sole job is to remind everyone about deadlines and set up status meeting, that’s simply not the case.
There is a science to what they do -- they have a deep understanding of and can perfectly execute the five phases of project management. In this article, we’ll cover what each of these phases entail and share tips for boosting success during each stage.
Developed by the Project Management Institute (PMI), the five phases of project management include conception and initiation, planning, execution, performance/monitoring, and project close. PMI, which began in 1969, is the world’s largest nonprofit membership association for the project management profession. It has set the standards for project, program, and portfolio management and offers training and certifications. The gold standard of certification from the association is the Project Management Professional (PMP)® certification. There are seven other certifications available for different types of project management.
In an effort to standardize project management information and practices, a team of over 80 PMI members created the text, A Guide to the Project Management Book of Knowledge (PMBOK® Guide) Currently in its fifth edition, the PMBOK® Guide is continually being updated by the PMI and shares the fundamental practices that are used worldwide to achieve the best results. The PMBOK® Guide includes a process standard that can be applied to many projects; however, it does recognize that each project is different. It is up to PMPs to apply the techniques and phases covered in the PMBOK® Guide to the unique requirements of their project.
When discussing project management phases, the mention of project life cycle is inevitable. So what’s the difference? The project phases make up a project life cycle, and as such, the phases are tailored to fit a project’s needs. According to the PMBOK® Guide, the elements of a project life cycle should define:
What work must be accomplished
What deliverables must be generated and reviewed
Who must be involved
How to control and approve each phase
Determining these elements will take a project from start to finish. It provides a systematic, timely, and controlled process that benefits a project’s stakeholders. This helps PMs define what needs to be accomplished before moving onto the next phase of a project.
Smartsheet is a cloud-based platform that allows teams and organizations to plan, manage, and report on projects, helping you move faster and achieve more. See Smartsheet in action.
According to PMI, “project management is the application of knowledge, skills, tools, and techniques to a broad range of activities in order to meet the requirements of a particular project.” There are five phases of project management and if the lifecycle provides a high-level view of the project, the phases are the roadmap to accomplishing it.
This is the start of the project, and the goal of this phase is to define the project at a broad level. This phase usually begins with a business case. This is when you will research whether the project is feasible and if it should be undertaken. If feasibility testing needs to be done, this is the stage of the project in which that will be completed.
Important stakeholders will do their due diligence to help decide if the project is a “go.” If it is given the green light, you will need to create a project charter or a project initiation document (PID) that outlines the purpose and requirements of the project. It should include business needs, stakeholders, and the business case. Note: There are plenty of PID templates that adhere to PMBOK® Guide guidelines available online that you can download to help you get started.
Tip: When creating a PID, don’t get too bogged down in technical requirements. Those will be clarified and clearly defined in Phase 2.
This phase is key to successful project management and focuses on developing a roadmap that everyone will follow. This phase typically begins with setting goals. Two of the more popular methods for setting goals are S.M.A.R.T. and CLEAR:
S.M.A.R.T. Goals – This method helps ensure that the goals have been thoroughly vetted. It also provides a way to clearly understand the implications of the goal-setting process.
Specific – To set specific goals, answer the following questions: who, what, where, when, which, and why.
Measurable – Create criteria that you can use to measure the success of a goal.
Attainable – Identify the most important goals and what it will take to achieve them.
Realistic – You should be willing and able to work toward a particular goal.
Timely – Create a timeframe to achieve the goal.
For more information about S.M.A.R.T. goals and to download free S.M.A.R.T. goal templates, read "The Essential Guide to Writing S.M.A.R.T. Goals."
C.L.E.A.R. Goals – A newer method for setting goals that takes into consideration the environment of today’s fast-paced businesses.
Collaborative – The goal should encourage employees to work together.
Limited – They should be limited in scope and time to keep it manageable.
Emotional – Goals should tap into the passion of employees and be something they can form an emotional connection to. This can optimize the quality of work.
Appreciable – Break larger goals into smaller tasks that can be quickly achieved.
Refinable – As new situations arise, be flexible and refine goals as needed.
During this phase, the scope of the project is defined and a project management plan is developed. It involves identifying the cost, quality, available resources, and a realistic timetable. The project plans also includes establishing baselines or performance measures. These are generated using the scope, schedule and cost of a project. A baseline is essential to determine if a project is on track.
At this time, roles and responsibilities are clearly defined, so everyone involved knows what they are accountable for. Here are some of the documents a PM will create during this phase to ensure the project will stay on track:
Scope Statement – A document that clearly defines the business need, benefits of the project, objectives, deliverables, and key milestones. A scope statement may change during the project, but it shouldn’t be done without the approval of the project manager and the sponsor.
Work Breakdown Schedule (WBS) –This is a visual representation that breaks down the scope of the project into manageable sections for the team.
Milestones – Identify high-level goals that need to be met throughout the project and include them in the Gantt chart.
Gantt Chart – A visual timeline that you can use to plan out tasks and visualize your project timeline.
Communication Plan – This is of particular importance if your project involves outside stakeholders. Develop the proper messaging around the project and create a schedule of when to communicate with team members based on deliverables and milestones.
Risk Management Plan – Identify all foreseeable risks. Common risks include unrealistic time and cost estimates, customer review cycle, budget cuts, changing requirements, and lack of committed resources.
Tip: When creating a WBS, work packages shouldn’t be longer than 10 days. Be sure to solicit the input and perspective from team members about their specific tasks.
Manage Your Project in Smartsheet
This is the phase where deliverables are developed and completed. This often feels like the meat of the project since a lot is happening during this time, like status reports and meetings, development updates, and performance reports. A “kick-off” meeting usually marks the start of the Project Execution phase where the teams involved are informed of their responsibilities.
Tasks completed during the Execution Phase include:
Develop team
Assign resources
Execute project management plans
Procurement management if needed
PM directs and manages project execution
Set up tracking systems
Task assignments are executed
Status meetings
Update project schedule
Modify project plans as needed
While the project monitoring phase has a different set of requirements, these two phases often occur simultaneously.
Tip: Consider using cloud-based project management software so team members can update task status in real time.
This is all about measuring project progression and performance and ensuring that everything happening aligns with the project management plan. Project managers will use key performance indicators (KPIs) to determine if the project is on track. A PM will typically pick two to five of these KPIs to measure project performance:
Project Objectives: Measuring if a project is on schedule and budget is an indication if the project will meet stakeholder objectives.
Quality Deliverables: This determines if specific task deliverables are being met.
Effort and Cost Tracking: PMs will account for the effort and cost of resources to see if the budget is on track. This type of tracking informs if a project will meet its completion date based on current performance.
Project Performance: This monitors changes in the project. It takes into consideration the amount and types of issues that arise and how quickly they are addressed. These can occur from unforeseen hurdles and scope changes.
During this time, PMs may need to adjust schedules and resources to ensure the project is on track
Tip: Review the business case at the end of each phase and make adjustments to the project plan as needed.
This phase represents the completed project. Contractors hired to work specifically on the project are terminated at this time. Valuable team members are recognized. Some PMs even organize small work events for people who participated in the project to thank them for their efforts. Once a project is complete, a PM will often hold a meeting – sometimes referred to as a “post mortem” – to evaluate what went well in a project and identify project failures. This is especially helpful to understand lessons learned so that improvements can be made for future projects.
Once the project is complete, PMs still have a few tasks to complete. They will need to create a project punchlist of things that didn’t get accomplished during the project and work with team members to complete them. Perform a final project budget and prepare a final project report. Finally, they will need to collect all project documents and deliverables and store them in a single place.
Tip: Using a cloud-based software solution is an easy way to collect and save all project documents in one location throughout the life of the project.
Empower your people to go above and beyond with a flexible platform designed to match the needs of your team — and adapt as those needs change.
The Smartsheet platform makes it easy to plan, capture, manage, and report on work from anywhere, helping your team be more effective and get more done. Report on key metrics and get real-time visibility into work as it happens with roll-up reports, dashboards, and automated workflows built to keep your team connected and informed.
When teams have clarity into the work getting done, there’s no telling how much more they can accomplish in the same amount of time. Try Smartsheet for free, today.
https://www.smartsheet.com/blog/demystifying-5-phases-project-management
An Introduction to Project Management
The purpose of this briefing paper is to introduce key project management terms and concepts to provide a common language for discussion, including what is:
• A project
• Project management
• Project success
• A project manager
• A project management plan
Successful project management has several significant characteristics. To understand the value of project management, it is necessary to understand the fundamental nature of a project; the core characteristics of project management processes; how success is evaluated, the roles, responsibilities, and activities of a project manager and the expertise required; and the context in which projects are performed, conceptually illustrated by figure 1.1
Throughout this document, references are made to The Project Management Institute’s (PMI®) Project Management Body of Knowledge (PMBOK®). Developed over the past 30 years, the PMBOK is a collection and organization of knowledge on the project management profession. It is widely accepted to include the core elements of successful project management practices. It is a regularly updated and internationally referenced standard (ANSI /PMI 99-001-
2004) and provides a basis for universal discourse on practices. Most modern
Figure 1.
1 Project Management Institute. A Guide to the Project Management Body of Knowledge:
PMBOK® Guide
2004, p. 43.
academic and practical publications on the subject of project management reference the PMBOK, adopt its methodology, and incorporate its terminology.
What Is a Project?
The fundamental nature of a project is that it is a “temporary endeavor undertaken to create a unique product, service, or result.”2 Projects are distinguished from operations and from programs.
To be temporary signifies that there is a discrete and definable commencement and conclusion; the management of a project requires tailored activities to support this characteristic, as such, a key indicator of project success is how it performs against its schedule—that is, does is start and end on time.
The uniqueness of the deliverable, whether it is a product, service, or result, requires a special approach in that there may not be a pre-existing blueprint for the project’s execution and there may not be a need to repeat the project once it is completed. Uniqueness does not mean that there are not similarities to other projects, but that the scope for a particular project has deliverables that must be produced within constraints, through risks, with specific resources, at a specific place, and within a certain period; therefore, the process to produce the deliverable as well as the deliverable itself is unique.
This unique process and deliverable produces the third characteristic of a project: progressive elaboration. Project management is a group of interrelated processes, implemented in a progressively elaborative manner, in which to produce the deliverable. Progressive elaboration is the revealing and focusing of details through time. For example, in the engineering design process, a general and broad concept may be a starting point for the design team; but through the design process, the concept is narrowed to a specific scope and is further elaborated to achieve the completed design; moreover, it may continue to be elaborated and not be finalized until the product, service, or result is delivered.
A clarification should be made with respect to Reclamation language. In Reclamation, a project is typically a congressionally authorized or directed activity that allows Reclamation to do something specific. Traditionally, projects
2 Project Management Institute. A Guide to the Project Management Body of Knowledge:
PMBOK® Guide
2004, p. 5.
are groups of infrastructure, such as the Central Arizona Project, the Lower Colorado Dams Project, or the Central Valley Project. The Reclamation “project” activities would range from the traditional planning, designing, and building of structures, to negotiating and signing delivery contracts, developing operations plans, and completing environmental compliance documents.[1] In historic Reclamation vernacular, the operation and maintenance of the completed project is also often considered as part of the “project.” Additionally at times in Reclamation, the people managing projects are often referred to as something other than project managers—they may be called team leaders, coordinators, activity managers or program managers; people managing “projects” may be called area managers or facility managers. Because of these connotations, care should be taken to distinguish between Reclamation “projects” and projects as defined above.
The operations of an organization are continuing and repetitive activities that are executed to achieve its mission and sustain the business, but without a definable end to their performance and without a unique output—that is, it is not produced or provided only once.
A project differs from a program in that “a program is a group of related projects managed in a coordinated way to obtain benefits and control not available from managing them individually. Programs may include elements or related work outside the scope of discrete projects in the program.”[2] Furthermore, programs often involve a series of repetitive or cyclical undertakings. In Reclamation, a program is typically a group of projects administered by Reclamation. Reclamation programs do not have to be specifically authorized, and a program’s schedule may continue past any individual project. Examples of Reclamation programs are the Safety of Dams Program, the RAX Program, and the Title 16 Program.[3]
What Is Project Management?
“Project management is the process of the application of knowledge, skills, tools, and techniques to project activities to meet project requirements.”[4][5] That is, project management is an interrelated group of processes that enables the project
team to achieve a successful project. These processes manage inputs to and produce outputs from specific activities; the progression from input to output is the nucleus of project management and requires integration and iteration. For example, a feasibility report could be an input to a design phase; the output of a design phase could be a set of plans and specifications. This progression requires project management acumen, expertise, tools and techniques, including risk management, contingency development, and change control. Figure 1 illustrates the project context, its conceptual boundaries, or scope lines, as well as the process groups required to manage the inputs and deliver the outputs.
The project management process groups depicted in figure 1 are initiating, planning, executing, monitoring and controlling, and closing. Initiating defines and authorizes the project or a project phase. Planning defines and refines objectives and plans the course of action required to attain the objectives and scope that the project was undertaken to address. Executing integrates people and other resources to carry out the project management plan for the project. Monitoring and controlling regularly measures and monitors progress to identify variances from the project management plan so that corrective action can be taken when necessary to meet project objectives. Closing formalizes acceptance of the product, service, or result and brings the project or a project phase to an orderly end.[6] Figure 2[7] illustrates the relative depth, breadth, and interrelationship between these process groups.
Figure 2.
Several significant observations regarding the nature of project management can be made from this figure. The breadth or range of project management is comprehensive—that is, it begins with initiating and continues through closing; these processes are coincident with the start and end of the specific project itself, respectively. Monitoring and controlling occur throughout the duration of the project and have a range relatively similar to that of executing. Indicating a project’s temporary nature and the importance of the timing of the deliverable, closing begins relatively shortly after initiating concludes. Planning and monitoring and controlling have a collective depth similar to that of executing, illustrating that these activities require a level of effort and have a implication similar to that of constructing the product, providing the service, or producing the result.
The level of interaction of the five processes indicates a strong relational dependence not exclusive of one another. One process does not simply end and the next one begins. The presence of this interrelationship and range is a function of progressive elaboration. Projects are executed in increments and details are exposed and developed through the progression of time—objectives are developed, discoveries are made; investigations, studies, and surveys are completed; analysis is performed; constraints are changed; resources are amended; contingencies are exercised; changes are managed; risks are mitigated; and Force Majeure (unforeseeable or unpreventable circumstances) occurs.
To manage the breadth or range of a project, active and proactive project management is required throughout the duration of the project. It cannot be simply initiated and/or planned and left alone; it must be continually planned and monitored and controlled. Sustained reactive project management is indicative of incomplete or absent planning and/or monitoring and controlling.
Project management process groups are not project phases. In fact, the process groups may need to be repeated for each phase, such as study, programming, engineering, procurement, construction, and commissioning. A process group or project phase is not discrete; they are interdependent and require integration. Also, project management must ensure continuity as a project progresses through processes and phases.
What Is Project Success?
A standard must be established by which to define and measure project success. Fundamentally, project success is the delivery of the required product, service, or result on time and within budget. To meet these objectives is to deliver a quality project. PMI illustrates project quality through the concept of the triple constraint—project scope, time and cost.[8] Project quality is affected by balancing these three interrelated factors. “The relationship among these factors is such that if any one of the three factors change, at least one other factor is likely to be affected.”[9] Figure 3 illustrates this constrained relationship, sometimes called the
“iron triangle.”
Figure 3.
Cost and time are intuitive, but the role played by scope warrants further discussion. To understand the significance of scope, one must appreciate the relationship between scope and the project objectives. For the scope to contribute to project quality, it must be managed to meet the demands of the project objective by reliably providing the required functions, nothing more or nothing less. It is not simply a matter of keeping the scope from creeping, or a matter of completing the cheapest and fastest project; it is establishing the appropriate scope and delivering the commensurate product, service, or result.
What Is a Project Manager?
The key responsibility of the project manager is to successfully accomplish the project objectives by balancing the competing demands for quality, scope, time, and cost.[10] Derivative responsibilities include identifying the project requirements; establishing clear and achievable objectives; and adapting the specifications, plans, and approach to the different concerns and expectations of the various stakeholders. Fundamentally, the project manager must direct the project from its inputs, through its nucleus, to delivery of its outputs. In order to accomplish these multifaceted responsibilities, the roles of the project manager include that of a leader, administrator, entrepreneur, facilitator, arbitrator and mediator, liaison, and coordinator.
The project manager must lead teams to operate cross functionally towards a common objective while assuring cohesiveness and continuity as the project progresses through project processes and project phases. “The project manager acts as the key catalyst to stimulate effective communication and coordination between design, procurement and construction activities.”[11]
In order to effectively manage these responsibilities and assume these roles, a project manager must have experience in the following project management knowledge areas: project integration, scope, time, cost, quality, human resources, communications, risk, and procurement management.[12]
What Is a Project Management Plan (PMP)?
A project management plan is a fundamental tool for the project manger to deliver the project successfully. This document is a strategic and formalized roadmap to accomplish the project’s objectives by describing how the project is to be executed, monitored and controlled, which includes creating a project work breakdown structure, identifying and planning to mitigate risk, identifying manners in which to effectively communicate with stakeholders and other project team members, and developing a plan to manage changes. It is essentially a guide for executing the project, and a manner in which to gain buy-in and approval from stakeholders and sponsors prior to commencement. This plan is a living document that is updated and revised throughout the project at strategic milestones or significant events to accommodate the progressive, elaborative nature of the project. The project management plan will vary based on size, complexity, risk, and/or sensitivity of the project. Implementing the project management plan requires competency in all of the project management knowledge areas and is critical to the success of the project.
Summary
A project is temporary, unique, and the product of a multifaceted and progressively elaborated process that produces a solution for a specific objective. For the endeavor to be successful, the project must be accomplished on time, within budget, and to the appropriate degree required to satisfy the objective. For success to be achieved, the project manager must be skilled and operate in an environment which enables a project team to function. Excellence in project management should be viewed as the positive trend in the performance of successful projects.
[1] Carly, Lauren. Project Management Primer. Bureau of Reclamation, 2004, p. 2.
[2] Project Management Institute. A Guide to the Project Management Body of Knowledge: PMBOK® Guide, 3rd Edition. Newtown Square, Pennsylvania, Project Management Institute, 2004, p. 16.
[3] Carly, Lauren. Project Management Primer. Bureau of Reclamation, 2004, p. 2.
[4] Project Management Institute. A Guide to the Project Management Body of Knowledge:
PMBOK® Guide
[5] , p. 37.
[6] Ibid, p. 41.
[7] Ibid, p. 68.
[8] Ibid, p. 8.
[9] Ibid.
[10] Project Management Institute. A Guide to the Project Management Body of Knowledge: PMBOK® Guide, 3rd Edition. Newtown Square, Pennsylvania, Project Management Institute, 2004, p. 8.
[11] Bent, James. Project Management for Engineering and Construction. Englewood Cliffs, New Jersy, Prentice Hall, 1989, p. 2.
[12] Project Management Institute. A Guide to the Project Management Body of Knowledge: PMBOK® Guide, 3rd Edition. Newtown Square, Pennsylvania, Project Management Institute, 2004, pp. 9-10.
CONFIDENTIALITY / COPYRIGHT NOTICE: This site and my information and any attachments contains the PRIVILEGED AND CONFIDENTIAL INFORMATION of Fred Finkelstein & Irondesigner DBA / LLC mutually, Inc., its affiliated corporations or legal entities, and is intended only for the use of the individual(s) named above. If you are not the intended recipient of this e-mail or invited to this site, or the employee or agent responsible for delivering this to the intended recipient, you are hereby notified that any unlawful interception, dissemination, disclosure, printing or copying of this e-mail or site or any attachments is strictly prohibited under the Electronics Communication Privacy Act (ECPA), 18 USCA 2510, 18 USCA 2511, and any applicable laws. If you have received this e-mail or viewing this site in error, please delete or destroy it & close down, including all attachments or copies, and immediately notify us by e-mail at mechanicalengrg@gmail.com