Home > Articles > Home & Office Computing > Microsoft Windows Server

The Action (Project) Plan and Cost Justification of the Project

  • Print
  • + Share This

To migrate to Windows 2000 effectively, you need an action plan. In this selection, the authors show you how to create a project plan and a cost justification scheme.

With the premigration assessment complete, it is time to develop what is typically called the project plan. A "project plan", however, seems to imply something sedentary, a document that sits on the shelf. Let's call it an action plan instead—after all, it must be active; it defines actions that must be accomplished. The action plan defines the scope and the participants in the design of the Windows 2000 enterprise and the migration from the existing environment.

Clearly, the value of an action plan is to put the project in order, make assignments for completing the tasks and subprojects, and provide a visible document that can be used to measure progress and success. By laying out all the tasks and responsibilities in document form, it is easy for design team members to ensure that all necessary parts are there and, most importantly, that they are in proper sequence. Recording comments, progress notes, and completion of tasks is also enabled by a formal plan.

Many possible tasks, projects, subprojects and organizational methods could make up the action plan. The intent here is to present possibilities that can be used, discarded, or expanded upon rather than to define a template to allow the design leader to just fill in the blanks. Although all companies will have commonalities with other implementers of Windows 2000, each will have many differences concerning political organization, geographical organization, security requirements, and applications.

In this chapter, the essential elements of the action plan are described, including these:

  • The design team—Who should be on this team, what expertise the members should have, and what migration assignments should be made.

  • The purpose, objectives, and scope of the migration project—How to define exactly what will be accomplished, and how to measure the project's success.

  • Cost justification—Calculation of return on investment (ROI) and total cost of ownership (TCO) to gain financial support for the project through measurable results.

The Design Team

The design of the Windows 2000 environment involves many people from many organizations and disciplines. To make the migration successful, the designer must enlist their help and form a Windows 2000 design team to ensure that all issues have been addressed and to get people to buy in to the project. The design team should include people who can address the issues noted in this section and any others that may uniquely apply to your organization.

Involve more than one person in an area, if necessary, but try to keep the group small. While the areas of expertise described in this section are typical, the designer must decide whether those areas apply to his situation or whether other areas should be listed. In a manufacturing facility, for instance, engineering, production, and management staffers would need to be involved. A business organization, on the other hand, wouldn't have any of those functions. Likewise, a software engineering firm might not have (or need) any administration over the desktop, so two or three people would comprise the team. This list is intended to give direction and prompt ideas, not to serve as the final answer.

Design Team Members

I talked to one company about the makeup of its design team and learned that it was just made up of people who were interested in joining. I noticed, however, that the people who were interested also held key roles in the existing domain and network structure. The point here is that it is probably more important to find the right people from the right areas than just having those groups represented. These "right people" must have sufficient interest and enthusiasm (as well as time) for a Windows 2000 migration so that they are motivated to meet schedules and to do quality work that will ensure the project's success. Obviously, you need the right disciplines, such as networking and DNS, as well.

Table 3.1 identifies the job titles or functions of design team members from three companies that I worked with on Windows 2000 design reviews. This list is intended to show the diversity as well as commonality of design team members in different enterprises. This should give the architect some ideas of who should make up the design team in an enterprise.

Table 3.1 Design Team Members for Sample Companies

Company A
(Food Industry)

Company B
(Financial Institution)

Company C
(Computer Company)

Director of Business and Technical Services

Network and workstation support

RAS/tunneling

Team member of the Technical Planning Group (two attendees)

Workstation support

Desktop

Team member of the Workstation Planning Group

Microsoft consulting

Mail and messaging

Manager of the Technical Planning Group

TCO

Help desk

Manager of Client Services

Construction

Security

Team member of network management (telecom)

Network support

Information systems Management

Program director of Technical Services

Information technology

DNS/DHCP/WINS

Team member of Security Services

Information security

Tools

Manager of Workgroup Servers

LAN administration

IIS

Team member of Workgroup Servers

 

Applications Network(physical)


While the titles and functions of team members will vary, definite roles in the Windows 2000 migration plan must be filled. The following list identifies these roles. Note that this is a generic list that probably includes some areas that do not apply to your enterprise, or that might not include areas that you need. Use this as ideas to form your own team.

  • Project lead (and documentation)

  • Network infrastructure: DNS administration, routing protocols, and WAN administration

  • Telecommunications

  • Network administration

  • Information technology

  • Network security

  • Messaging

  • Domain administration

  • Application development and support

  • Workstation and desktop

  • Technical support

  • Appropriate levels of management

  • Field office support

  • Engineering

  • Manufacturing and production

  • Management sponsor

  • Consultants

  • Internal special projects

  • Administrators of other OSs that will impact or be impacted by Windows 2000 (NetWare, Banyan Vines, and so on)

Windows 2000 Design Tasks

Windows 2000 design tasks don't exactly map to the titles, organizations, and responsibilities shown above. The members must be assigned to the Windows 2000 tasks listed here according to their expertise.

When the team is identified, the members must be assigned to specific tasks associated with the design, migration, and implementation of Windows 2000. The assignments usually are made by the project leader.

If you read five books on Windows 2000 deployment, you will have five different lists of Windows 2000 design topics. The three companies noted in the previous section all constructed their design teams similarly, but had some differences. For a base, let's list all the tasks that must be covered to accomplish the design. Note that some of the subtopics might not require a separate person to manage them; they are listed with the intent of defining important subtasks, and it is up to the project leader to determine the size of the assignment for each team member. Refer to Table 3.2 for a sample list of design assignments.

