The following are some important Terms that we have learnt as part of the Project Initiation Phase.
• Assumption - A factor that you consider to be true without any proof or verification. Assumptions can appear in both the input and the output of various processes.
• Constraint - A restriction that can affect the performance of the project.
• Initiating process group - A process group that contains two processes: develop project charter and develop preliminary project scope statement.
• Project charter - A document that states the initial requirements to satisfy the stakeholders’ needs and expectations and also formally authorizes the project.
• Project Management Information System (PMIS) - An information system that consists of tools used to store, integrate, and retrieve the outputs of the project management processes. This can be used to support all stages of the project from initiating to closing.
• Project scope - The work that must be performed to deliver a product, service, or results with the specified features. The project scope draws the boundaries around the project: what is included and what is not.
• Stakeholder management strategy - The approach developed to deal with the stakeholders in the best interests of the project.
• Stakeholder register - A document that identifies the project stakeholders and the relevant information about them.
• Statement of work (SOW) - A document that describes the products or services to be delivered by the project. It is an input to developing the project charter and the preliminary project scope statement.
Previous: Summary - Project Initiation
Next: Project Planning
Showing posts with label sow. Show all posts
Showing posts with label sow. Show all posts
Wednesday, May 11, 2011
Saturday, May 7, 2011
Chapter 17: Introduction to Project Initiation
As you learned in the previous section on Introduction to Project Management, you manage projects through processes. You also learned that a process has an input, uses some tools and techniques, and produces output. You manage the initiation of a project through a process group called the initiating process group, which consists of two processes: Develop Project Charter and Identify Stakeholders. Before you can initiate a project, it must originate from somewhere.
In this section (a bunch of chapters) we will be looking at one big question:
So, lets get started!!!
Initiating a Project:
Initiating a project means defining the project, getting approval from people to start it, and identifying and analyzing the project stakeholders. During this stage the initial scope of the project is defined. Accordingly, initial resources are determined and allocated, a project manager with an appropriate authority level is assigned, and project stakeholders are identified.
Defining the project includes the following tasks:
Based on the project definition, you will identify the project stakeholders.
Look at the image below and you will understand the process of how inputs are provided to create the project charter.
Every organization has a business strategy and based on the business needs, someone in the top management writes down a statement of work and makes a business case. This business case and the statement of work are the starting points to develop the initial project scope and thereby determine what needs to be done in order to meet the business strategy. All these things go into the Project Charter which in turn is an input to the process of identifying the Stakeholders. Remember the chapter on Project Stakeholders?
In the next chapter, we will ponder more about the origin of projects and how they are initiated!!!
Previous: Important Terms - Introduction to Project Management
Next: Origin of Projects
In this section (a bunch of chapters) we will be looking at one big question:
How is a Project Initiated?
So, lets get started!!!
Initiating a Project:
Initiating a project means defining the project, getting approval from people to start it, and identifying and analyzing the project stakeholders. During this stage the initial scope of the project is defined. Accordingly, initial resources are determined and allocated, a project manager with an appropriate authority level is assigned, and project stakeholders are identified.
Defining the project includes the following tasks:
1. Developing project objectives and describing how they are related to the organization’s business objectives and strategy. (Remember the Project/Program/Portfolio Relationship chapter?)Note: The processes in the initiating process group, just like any other process group, can also be used to initiate a phase of a project that has multiple phases.
2. Specifying the project deliverables, such as products, services, or results, that will meet the objectives of starting this project.
3. Based on the objectives and deliverables, defining the initial scope of the project by explaining what will be done and drawing boundaries around what will be done and what will not be done.
4. Based on the initial scope, estimating the project duration and the resources needed. Only an Initial estimate would be made so that resources can be procured accordingly. An even accurate estimate would be made during the planning phase
5. Defining the success criteria. The project definition is incomplete without defining its success.
6. Assigning the initial project resources.
7. Assigning a project manager if one is not already assigned.
8. Authorizing the project. While different organizations may have a different process to approve the processes, the standard way to do it is to approve the document that holds the definition of the project, such as the project charter.
Based on the project definition, you will identify the project stakeholders.
Look at the image below and you will understand the process of how inputs are provided to create the project charter.
Every organization has a business strategy and based on the business needs, someone in the top management writes down a statement of work and makes a business case. This business case and the statement of work are the starting points to develop the initial project scope and thereby determine what needs to be done in order to meet the business strategy. All these things go into the Project Charter which in turn is an input to the process of identifying the Stakeholders. Remember the chapter on Project Stakeholders?
Trivia:
It’s a good policy to involve customers and other important stakeholders in the initiation stage of the project. It gives them the feeling of shared ownership that will greatly contribute to the success of the project by positively influencing factors such as deliverable acceptance and stakeholder satisfaction.
In the next chapter, we will ponder more about the origin of projects and how they are initiated!!!
Previous: Important Terms - Introduction to Project Management
Next: Origin of Projects
Subscribe to:
Posts (Atom)
© 2013 by www.getpmpcertified.blogspot.com. All rights reserved. No part of this blog or its contents may be reproduced or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of the Author.
Followers
Popular Posts
-
So far, we have been talking in terms of projects only. There are two other terms that are closed linked with projects and project manageme...
-
In the previous chapter , we took a look at Expected Monetary Value or EMV Analysis . The Decision Tree Analysis is another tool/technique ...
-
In the previous chapter, we saw how to create the Project Scope Document. The next step in planning for a projects scope is to create the Wo...
-
In the previous chapter, we saw the project lifecycle in detail. In this chapter, we are going to take a look at the Project Management Kno...
-
In the previous chapter we learnt how to create the project human resource plan. To get resources you need to spend money (Cost) and you can...
-
In the previous chapter , we learnt the basic details about Continuous Distributions. In this chapter, we are going to take a detailed look...
-
In the previous chapter we learnt that the risk register is going to be constantly updated as we progress through the various processes in...
-
Expected Monetary Value Analysis or EMV Analysis in short is the 2nd tool and technique in the Quantitative Risk Analysis and Modeling Tech...
-
In the previous chapter, we saw that an organizations policies and culture can have a significant impact on a project. Towards the end we al...
-
In the previous chapter, we took a look at how to sequence the activities based on the requirements and dependencies. The next step would be...
