Page 1 of 4Free preview · 1–4

About this document

This February 2018 document distinguishes project management guidelines from standards, challenges six common project management myths, and outlines practical approaches to planning, execution oversight, risk management, and project closure. Recommendations include creating a project charter, refining plans over time, holding kick-off meetings, monitoring warning signs, requiring sponsor approval for scope changes, preventing scope creep, and documenting lessons learned through post-mortem meetings.

Free preview text

The first 4 pages, shown as text so search engines and readers can find this document.

Page 1

1 Project Management Best Practices Mangaiah Chowdary Garikapati February 2018 A best practice is a technique, method, or process that is believed to be more efficient and effective in achieving a goal than any other techniques, methods and processes, when applied to a particular condition or circumstance. Best practice is based on experience and is used to describe the process of developing and following a standard way of doing things. In project management, best practice is a general term that includes: • Guidelines • International standards Both standards and guidelines look to improve project management. In practice, most project managers think that the two concepts are one and the same. Guidelines in project management are methods that can contribute to goal achievement when dealing with projects, whereas standards are expected to be objective, definitive and robust. Guidelines issued by professional bodies are open to interpretation, but, standards issued by specialized organizations are usually based on best practices and guidelines given by professional bodies. However, sometimes guidelines can become standards. Before looking into some of the widely accepted best practices, let’s look into project management myths which everyone should be aware of and have a clear understanding so that these wouldn’t become roadblocks to successful project management. Myths The Project Portfolio must be fixed. Reluctance to shift gears at an organization-wide level is perfectly understandable; it can mean increased costs and schedule delays across the portfolio. But given today’s increasingly complex project environments, organizations must try to build some flexibility into their plans. “Projects are fluid. No matter how much you think of and how much you anticipate, there’s always something else that comes along, you have to adapt the plan to allow for that.” Process outplays people. From work breakdown structures to change control, project management is full of processes. But no organization should forget that it’s people who actually execute projects. “Because the project management process is about accomplishing goals through coordinating the activities of people, the people are generally more important to project management success than the process,” says James Bosak, director, program management at IT giant CA Technologies, Raleigh-Durham, North Carolina, USA. Higher management need details. No, Higher management doesn’t need complete understanding of the day to day task and progress details of every single project across the portfolio. They have a lot to deal with and going into details is impossible and not necessary also. They need to have trust in the project managers and shouldn’t hesitate to get input from them. Project managers should be able to give their management a big picture overview of the status with which they should be able to have a solid overview of the projects and relate them to the strategic goals.

Page 2

2 Execution is everything. We all think that executing a project is the interesting and important part of a project. But it’s not. Successful Project Management clearly needs the best planning possible which can make all other phases run smoothly. A detailed, well thought of project plan answers some key questions about the upcoming effort, including how, when, by whom and for how much. Only through effective project planning can organizations consistently deliver expected benefits and value. A well-managed portfolio means no project backlog. A portfolio with no project backlog looks perfect but it’s not the right way. A slight backlog actually indicates that the organization is moving at the right pace. If not, it means that the organization is pushing its resources too hard to take up all the projects in the pipeline and clear the backlog which will actually impact negatively in the long run and might not yield the expected results after the project completion. Risk management ends when the project begins. Risk management is one of the important parts of a Project Management that it doesn’t end at the launch of the project. It should be practiced across the entire project life cycle. Organizations should first identify risks, then they should conduct an analysis of their tolerance for those risks, as well as a response strategy. But organizations also need to establish an ongoing process for monitoring and responding to risks that weren’t identified in the preliminary project planning. Best Practices Now let’s get to the interesting part. There are many advantages of using best practices. They not only advise you on how to be a successful project manager but also help you avoid any unforeseen issue which usually is not thought of. Plan the work by creating Project Charter document. As already mentioned in one of the myths, planning is the most important part of a project. The tendency to shortchange the planning process and jump right into the execution should be controlled and more emphasis needs to be put in planning the work thoroughly. The importance of this practice can’t be stressed enough. The project charter is the primary deliverable from the planning process and describes all aspects of the project at a high level. Once approved by the relevant stakeholders, it becomes the basis for the work to be performed. Create a planning horizon. A detailed project plan will have everything about how the project will be completed. So more time and emphasis should be placed on creating Advantages of using best practices Transfer of knowledge Better communication Time and cost savings Better process quality Better process quality Better team work Better monitoring & controlling

Page 3

