none
How to write a Phase-in Plan for an IT project RRS feed

  • Question

  • Our contracting company is planning to take over an existing IT project from an incumbent contracting company and I need to write a phase-in plan covering the following areas:

    Systems Analysis
    Technical Development (Operation & Maintenance)
    Technical Development (Development, Modernization and Enhancement)
    Database Administration
    Documentation
    Release Management

    Although, I have an experience in working in all of the above areas as a senior developer and as a technical lead, I have never gone through a phase-in plan. I would greatly appreciate some good pointers (templates etc.) and/or if someone can provide me links to online documentation on this subject.
    Sunday, July 18, 2010 5:12 AM

Answers

  • I am a newbie in Project Management arena. Recently became Member of PMI and also trying to learn Microsoft MOF. Here are some pointers and samples.

    Pointers:
      • http://www.datamigrationpro.com/data-migration-articles/2008/12/3/data-migration-project-checklist-a-template-for-more-effecti.html
      • http://technet.microsoft.com/en-us/library/bb497050.aspx

    Samples:
      • www.search.org/files/doc/Sample%20Project%20Plan.doc
      • http://www.mhhe.com/engcs/compsci/pressman/graphics/Pressman5sepa/common/cs1/projplan.pdf

    Hope these are helpful.

    Rubel Khan - MY BLOG!
    If your question was truly answered, please mark it as Answered and Vote as helpful. Thank you in advance.

     

    Tuesday, July 20, 2010 4:22 PM
  • Here are some pointer to help with the system analysis aspect:

    Sytem Analysis

    In this phase, the current system is studied in detail. A person responsible for the analysis of the system is known as analyst. In system analysis, the analyst conducts the following activities.

    Needs Analysis

    This activity is known as requirements analysis. In this step the analyst sums up the requirements of the system from the user and the managers. The developed system should satisfy these requirements during testing phase.

    Data Gathering

    In this step, the system analyst collects data about the system to be developed. He uses different tools and methods, depending on situation. These are:

    Written Documents

    The analyst may collect the information/data from written documents available from manual-files of an organization. This method of data gathering is normally used if you want to computerize the existing manual system or upgrade the existing computer based system. The written documents may be reports, forms, memos, business plans, policy statements, organizational charts and many others. The written documents provide valuable information about the existing system.

    Interviews

    Interview is another data gathering technique. The analyst (or project team members) interviews, managers, users/ clients, suppliers, and competitors to collect the information about the system. It must be noted that the questions to be asked from them should be precise, relevant and to the point. 

    Questionnaires

    Questionnaires are the feedback forms used to collect Information. The interview technique to collect information is time-consuming method, so Questionnaires

    are designed to collect information from as many people as we like. It is very convenient and inexpensive method to collect information but sometimes the response may be Confusing or unclear and insufficient.

    Observations 

    In addition to the above-mentioned three techniques to collect information, the analyst  (or his team) may collect Information through observation. In this collect technique, the working, behavior, and other related information of the existing system are observed. It means that working of existing system is watched carefully.

     Sampling

    If there are large numbers of people or events involved in The system, we can use sampling method to collect information. In this method, only a part of the people or events involved are used to collect information. For example to test the quality of a fruit, we test a piece of the fruit.

     Data Analysis

    After completion of “Data Gathering” step the collected data about the system is analyzed to ensure that the data is accurate and complete. For this purpose, various tools may be used. The most popular and commonly used tools for data analysis are:

    • DFDs (Data Flow Diagrams)
    • System Flowcharts
    • Connectivity Diagrams
    • Grid Charts
    • Decision Tables etc.

     

    Analysis Report

    After completing the work of analysis, the requirements collected for the system are documented in a presentable form. It means that the analysis report is prepared. It is done for review and approval of the project from the higher management. This report should have three parts.

    • First, it should explain how the current system works.

    • Second, it   should explain the problems in the existing system.

    • Finally, it should describe the requirements for the new system and make recommendations for future.


      Helga Schiffer

      PMP

    Wednesday, January 26, 2011 6:49 PM

