Page 1 of 6Free preview · 1–5

About this document

A practical guide to proactive project management, using a migration from Microsoft Exchange 5.5 to Exchange 2000 as an example. It covers project definition, workplan development, planning horizons, management procedures, schedule and budget monitoring, scope-change approval, scope creep, risk assessment, and issue resolution. The document emphasizes disciplined planning, monitoring, and control rather than reactive execution.

Free preview text

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

Page 1

Project management best practices www.techrepublic.com Project management best practices Project management processes and techniques are used to coordinate resources to achieve predictable results. All projects need some level of project management. The question is whether the project will be managed reactively or proactively—ad-hoc or in a structured, disciplined manner. Consider these questions: • All technology migrations encounter unexpected problems, also known as issues. Do you resolve the problems proactively using a predefined process, or do you hesitate when the problems arise—not knowing exactly who to seek or how to resolve them? • Infrastructure projects, such as a migration from Microsoft Exchange 5.5 to Exchange 2000, can touch everyone. There is always some cloud of uncertainty or a risk that events will not occur as they are planned. Do you proactively manage the risks to resolve them before they happen, or do you wait until the problems arise and deal with the consequences? • There can be many stakeholders in technology migrations, each of whom may have benefits they would like to see fulfilled by this project. Are you going to manage scope aggressively and proactively or wait until you are hopelessly over budget and past your deadline before you realize that you’re doing work that was not in your original project scope? Studies prove that most projects, especially large ones, do not end successfully. Given the odds, you might think that companies would be happy to just have their project finish with some degree of success. However, in spite of the odds, organizations also expect projects to be completed faster, cheaper, and with higher quality. The only way that these objectives can be met is through the use of effective project management processes and techniques. Consider the size, complexity, and other characteristics of your project, and build the right project management processes to effectively manage and control your project. There’s a common saying among project managers: Plan the work and work the plan. In essence, that is the key to successful project management. You must first plan out the project and then monitor and control the execution of the program work. What follows is a step-by-step best practices guide, which uses a migration from Microsoft Exchange 5.5 to Exchange 2000 as an example. Planning It’s hard to overestimate the importance of proper planning for a project such as an Exchange migration. In general, project failures can most often be traced back to deficiencies in the planning process. There are three major deliverables from the project planning process—the project definition, the workplan, and the project management procedures. ©2001 TechRepublic, Inc. www.techrepublic.com. All rights reserved.

Page 2

Project management best practices www.techrepublic.com Project definition Best practice: Plan the work by utilizing a project definition document. There is a tendency for IT infrastructure projects to shortchange the planning process, with an emphasis on jumping right in and beginning the work. This is a mistake. The time spent properly planning the migration will result in reduced cost and duration and increased quality over the life of the project. The project definition is the primary deliverable from the planning process and describes all aspects of the project at a high level. Once approved by the customer and relevant stakeholders, it becomes the basis for the work to be performed. The project definition should include the following: • Project overview—Why is the Exchange migration taking place? What are the business drivers? What are the business benefits? • Objectives—What will be accomplished by the migration? What do you hope to achieve? • Scope—What features of Exchange 2000 will be implemented (i.e., e-mail, chat, instant messaging, conferencing)? Which departments will be converted? What is specifically out of scope? • Assumptions and risks—What events are you taking for granted (assumptions), and what events are you concerned about? Will the right hardware and infrastructure be in place? Do you have enough storage and network capacity? • Approach—How will the migration project unfold and proceed? • Organization—Show the significant roles on the project. Identifying the project manager is easy, but who is the sponsor? It might be the CIO for a project like this. Who is on the project team? Are any of the stakeholders represented? • Signature page—Ask the sponsor and key stakeholders to approve this document, signifying that they agree on what is planned. • Initial effort, cost, and duration estimates—These should start as best-guess estimates and then be revised, if necessary, when the workplan is completed. Project workplan After the project definition has been prepared, the workplan can be created. The workplan provides the step-by-step instructions for constructing project deliverables and managing the project. You should use a prior workplan from a similar migration effort as a model, if one exists. If not, build one the old-fashioned way by utilizing a work-breakdown structure and network diagram. Best practice: Create a planning horizon. Create a detailed workplan, including assigning resources and estimating the work as far out as you feel comfortable. This is your planning horizon. Past the planning horizon, lay out the project at a higher level, reflecting the increased level of uncertainty. The planning horizon will move forward as the project progresses. High-level activities that were initially vague need to be defined in more detail as their time frame gets closer. ©2001 TechRepublic, Inc. www.techrepublic.com. All rights reserved.