3 the project plan with as much details as possible. High-level activities that were initially vague need to be defined in more detail as their time frame gets closer. Have a Project Kick-Off meeting. Having a kick-off meeting is as important as carefully planning a project and documenting it. This meeting provides a stage to set the ground rules for the project and also get the views and opinions from the team and other stakeholders if they are in agreement with the process and procedures. This will also help in • Communicating the business driver of the project to the team • Establishing goals • Explaining the project delivery methodology • To build common vision with all the stakeholders. Keep a watch on warning signs. The Project Manager should always keep a watch on warning signs which may push the project off course. These signs keep showing up in various forms and an effective project manager should be able to catch them in time and avoid them. These warning signs include • Small variances in schedule or budget • Change in team morale • Change in quality • Frequent unexpected issues These may seem small day to day operational issues but there might be a bigger problem lying behind them, which, if not caught and solved, might impact the entire project. Ensure that the sponsor approves scope-change requests. This may sound very obvious but sometimes it gets missed which leads to bigger problems. However small the change request be, if its impacting the project constraints, it needs to go through a change request with formal approval from sponsor who is the only one who can add additional funding to cover the changes and know if the project impact is acceptable. Safeguard against scope creep. Scope creep is a series of small changes in scope which are made to the project without using change management procedures. Individually these changes may not impact the project constraints but they can accumulate and have a significant impact on the overall project. Project managers should be diligent enough to lookout for the scope creep and make sure that any kind of changes go through a formal process which will help in identifying the necessary and unnecessary changes. Identify risks during planning. It is very crucial to identify risks and mitigations during the planning phase to minimize their impact on the project. And effective project manager may not be able to identify all the risks associated but should be able to identify most of the risks in the beginning of the project itself to be able to create a mitigation plan and make sure that they don’t become issues during the life of the project.

Page 4

4 PMs can use information from similar projects if exists to be able to identify all the possible risks irrespective of the feeling of their occurrence in that specific project. PMs should also leverage multiple tools or build own tools like custom surveys and brainstorming to be able to identify potential risks. Lookout for potential risks throughout the project. Project manager’s role in risk management doesn’t end after planning phase. Risks are the biggest threats for a project and they can creep in at any stage of the project. So a PM should perform updated risk assessment in regular intervals to see that no new risks have surfaced which needs to be planned and mitigated properly. Understand the difference between a risk and an issue. It’s very common for project managers to mistake an issue for risk and vice versa. In both cases it will become a bigger problem as the plan is different for managing and risk compared to managing an issue. A risk as an event that has not happened yet and an issue is something that already has happened. An issue needs to be checked almost every day or week as it has already happened but a risk need to be checked only periodically. PMs should be able to differentiate between these two and take necessary action to solve or mitigate them accordingly. Have a Project Post-Mortem meeting. One of the most commonly ignored phases in project management is closing. Closing the project effectively not only improves the project quality but also helps other future projects to refer to this project for useful data like lessons learned. Project post mortem meeting with all stakeholders helps in identifying all the good and bad happened in the project and will help PM to document the lessons learned effectively. All the lessons learned should be placed in a central repository and made available for all PMs. Post-mortem should be scheduled right after the project is completed while the details are still fresh in memory and should be conducted in a constructive manner to identify the possible improvements if a similar project is undertaken in future.

Tags

Doxxly editorial guide

Project Management Best Practices: summary, contents and background

This guide helps you understand the scope of Project Management Best Practices before or alongside reading the original document. It is based on the catalogue record, credited creator, source, classification and topics shown on this page. It does not replace the original work and does not invent claims about passages that Doxxly cannot verify.

Summary and overview

Project Management Best Practices is a 4-page documentcredited to Petra S. Underhill. This February 2018 document distinguishes project management guidelines from standards, challenges six common project management myths, and outlines practical approaches to planning, execution oversight, risk management, and project closure. Recommendations include creating a project charter, refining plans over time, holding kick-off meetings, monitoring warning signs, requiring sponsor approval for scope changes, preventing scope creep, and documenting lessons learned through post-mortem meetings. It appears in the Business & Economics collection, which groups it with other material that readers may use for comparison and further study.

The item can be approached in several ways. A reader looking for a quick orientation can begin with the free five-page preview, inspect the page structure and use the metadata to judge relevance. Someone undertaking deeper research can work through the complete file, search its indexed text, record useful page references and compare its treatment of Project Management, Best Practices, Project Planning, Portfolio Management, Risk Management, Scope Management, Change Control, Lessons Learned with the related resources linked below.

Rather than reducing the work to a single claim, this page treats it as a source that should be read in context. The title, creator, publication source, licence and format all help explain what kind of evidence it may offer. Readers should distinguish the original author's statements from Doxxly's catalogue description, and should cite the original edition when using the material in academic, professional or published work.

Key topics and reader takeaways

The catalogue connects this document with Project Management, Best Practices, Project Planning, Portfolio Management, Risk Management, Scope Management, Change Control, Lessons Learned. These terms offer practical entry points rather than a substitute for close reading. Start by identifying the definitions, examples, arguments, tables or visual explanations attached to each topic. Then note where the creator draws connections, makes distinctions or moves from background material to a conclusion, recommendation, calculation or narrative development.

A useful reading method is to separate description from interpretation. First record what the item actually presents: names, headings, figures, formulas, quotations or stated propositions. Next consider why those details matter within the whole work. Finally compare them with another source from the same subject area. This process helps turn a long digital file into evidence that can be evaluated rather than merely skimmed.