All replies

  • I am a newbie in Project Management arena. Recently became Member of PMI and also trying to learn Microsoft MOF. Here are some pointers and samples.

    Pointers:
      • http://www.datamigrationpro.com/data-migration-articles/2008/12/3/data-migration-project-checklist-a-template-for-more-effecti.html
      • http://technet.microsoft.com/en-us/library/bb497050.aspx

    Samples:
      • www.search.org/files/doc/Sample%20Project%20Plan.doc
      • http://www.mhhe.com/engcs/compsci/pressman/graphics/Pressman5sepa/common/cs1/projplan.pdf

    Hope these are helpful.

    Rubel Khan - MY BLOG!
    If your question was truly answered, please mark it as Answered and Vote as helpful. Thank you in advance.

     

    Tuesday, July 20, 2010 4:22 PM
  • Hi NamWam,

     

    Take a look on this too:

     

    http://technet.microsoft.com/en-us/library/cc506051.aspx

    http://technet.microsoft.com/en-us/library/ee956951.aspx

     

    Hope this helps.

    Regards,

     

    Cleber Marques

    Microsoft MVP & MCT | Charter Member: SCVMM & MDOP
    MOF Brazil Project: Simplifying IT Service Management
    My Blog | MOF.com.br | CleberMarques.com | CanalSystemCenter.com.br
    Wednesday, July 21, 2010 3:06 AM
    Moderator
  • I’m changing the status for this post as answered, if you need any help about MOF please open a new thread. J

     

    Thank you,

     

    Cleber Marques

    Microsoft MVP & MCT | Charter Member: SCVMM & MDOP
    MOF Brazil Project: Simplifying IT Service Management
    My Blog | MOF.com.br | CleberMarques.com | CanalSystemCenter.com.br
    Wednesday, July 28, 2010 9:24 AM
    Moderator
  • Here are some pointer to help with the system analysis aspect:

    Sytem Analysis

    In this phase, the current system is studied in detail. A person responsible for the analysis of the system is known as analyst. In system analysis, the analyst conducts the following activities.

    Needs Analysis

    This activity is known as requirements analysis. In this step the analyst sums up the requirements of the system from the user and the managers. The developed system should satisfy these requirements during testing phase.

    Data Gathering

    In this step, the system analyst collects data about the system to be developed. He uses different tools and methods, depending on situation. These are:

    Written Documents

    The analyst may collect the information/data from written documents available from manual-files of an organization. This method of data gathering is normally used if you want to computerize the existing manual system or upgrade the existing computer based system. The written documents may be reports, forms, memos, business plans, policy statements, organizational charts and many others. The written documents provide valuable information about the existing system.

    Interviews

    Interview is another data gathering technique. The analyst (or project team members) interviews, managers, users/ clients, suppliers, and competitors to collect the information about the system. It must be noted that the questions to be asked from them should be precise, relevant and to the point. 

    Questionnaires

    Questionnaires are the feedback forms used to collect Information. The interview technique to collect information is time-consuming method, so Questionnaires

    are designed to collect information from as many people as we like. It is very convenient and inexpensive method to collect information but sometimes the response may be Confusing or unclear and insufficient.

    Observations 

    In addition to the above-mentioned three techniques to collect information, the analyst  (or his team) may collect Information through observation. In this collect technique, the working, behavior, and other related information of the existing system are observed. It means that working of existing system is watched carefully.

     Sampling

    If there are large numbers of people or events involved in The system, we can use sampling method to collect information. In this method, only a part of the people or events involved are used to collect information. For example to test the quality of a fruit, we test a piece of the fruit.

     Data Analysis

    After completion of “Data Gathering” step the collected data about the system is analyzed to ensure that the data is accurate and complete. For this purpose, various tools may be used. The most popular and commonly used tools for data analysis are:

    • DFDs (Data Flow Diagrams)
    • System Flowcharts
    • Connectivity Diagrams
    • Grid Charts
    • Decision Tables etc.

     

    Analysis Report

    After completing the work of analysis, the requirements collected for the system are documented in a presentable form. It means that the analysis report is prepared. It is done for review and approval of the project from the higher management. This report should have three parts.

    • First, it should explain how the current system works.

    • Second, it   should explain the problems in the existing system.

    • Finally, it should describe the requirements for the new system and make recommendations for future.


      Helga Schiffer

      PMP

    Wednesday, January 26, 2011 6:49 PM