Page 3

Project management best practices www.techrepublic.com Project management procedures Best practice: Define project management procedures up front. The project management procedures outline the resources that will be used to manage the project. It will include sections on how the team will manage issues, scope change, risk, quality, communication, and so on. It is important to be able to manage the project rigorously and proactively and to ensure that the project team and all stakeholders have a common understanding of how the project will be managed. If common procedures have already been established for your organization, utilize them on your project. Manage and control Once the project has been planned sufficiently, execution of the work can begin. In theory, since you already have agreement on your project definition and since your workplan and project management procedures are in place, the only challenge is to execute your plans and processes correctly. Of course, no project ever proceeds entirely as it was estimated and planned. The challenge is having the rigor and discipline needed to apply your project management skills correctly and proactively. Manage the workplan Review the workplan on a regular basis to determine how you are progressing in terms of schedule and budget. If your migration effort is small, this may need to be weekly. For larger migration projects, the frequency might be every two weeks. ID 1 2 3 4 5 6 S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M Mar 4, '01 Mar 11, '01 Mar 18, '01 Mar 25, '01 Apr 1, '01 Apr 8, '01 Apr 15, '01 Apr 22, '01 Apr 2 • Monitor the schedule. Identify activities that have been completed during the previous time period and update the workplan to show they are finished. Determine whether there are any other activities that should be completed but have not been. After the workplan has been updated, determine if the project will be completed within the original effort, cost, and duration. If not, ©2001 TechRepublic, Inc. www.techrepublic.com. All rights reserved.

Page 4

Project management best practices www.techrepublic.com determine the critical path and look for ways to accelerate these activities to get you back on track. • Monitor the budget. Look at the amount of money your project has actually consumed and determine whether your actual spending is more than originally estimated based on the work that has been completed. If so, be proactive. Either work with the team to determine how the remaining work will be completed to hit your original budget or else raise a risk that you may exceed your allocated budget. Cost By Month and Variance 0 5000 10000 15000 20000 25000 Jan Feb M ar April Variance YTD Dollars Budget Actuals Best practice: Look for warning signs. Look for other signs that the project may be in trouble. These could include the following: • A small variance in schedule or budget starts to get bigger, especially early in the project. There is a tendency to think you can make it up, but this is a warning. If the tendencies are not corrected quickly, the impact will be unrecoverable. • You discover that activities you think have already been completed are still being worked on. Users whom you think have been migrated are still not. • You need to rely on unscheduled overtime to hit the deadlines, especially early in the project. • Team morale starts to decline. • Deliverable quality or service quality starts to deteriorate. For instance, users start to complain that their converted e-mail folders are not working correctly. • Quality-control steps, testing activities, and project management time starts to be cut back from the original schedule. This migration project can affect everyone in your organization. Don’t cut back on the activities that ensure the work is done correctly. If these situations occur, raise visibility through risk management, and put together a plan to proactively ensure that the project stays on track. If you cannot successfully manage through the problems, raise an issue. Manage scope After the basics of managing the schedule, managing scope is the most important activity required to control a project. Many project failures are not caused by problems with estimating or team skill sets but by the project team working on major and minor deliverables that were not part of the original project ©2001 TechRepublic, Inc. www.techrepublic.com. All rights reserved.

