# MSP_TEXT_FIELDS

TEXT_VALUE:
Some examples of questions that should be asked when defining user requirements are: ...


TEXT_VALUE:
Take the user requirements and put them in terms of functions for the developers.  Examples:...


TEXT_VALUE:
Figure out conceptually what you want the look and feel of the site to be.  If the site is large you will want to absolutely determine the design and layout of the site.  If you don't decide, and have builders work on HTML and navigation, you will spen...


TEXT_VALUE:
Determining conceptually what your "hot spots" will be and what they will link to.  Microsoft Front Page helps you do this very easily.


TEXT_VALUE:
After you have defined the specific functionality in the Concept phase, you must decide how to implement it.  This decision entails whether you will have in-house developers do the work, hire vendor development services, or will you buy a product off-t...


TEXT_VALUE:
Determine how much data you will have so that you know how much space it will take up on the server.


TEXT_VALUE:
How many people will visit your site and how often will they visit it?  This will help you figure out what server (hardware and software configuration) you should use.


TEXT_VALUE:
This task involves deciding who has access to what information on the intranet.  IIS (Internet Information Server) on the NT server helps you do this very easily.


TEXT_VALUE:
Since you do not want to make content changes to your intranet while users are working on it, you need to define how changes to content will be made and how those changes will be propagated to the live site.


TEXT_VALUE:
Communicate all server requirements with personnel responsible for server operations so that they can prepare and set up the production server....


TEXT_VALUE:
Ideally, a lab should be set up to simulate the production network (bandwidth and traffic).  Since this is not always feasible, your best guess on impact to the network is important so that different potential solutions to problems can be identified.


TEXT_VALUE:
If your system's speed, reliability, or response time will be compromised because of network issues, you must determine what steps need to be taken to address those issues....


TEXT_VALUE:
Keep your support personnel abreast of any issues you think relevant (network, server, or content related), so that they can prepare to staff accordingly.  This is important because you want your support staff and intranet site to go live simultaneously.


TEXT_VALUE:
Test the links/connections of all pages of the site.


TEXT_VALUE:
For this stage of testing, you have the users use the site and test to see if it meets the requirements that we had defined in the concept phase.


TEXT_VALUE:
Simulate the load on the system to test the performance of the site according to the predetermined requirements.


TEXT_VALUE:
Move the site to the server that users will use when the site goes live if it is not already there.  Do this step before stress testing if you do not have a way to simulate the production server.


TEXT_VALUE:
To generate internal interest for the new web site it is useful to conduct internal PR announcing the new web site location and live date.


TEXT_VALUE:
The roll out day is the day the site formally goes live and is available for all users to access....


TEXT_VALUE:
Determine what and how many support resources are needed to effectively support the users that will be using the intranet site.


TEXT_VALUE:
If you determined that more support resources are needed than you have available, make the appropriate staffing changes.


TEXT_VALUE:
Decide whether you will use a Help Desk, a hotline, email, etc.


TEXT_VALUE:
Decide how support will be administered:  maximum time until help is delivered, if and how calls will be logged, etc.


TEXT_VALUE:
This should occur simultaneously with the rollout of the site.


TEXT_VALUE:
This is the stage in which you create the HTML source code.  If you do not have developers assigned to this task, Microsoft FrontPage, Internet Assistant for Word, and other HTML editors can perform this function quickly and easily.


TEXT_VALUE:
If development is being done in-house, it is useful to have certain standards followed for HTML coding.  This makes the code easier to maintain in the long run.  Creating a template for your developers will help this effort.


TEXT_VALUE:
After you have designed the functionality, you must develop it or buy it, depending on the cost-benefit analysis performed in the design phase.


TEXT_VALUE:
If custom development is the way you want to proceed with getting the functionality you need, determine who will be responsible and plug them into this task.


TEXT_VALUE:
Will you use an off-the-shelf HTML editor?  Or create your pages free-form?  Or will you customize a data-conversion tool if you are converting an existing system?  All options need to be considered.


TEXT_VALUE:
Define your overall test plan - including when, how, and roles and responsibilities of the parties involved.


TEXT_VALUE:
The size of this task depends on the amount of content your web site will contain.  The more detailed design work done up front, the quicker this task will be accomplished.


TEXT_VALUE:
Once the functionality you need for your web site is complete, either by your own development or by purchasing some 3rd party software, integrate it into the other pages to complete the site.


TEXT_VALUE:
Decide what information users require and how they prefer to access that information.  Determine exactly what content will move to the intranet and for which user types.


TEXT_VALUE:
Bring all of the necessary information together in a plan.  The plan should:...


TEXT_VALUE:
The project plan will be used as a tool to communicate with the development team whether they are an internal development team or an external vendor.  As a result of the briefing you should have committed development resources for the project and buy i...


TEXT_VALUE:
Evaluate how your company's current system of communication works (e-mail, public folders, network servers) and determine how you will migrate/integrate that system into an intranet site.


TEXT_VALUE:
Define what specific content will be converted to HTML to be viewed directly on the site and which content will remain in its native file form and linked to from the intranet.  Determine the source and location of each type of content.


TEXT_VALUE:
Create a content site map detailing where each content type resides today and where it will reside on the new web server.  Prioritize the content migration, i.e. determine in what order the content will be moved to the web and, if appropriate, what con...


TEXT_VALUE:
Convert necessary content to HTML either manually or by utilizing a set of conversion utilities.  The choice is dependent upon the quantity of content that requires conversion.  Your development team can advise you on the type and availability of conve...


TEXT_VALUE:
Once the content has been converted either manually or with the aid of conversion utilities, an editor should double check the quality of conversion to make sure that standard formats are in place.


TEXT_VALUE:
Define how you want the content to appear on each page....


TEXT_VALUE:
Some examples of questions that should be asked when defining system requirements are:...


TEXT_VALUE:
Your organization may have strict rules about how information is stored on their machines.  Some of the questions that should be asked when defining server owner requirements are:...


TEXT_VALUE:
Determine the order in which groups or users within a group will go live on the system. A staggered roll out will allow trainers and support staff to spend more time with individual users.


TEXT_VALUE:
All users at all locations should receive a detailed plan for the roll out informing them when the roll out will occur and when and where training is available.


TEXT_VALUE:
Even in very small groups, users should go through a formal training course on the new system.  Formal training will reduce support calls and user frustration.


TEXT_VALUE:
It is important to analyze your concept, the environment you are working in, and the potential problems that could arise.  These areas of risk should be documented and a plan formulated to mitigate the risk where possible, and to manage the risk where ...


TEXT_VALUE:
1) This plan is not resource loaded.  For example, Tasks 3, 4, and 5 all have predecessor 2.  They can be done simultaneously if the resources are there to do it; if not they will have finish-to-start dependencies and will stagger accordingly....


# MSP_TASKS

TASK_NAME:
Determine estimated disk space utilization


TASK_NAME:
Determine what support resources are needed


TASK_NAME:
Determine method that users will attain support


TASK_NAME:
Determine what content will be moved/converted


TASK_NAME:
Implement content migration and conversion


TASK_NAME:
Define risks and risk management approach


# MSP_CONVERSIONS

CONV_STRING:
Dependencies External Predecessor Task Name


CONV_STRING:
Dependencies External Successor Task Name


CONV_STRING:
Only allow outline codes listed in the lookup table


CONV_STRING:
Only allow new outline codes with values at all levels of mask