Table of contents and reading guide

The following is an editorial content guide based on the verified catalogue topics. It is not represented as the original author's formal table of contents. Use it to organise notes while moving through the 4 pages in the player.

  1. Part 1

    Project Management

    Use this section of the reading guide to identify how Project Management appears in Project Management Best Practices, note important terms, and connect the subject to the wider purpose of the work.

  2. Part 2

    Best Practices

    Use this section of the reading guide to identify how Best Practices appears in Project Management Best Practices, note important terms, and connect the subject to the wider purpose of the work.

  3. Part 3

    Project Planning

    Use this section of the reading guide to identify how Project Planning appears in Project Management Best Practices, note important terms, and connect the subject to the wider purpose of the work.

  4. Part 4

    Portfolio Management

    Use this section of the reading guide to identify how Portfolio Management appears in Project Management Best Practices, note important terms, and connect the subject to the wider purpose of the work.

  5. Part 5

    Risk Management

    Use this section of the reading guide to identify how Risk Management appears in Project Management Best Practices, note important terms, and connect the subject to the wider purpose of the work.

  6. Part 6

    Scope Management

    Use this section of the reading guide to identify how Scope Management appears in Project Management Best Practices, note important terms, and connect the subject to the wider purpose of the work.

  7. Part 7

    Change Control

    Use this section of the reading guide to identify how Change Control appears in Project Management Best Practices, note important terms, and connect the subject to the wider purpose of the work.

  8. Part 8

    Lessons Learned

    Use this section of the reading guide to identify how Lessons Learned appears in Project Management Best Practices, note important terms, and connect the subject to the wider purpose of the work.

When a heading in the original differs from this guide, follow the original heading in your citation. Page numbers can also vary between editions. Doxxly's direct page field is useful for navigation, but formal references should include the title, creator, source and edition details available in the file itself.

About Petra S. Underhill

Doxxly credits Petra S. Underhill as the author or creator of Project Management Best Practices. This page does not add an unverified biography, job title or institutional affiliation. The attribution is preserved so readers can distinguish the creator from the hosting library and follow the original record when an external author link is available.

Author context matters because a work reflects a particular purpose, audience and point of view. Before relying on the material, consider what the creator set out to explain, when the source was produced and whether later research or revised guidance should also be consulted. For literature and philosophy, compare translations and editions; for technical material, check whether a newer version has superseded the one shown here.

About the source organisation

The recorded source for this item is doit.niu.edu. Doxxly provides access and discovery tools but does not claim to be the original publisher unless explicitly stated. Source links, creator attribution and the recorded Publicly available file collected for editorial review licence are displayed to help readers assess provenance and permitted use.

Provenance is especially important for reports, standards, presentations and working spreadsheets. Check the original source for amendments, supporting files and current policy. A trustworthy research workflow keeps the source URL with any notes or downloaded copy, verifies important figures against the original, and avoids treating an archived document as automatically current.

Visit doit.niu.edu

How to read and use this document

Begin with the title and opening pages, then use the guide above to decide whether to read sequentially or move to a particular topic. The Doxxly player provides previous and next navigation, a direct page field, zoom steps, fit-to-width and fit-to-page modes, rotation and fullscreen. These controls are useful when a page contains small type, a wide table, an image, a scanned layout or a dense sequence of notes.

The first five pages are open to every visitor. A plan unlocks the complete item and full-document search. Search is best used for distinctive names, technical terms or short phrases; broad words can produce too many possible contexts. When you find a useful passage, read the surrounding pages so that a sentence, chart or formula is not separated from its explanation.

If downloading is enabled, members can obtain the original PDF file. Keep the original format when formulas, slide sequencing, pagination or layout carries meaning. Respect the Publicly available file collected for editorial review terms displayed on this page, and use the rights-report link if you believe the attribution or availability needs review.

Research questions to consider

As you read Project Management Best Practices, ask which audience the creator addresses, what problem or idea organises the work, what evidence is presented, and which assumptions remain unstated. Note whether important terms are defined consistently and whether examples represent a broader pattern or a narrow case. For quantitative material, record units, time periods, formulas and data sources. For interpretive material, separate the creator's language from your own summary.

A second set of questions concerns relevance today. Which parts remain durable, which depend on their historical or institutional setting, and what would need confirmation from a newer source? Following the tags and the Business & Economics collection can reveal useful comparisons. Agreement between sources can strengthen confidence, while disagreement can point to changing definitions, methods, evidence or priorities.

Finally, decide what you need from the item: background knowledge, a quotation, a worked example, a model, a visual explanation or a starting bibliography. That purpose should guide the depth of reading and the notes you keep. Doxxly helps locate and navigate the source; careful interpretation remains the reader's responsibility.

Explore more Business & Economics resources

Frequently asked questions about Project Management Best Practices

Practical answers about reading, downloading and understanding this document on Doxxly.

More in Business & Economics