Sunday, July 1, 2007

Elements of a Project Information Plan

In the IT project life cycle, outputs of one phase become the inputs to the next phase in the cycle. Since planning is the first phase conducted, where does the project team get its information to conduct the key planning activities?

The project team's information comes from the information plan. The information plan is an input to the planning phase and is obtained from the management team and the client.

The information plan provides a high-level description of the project's information systems and related business objectives. This plan is always the first document created for a project. Every information plan should contain a brief overview, as well as the following five sections.

1. Needs analysis
The needs analysis is a set of procedures undertaken to set priorities and make decisions about a product, based on the client's request. To conduct a needs analysis, the project manager (PM) interviews the client and reviews the project's schedule, resources, and budget to obtain information. During the information gathering process, the PM should follow the steps listed below.
  • Identify the business need. The PM restates the project request to make sure it is clear and asks why the client wants to invest in a product. Three of the most common needs are to generate revenue, reduce expenses, or comply with regulations. The PM then asks for a tangible goal that will result from satisfying the need.
  • Identify the gap. The gap is the difference between the client's current state and the desired state of technology that the project's product will help the client to achieve. The PM must ask the client what the current state of affairs is and what the client ultimately expects from the final product.
  • Identify the tasks involved. With the help of the client, the PM identifies what tasks the end users will perform when using the final product.
  • Identify the user groups. The PM asks the client who the intended users of the proposed product are. The PM also needs to obtain from the client a description of any user trait that might affect how the product is developed.
  • Identify any project constraints. Finally, the PM should identify any constraints. A constraint is anything that could potentially limit the success of the project.
If you have followed all of these steps to gather information, you should have the information you need to create the needs analysis section of the information plan for your client's project.

2. Project goals
The next section of the information plan, goals, contains two parts. First, it states the business objective and explains how the product will contribute to revenue, contain expenses, or comply with regulations. This information is obtained from the needs analysis section. The second part outlines product evaluation and explains how the customer can determine if the final product has achieved its goal.

3. Form of the product
The form of the product describes the medium you will use to deliver the product and the reason you chose that medium. You will have to choose the medium that best fits your product and that most efficiently distributes the information to the intended users. The available choices include mediums such as:
  • CD-ROM software packages
  • networks
  • network-installed applications
  • downloadable Web packages.
4. Product function
The next section, function of the product, briefly describes what the product will do for the company or the reason why the product was created.

5. Quality guidelines
The fifth section, quality guidelines, outlines the standards that the product must meet to be accepted by management and the client. A project usually has two types of guidelines.
  • Product guidelines affect production and the product's appearance. These guidelines cover such areas as programming languages and templates to be used, grammar standards, and a viewing platform for the final product.
  • Project guidelines affect time, money, and resources needed to complete the project, such as schedules or budgets.
Remember, the information plan is created during the project conception and is used as an input to the planning phase. It will provide the reasoning behind the design choices the project team will make. Without a complete information plan, the PM will not have the necessary information to achieve the project plan sign-off milestone that must be met to complete the planning phase and begin the analysis phase of the project.

1 comment:

Anonymous said...


Tag: PM206A56. Let me share all of you about #5 Tips for Project Management Success,, I hope you enjoy it

1. Plan your day using time management techniques

As a project manager, time management skills are essential because you are dealing with a wide range of tasks that demand a quick turnaround time. Planning your day will go a long way in keeping you organized and increasing your productivity. Assist your task planning by using project management software which helps you track the work of you and your team.

If you are not very tech savvy, a simple to-do list can also be a great organizational tool. Prioritize your most important tasks by putting them at the top of the list and less important ones at the bottom. Having a visual plan of your daily tasks helps to keep you on track and aware of time.

Related post: Free ebook 104 secrets to become a great project manager

2. Include stakeholders in important project conversations

While you will have plenty of responsibilities regarding the project, don’t neglect your clients.

Good communication is essential is keeping both parties informed of project progression, curtailing scope creep, and apprised of changing requirements. Some clients may have different expectations when it comes to communication, so make sure to establish the frequency and type of communication (like emails, phone calls, and face-to-face conversations) at the beginning of your project.

Establishing communication expectations early helps alleviate stakeholder uncertainty about communication frequency and delivery.

3. Regularly communicate with your team

Daily team communication helps keep misunderstandings and unclear requirements under control. Keeping your team informed in every step of the project is essential to project management success.

For example, a study published by Procedia Technology found that good communication skills were the cornerstone of project management. The study examined over 300 “construction project managers, architects, construction managers, engineers and quantity surveyors” and their successes and failures on various construction projects.

4. Anticipate project setbacks

Even the best-laid plans often go awry.

Remember that even with a high amount of planning and attention to detail, your project may still encounter some challenges. Pay attention to complaints from stakeholders or colleagues, and other warning signs, like a missed deadline or cost overrun, that there may be a problem.

Preventing a crisis will keep your project running smoothly, save you a lot of time, and keep you, your team, and your stakeholders confident in progressing with the project.

Unfortunately not every complication can be avoided. Crisis management skills are essential for dealing with the unexpected. Project managers need to be flexible and pragmatic. Improvise and make sharp decisions when needed.

Related post: 92 free project management templates

5. Stay focused on the details

A common problem project managers encounter is having the project aims not aligned with the organization’s objectives. A great project manager will strategize a plan for the project to lead back to the overall success of the business.

Know your project’s scope by heart and avoid wandering outside of the project’s requirements. It’s too easy to get lost in minor details and forget what your focus is, so a well-planned project scope is essential for success.

And final, you should use KPI to measure effectiveness of the project, here are full list: 76 project management KPIs