Table 3.2 Windows 2000 Design Assignments

Team

Assignments

Active Directory Design

Namespace design

 

(Structure and administration for DNS and domain)

 

Replication topology and site design

 

Group Policy design and planning

Physical Network Analysis

Protocols

 

DHCP, WINS

 

Remote access

 

Hardware

Security

 

Migration

Planning and strategy

 

Transition

 

Interoperability (resource access and third-party operating systems)

Backup and Recovery

 

Mail and Messaging

 

Applications

 

Tools

 

Desktop Deployment

 

Training

 

Company-Specific Projects

Testing (performance and sizing)


Again, for comparison, Table 3.3 shows action plan task lists from two actual companies for their Windows 2000 deployment plans.

Table 3.3 Action Plan Tasks for Actual Companies

Company D

Company E

Group policy design and planning

Project manager

Training

Program management

RAS and tunneling

Product manager

Security

Process project manager

DNS/DHCP/WINS

Consulting

Mail and messaging

Active Directory design

IIS

Security

Applications

Base operating system

Transition

Testing

Network

TCO

Tools

Networking

Backup

Application integration

Domain migration

Deployment

Directory monitoring

 

Enterprise administrator

 

Terminal server

 

SMS

 

Server monitoring

 

Desktop

 

   IntelliMirror

 

   Client side caching

 

   Software distribution

 

   Wins9x dir svc client

 

Migration planning

 

   User accounts

 

   Domains

 

   OU structure

 

Policies/standards/implementation

 

Project plan review

 


The difference is not only the approach these two example companies take in identifying the action plan tasks, but also in their internal organization, which is quite evident from these two lists. Both lists are valid because they work for their respective situations, and that is most important in a Windows 2000 design scenario. The plan must address not only the issues presented by the migration and the Windows 2000 technical features, but also the internal requirements of the company or business undertaking the migration.

Note that neither plan specifically lists a management sponsor. We can assume that the companies have upper management support for the project but did not list it in the plan. I'm a proponent of listing details and would recommend listing the management sponsor who can carry issues to upper management that need attention; the project manager can manage technical details.

Because Company E's list is considerably shorter than Company D's list, we can assume that Company E has subdivided these tasks to accomplish all the tasks noted in our original task list. Leave task subordination and project planning to the project manager.

The Design "Core" Team

It is likely that the design team will grow as you develop the plan and define design issues. Therefore, it is recommended that you select a core team from this group and secure a management sponsor. This is the initial group that will define the action plan and represent major components of the migration. The core team should include people assigned to DNS administration, network infrastructure, Active Directory design, security, application deployment, desktop deployment, and technical support. The core team has the authority to delegate tasks to others and can reassign tasks to respond to staff outages in order to keep on schedule. They also can represent key areas in the migration, or critical tasks. In addition, they are ultimately responsible for the project and for making decisions.

Perhaps the person with the biggest impact on the migration, and whose support of the migration is critical, is the DNS administrator. The corporate DNS administrator or a qualified representative should be a member of the Windows 2000 design team. Appointing someone else to act as the Windows 2000 DNS administrator will not accomplish the goal because Windows 2000 DNS must integrate well with the corporate DNS structure. Spending time converting this person to your project will pay huge dividends in the future and may be the cause of success or failure of the project.

In Chapter 4, "Namespace Design of the Windows 2000 Active Directory," you learn that DNS is at the heart of Windows 2000. The difficulty likely will lie in convincing the DNS administrator to let the Windows 2000 environment run on Microsoft DNS servers, and spending the time to make sure that Windows 2000 fits in to the corporate DNS structure. How DNS is organized and delegated directly affects the Windows 2000 domain naming scheme as well.

Table 3.4 is a sample form to identify the members of the design team. Note the distinction of core team members. You might want to add other people in responsible positions, specific to your company, to the core team.

Table 3.4 Core Design Team Assignment List

Project Task

Core Team

Assigned to

Project leader

Core

 

Management sponsor

Core

 

Active Directory design

 

Namespace design: DNS

Core

 

Namespace design: domain

Core

 

Replication topology and site design

Core

 

Group Policy design and planning

Core

 

Physical network

Core

 

Security

Core

 

Migration

Core

 

Planning and strategy

 

 

Interoperability

 

 

Backup and recovery

 

 

Mail and messaging

Core*

 

Applications

Core

 

Tools

 

 

Desktop deployment

 

 

Project

 

 

Training

 

 

*Assumes use of Exchange 2000

The core team's initial responsibilities include the following:

  • Establish the DNS design.

  • Determine the domain namespace design.

  • Review the network infrastructure to ensure that it will support Windows 2000.

  • Design the Active Directory structure, including replication topology and site design, Group Policy implementation, Global Catalog server placement, and FSMO role planning.

  • Design the security model.

  • Ensure compliance with company standards.

  • Certify applications for Windows 2000 deployment. This should include an analysis of the use of SMS versus Group Policy software deployment, design of MSI packages, and so on.

In Table 3.4, a Mail and Messaging representative is listed as a core member. This is assuming the use of Exchange 2000 for a mail system. With Exchange 2000 tightly integrated with Active Directory in Windows 2000, it is important to have the messaging people involved in all phases of the Windows 2000 implementation. If Exchange is not the mail system, this would likely not be a core assignment.

 

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020