An overview of project lifecycle phases drawing on multiple project management methodologies. The document covers determining whether a project is needed, planning and stakeholder identification, project documentation, monitoring progress and managing change, and project closure. Each phase includes practical questions to guide decisions, communication, assessment, and lessons learned.
Free preview text
The first 4 pages, shown as text so search engines and readers can find this document.
Page 1
Project Management Best Practices
This document is intended to provide an overview of phases in project lifecycles. It includes brief
descriptions of phases as well as potential questions to consider at each phase. It does not adhere to a
single project management methodology but draws from multiple. More specific documentation that
elaborates on project management processes and templates will be linked here as created.
Before you begin 1
Starting a project 1
Project documentation 2
Projects in progress 3
Ending a project 4
Before you begin
Before you formally initiate a project, ensure that a project is necessary. A project has a clear
beginning and end as well as clear objectives. A project will solve a problem by providing new or
improved products, services, or processes.
Questions to ask:
● What is the problem you are trying to solve?
● Is this something that has a clear end?
● Do your colleagues and management agree that your problem is “a problem”?
● Would a SWOT analysis be helpful in defining your project?
● Has someone else already solved this problem somewhere else? Can you borrow from
their work?
● Has someone else already attempted to solve the problem at your institution? What was
the result and why was it successful / not successful?
Starting a project
Once you have determined that this problem is best solved by a project, begin the project
planning and pre-work. This is a time to develop documentation that will guide the project -
those who work on it, the tasks it undertakes, and the output it produces. While everyone may
be excited to begin working on the project immediately, spending time to develop
documentation generally will reduce unnecessary work or rework and keep everyone on track in
the longer term. Some projects may lend themselves to a lightweight approach and won’t
require all the documents described here, but it’s useful to be familiar with the full breadth of
available tools.
Page 2
Pre-project work is the phase in which a problem is identified, defined, and information about
the problem is gathered. This information can include details about the current state of practice
at your institution as well as information from an environmental study. Pre-project work also
includes the identification of stakeholders such as: end-users/customers, managers, project
managers, those doing the work, those funding the work as applicable, and any generally
interested parties.
Questions to ask:
● What resources do you need? (people, money, material, time)
● Who are the right people to solve your problem?
● Do you require a domain or subject matter expert to understand the problem and solve
it?
● What is the priority of this project in relation to other projects and ongoing work?
● Who needs to “buy-in” or approve before you can begin?
● Who are the anticipated users of the product or service?
● Who and what will be impacted by the new product or service?
● Will any users of the service or product need training before the product or service
launches?
● Think about: owners of and a plan for ongoing commitment.
Project documentation
The documentation developed while starting a project can include a project charter (see: TRLN
Project Charter Template) or project plan, a communication plan, schedule, budget, supporting
information in a project management tool, and any other supplemental information. These
documents will provide in-depth information about people (see: TRLN Project Roles Definitions
and Template): project team members and their roles, stakeholders and their needs, and
communication expectations. The documents will also define the project’s end result: goals,
functional requirements, deliverables, and what is in or out of scope. Finally, the documents will
address the things that impact projects: budgets, timelines, risks, and change processes.
Hold a kickoff meeting either prior to creating documentation or once documentation has been
finalized. Regardless of timing of the kickoff meeting, ensure that all key individuals sign off on
the project charter/plan so that everyone involved can proceed to the goals with the same
expectations for success. Use the project charter/plan to get buy-in from stakeholders (both
those who control resources for your project and those who will be impacted by your project).
Questions to ask:
● What is the project’s goal and scope? What is (are) the associated deliverable(s)?
● Who is involved in or impacted by the project?
● What are the project limitations and constraints (time, budget, challenges)?
Page 3
Projects in progress
Now that the project is underway, your well-articulated plan, timeline, and stakeholder
identification will help you to keep the project on track. However, even with excellent planning
and the best intentions, projects will inevitably get messy.
As the project manager, ensure that you perform regular, scheduled assessments with your
team and check-in with the stakeholders. Communication is essential throughout a project’s
lifecycle! It is often beneficial to use prototyping, mockups, and beta testing to gather feedback
at multiple points in the process, which also helps your team to embrace risk taking, failure, and
iteration.
In all of your communications with the team, be honest about the project’s progress, challenges
(aka roadblocks), and remaining work. It is hard to be honest, especially if the project has
encountered problems. Don’t be afraid; be clear about issues. Your team and your stakeholders
respect honesty. You can do it! Enlist the help and support of management when needed if your
team members are not delivering as promised. Conversely, don’t hesitate to celebrate victories,
however small, and acknowledge progress.
Be open to change - in goals, scope, schedule, budget, and stakeholders - but do not let it
manage the project. If a change occurs that impacts the project, make sure to update the
documentation so that you have a record moving forward. Don’t be tempted to over deliver or to
dive down every rabbit hole or tangent. Remember that you can always create new, related, or
follow up projects for things that are worthwhile; but if you continually move the goals for your
current project, you prevent progress.
Questions to ask:
● Re-read your project charter - does it resonate with the work you and the team are
actually doing? Or are you now doing a completely different project?
● Are you following through with your communication plan?
● Is the project still in scope? Is the scope creeping?
● Is the timeline still achievable? Why or why not?
● Where are the roadblocks? Who can address these issues?
● Have you learned anything that indicates a need for changes to your project?
● Are you over-delivering?
● Are you assessing & measuring the right things to ensure success?
Ending a project
Once the new or redefined product, service, or process has been delivered and accepted, the
project is complete. Any ongoing or maintenance work should be considered regular work, not
part of the project. In addition to getting formal approval that the work is complete, the end of the
Page 4
project is also the time to assess the project as a whole (see: TRLN Gathering Feedback matrix)
to better inform future projects, finalize and archive project documentation and lessons learned,
and celebrate success. If the team is tracking their time, the end of a project presents an
excellent opportunity for consolidating this data. Although it can be challenging for teams to
embrace time tracking, it is the best method for predicting the resources required for similar
projects in the future.
Although not essential, it is beneficial to document the end of project assessment as a report
and archive it with other project documentation. It is not overly time-consuming to produce an
end of project report, and as it is sometimes required for grants it is a good habit to form.
Regardless of how the end of project assessment is conducted, it is important to recognize team
members’ contributions and show appreciation for their efforts. It is also beneficial to officially
inform all project team members that the project is over, their work is complete, and they are
free to focus on other tasks and projects.
Questions to ask:
● Did you meet the project’s goals?
● Did you receive sign-off on the deliverable?
● Have you transitioned any service/support work to those responsible for it?
● What lessons did you learn? How can you use them and your project’s information to
improve a future project?
● Did you thank your team and your stakeholders? Is there an opportunity to thank your
team publicly or announce your results widely?
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 Ada I. Hollis. An overview of project lifecycle phases drawing on multiple project management methodologies. The document covers determining whether a project is needed, planning and stakeholder identification, project documentation, monitoring progress and managing change, and project closure. Each phase includes practical questions to guide decisions, communication, assessment, and lessons learned. It appears in the Technology & Security 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, Project lifecycle, Project planning, Project documentation, Stakeholder communication, Scope management, Project closure, 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, Project lifecycle, Project planning, Project documentation, Stakeholder communication, Scope management, Project closure, 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.
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.
Part 2
Project lifecycle
Use this section of the reading guide to identify how Project lifecycle appears in Project Management Best Practices, note important terms, and connect the subject to the wider purpose of the work.
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.
Part 4
Project documentation
Use this section of the reading guide to identify how Project documentation appears in Project Management Best Practices, note important terms, and connect the subject to the wider purpose of the work.
Part 5
Stakeholder communication
Use this section of the reading guide to identify how Stakeholder communication appears in Project Management Best Practices, note important terms, and connect the subject to the wider purpose of the work.
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.
Part 7
Project closure
Use this section of the reading guide to identify how Project closure appears in Project Management Best Practices, note important terms, and connect the subject to the wider purpose of the work.
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 Ada I. Hollis
Doxxly credits Ada I. Hollis 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 trln.org. 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.
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 Technology & Security 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.