Page 5

Project management best practices www.techrepublic.com definition or business requirements. Even if you have good scope-management procedures in place, there are still two major areas of scope-change management that must be understood to be successful: understanding who the customer is and scope creep. Best practice: Ensure that the sponsor approves scope-change requests. In general, the project sponsor is the person funding the project. For infrastructure projects like an Exchange migration, the sponsor might be the CIO or CFO. While there is usually just one sponsor, a project like the Exchange migration could have many stakeholders, or people who are impacted by the project. Requests for scope changes will most often come from stakeholders—many of whom may be managers in their own right. One manager might want chat services for their area. Another might want an exception to the size limits you have placed on mailboxes. It doesn't matter how important a change is to a stakeholder, they cannot make scope-change decisions, and they cannot give your team the approval to make the change. In proper scope-change management, the sponsor (or their designate) must give the approval, since they are the only ones who can add additional funding to cover the changes and know if the project impact is acceptable. Best practice: Guard against scope creep. Most project managers know to invoke scope-change management procedures if they are asked to add a major new function or a major new deliverable to their project. However, sometimes the project manager doesn’t recognize the small scope changes that get added over time. Scope creep is a term used to define a series of small scope changes that are made to the project without scope-change management procedures being used. With scope creep, a series of small changes—none of which appear to affect the project individually—can accumulate to have a significant overall impact on the project. Many projects fail because of scope creep, and the project manager needs to be diligent in guarding against it. Manage risk Risks refer to potential events or circumstances outside the project team’s control that will have an adverse impact on the project. Best practice: Identify risks up front. When the planning work is occurring, the project team should identify all known risks. For each risk, they should also determine the probability that the risk event will occur, as well as the potential impact to the project. Those events identified as high-risk should have specific plans put into place to mitigate them to ensure that they do not, in fact, occur. Medium risks should be evaluated, as well, to see if they should be proactively managed. (Low-level risks may be identified as assumptions. That is, there is potential risk involved, but you are “assuming” that the positive outcome is much more probable.) Some risks are inherent in a project like this that can impact every person in the company. Other risks may include not having the right level of expertise, unfamiliarity with the technology, and problems integrating smoothly with the rest of Windows 2000. Best practice: Continue to assess potential risks throughout the project. Once the project begins, periodically perform an updated risk assessment to determine if other risks have surfaced that need to be managed. ©2001 TechRepublic, Inc. www.techrepublic.com. All rights reserved.

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 6-page documentcredited to Ivo Y. Kestrel. A practical guide to proactive project management, using a migration from Microsoft Exchange 5.5 to Exchange 2000 as an example. It covers project definition, workplan development, planning horizons, management procedures, schedule and budget monitoring, scope-change approval, scope creep, risk assessment, and issue resolution. The document emphasizes disciplined planning, monitoring, and control rather than reactive execution. 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, Project planning, IT infrastructure, Technology migration, Scope management, Risk management, Issue management, Microsoft Exchange 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 planning, IT infrastructure, Technology migration, Scope management, Risk management, Issue management, Microsoft Exchange. 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 6 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

    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.

  3. Part 3

    IT infrastructure

    Use this section of the reading guide to identify how IT infrastructure appears in Project management best practices, note important terms, and connect the subject to the wider purpose of the work.

  4. Part 4

    Technology migration

    Use this section of the reading guide to identify how Technology migration appears in Project management best practices, note important terms, and connect the subject to the wider purpose of the work.

  5. Part 5

    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.

  6. Part 6

    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.

  7. Part 7

    Issue management

    Use this section of the reading guide to identify how Issue management appears in Project management best practices, note important terms, and connect the subject to the wider purpose of the work.

  8. Part 8

    Microsoft Exchange

    Use this section of the reading guide to identify how Microsoft Exchange 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 Ivo Y. Kestrel

Doxxly credits Ivo Y. Kestrel 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 acqnotes.com. 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 acqnotes.com

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