Читать книгу Project Management For Dummies - Stanley E. Portny - Страница 50

Three documents are generated at the completion of the development of the project charter:

 The project charter itself: A list of the information typically included in the project charter is included at the beginning of this section.

 An initial version of a stakeholder register: A register of people or groups that are needed to support, affected by, or interested in your project. A stakeholder can be classified as a driver (someone who has some say in defining the results your project is to produce), a supporter (a stakeholder who helps you perform the project), or an observer (someone who is interested in your project, but is neither a driver nor a supporter). (See Chapter 4 for more information on project stakeholders.)

 An assumptions list: A list of statements about project information that people consider to be true, even though they have not been proven to be. The assumptions you make about project information that’s important but about which you’re uncertain can dramatically affect every aspect of your project planning, tracking, and analysis. Equally as problematic is the information you believe to be true but is actually based on someone else’s assumption or on a faulty source. Therefore, it’s critical to begin to maintain a list of project information you know to be assumed in the early stages of the development of project materials and to continually add to and delete from it as necessary throughout the project.

When developing elements of the project plan, be sure to reflect the information developed in the early stages of the project’s development. As examples, the project charter should be considered when drafting a project’s scope statement (see Chapter 5), and the project stakeholder register and assumptions list should evolve from the corresponding documents begun when developing the project charter.