Your SlideShare is downloading. ×
  • Like
Pmp training sigmora
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Pmp training sigmora

  • 525 views
Published

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
525
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
89
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”
  • Project Objective Statement: This should be a 25 word or less statement of the project objective, including scope, schedule and resources. Example: Implement a disaster recovery site for critical financial systems and processes by 6/1/04 for $500k. Note that at this point (New project) the details of schedule and cost/resources may not be known. Give an estimate from the Business case or use approximations, for example “Implement a disaster recovery site for critical financial systems and processes by summer 2004 for less than $1M”.
    Scope Statement: give a several sentence long statement of the scope of this project
    What is NOT Included: if there are specific things that are excluded from this project, point those out here. For example: “This project will provide functionality for EMEA only, rollout to the US and APAC will occur at a later time.”

Transcript

  • 1. PMP® Training By Balaji Gadicharla
  • 2. Agenda Day 1 Day 3 Instructor and Participants’ Introduction Quiz on Day 2 study Introduction to PMI and PMP Human Resources Management Project, Program and Portfolio Management Communication Management Process Areas Risk Management Integration Management Day 4 Scope Management Quiz on Day 3 study Day 2 Procurement Management Quiz on Day 1 study Stakeholder Management Time Management Quiz on Day 4 study Cost Management Day 5 Quality Management Business Templates Review of Exam Preparation
  • 3. Introductions • Balaji has around 20 years of industry experience • Implemented several projects both in India and the US • Real-life expertise in project management • Teaching project management for the past five years Page 3
  • 4. Project Management Institute (PMI) • PMI is the world’s largest not-for-profit membership association for the project management profession. Our professional resources and research empower more than 700,000 members, credential holders and volunteers in nearly every country in the world to enhance their careers, improve their organizations’ success and further mature the profession. • PMI credentials certify your knowledge and experience in project management so you can be more confident at work and more competitive in the job market. Note : The above information is taken from the official PMI website Page 4
  • 5. Project Management Professional (PMP) • PMI’s Project Management Professional (PMP)® credential is the most important industry-recognized certification for project managers. Globally recognized and demanded, the PMP® demonstrates that you have the experience, education and competency to lead and direct projects. Note : The above information is taken from the official PMI website Page 5
  • 6. PMP® Certification Overview • For complete details regarding the PMP eligibility requirements, please view the PMP Handbook on PMI website • PMBOK (Project Management Book of Knowledge) is the book that will be followed. Currently in fifth edition • This course will meet one of the key requirements of having 35 hours of project management education to apply for certification • PMP Certification exam consists of - 175 scored questions - 25 unscored qustions Total alloted time for these 200 questions is 4 hours Page 6
  • 7. PMP Examination Overview PMP Certification exam consists of - 175 scored questions - 25 unscored questions Total alloted time for these 200 questions is 4 hours Domain Percentage of Questions Initiation 13% Planning 24% Executive 30% Monitoring and Control 25% Closure 8% TOTAL Page 7 100%
  • 8. Maintaining PMP certification • As part of PMI’s Continuing Certification Requirements (CCR) program, a PMP credential holder will need to earn 60 Professional Development Units (PDUs) per three-year period • Each professional development activity yields one PDU for one hour spent engaged in the activity • Need to report the earned PDUs to PMI • Please refer PMI website for further details Page 8
  • 9. • OK, Lets get started!!! Page 9
  • 10. What is a Project? Page 10
  • 11. A project is a… • Temporary effort • Create a unique product, service or offering • Can be short term or long term • Definite begin and end • Can have repetitive elements but the result is unique Ongoing operations like shop floor production or billing and invoicing of existing customers cannot be considered a project Page 11
  • 12. Project, Program and Portfolio Management Portfolio Program Project Page 12
  • 13. Organizational Structure Type of Organization Type of Organization Functional Organization Functional Teams work on project independently Weak Matrix Organization PM is more a coordinator. No formal PM. Balanced Matrix Organization PM role is recognized but no full authority. Rolls up to a func manager Strong Matrix Organization PM reporting to Manager of PMs and not to a functional manager Projectized Organization PM has all staff working on the project reporting PMOs – Supportive, Controlling and Directive types Page 13 Project manager’s authority, role and resource availability
  • 14. Project Process Groups • Initiation • Planning • Execution • Monitoring and Control • Closure 1. How does stakeholder risk and influence change while the project progresses? 2. How does the uncertainty in the project change over the period? 3. How does the cost move along the time of the project? Project Life Cycles – Predictive, Incremental and iterative, adaptive Page 14
  • 15. Project Process Groups Monitoring and Control Planning Execution Cost, Staff, Work Initiation Time Page 15 Closure
  • 16. Knowledge Areas • Project Integration Management • Project Scope Management • Project Time Management • Project Cost Management • Project Quality Management • Project Human Resources Management • Project Communication Management • Project Risk Management • Project Procurement Management • Project Stakeholder Management Page 16
  • 17. Mapping of Knowledge Areas and Process Groups • Each process group has one or more processes each of the • Each process group has a set of activities from knowledge areas • The processes are also grouped across knowledge areas • Each activity in each of the knowledge area has • Each process is tied to one knowledge area and one process group • An input • Each process has • Tools and expertise to do that activity • An input • An output • Tools and expertise to do that process • An output Input to a process Note : Study the handout Page 17 Tools and expertise to do that process Output
  • 18. Document Flow Chart Page 18
  • 19. Project Integration Management Page 19
  • 20. Integration Management Processes • Develop Project Charter • Develop Project Management Plan • Direct and Manage project work • Monitor and control project work • Perform Integrated Change Control • Close Project or Phase Page 20
  • 21. Processes : Inputs -> Tools -> Output Process Group Initiation Process Develop Project Charter Inputs Project SOW Busines Case Agreements Enterprise Environmental factors Organizational process assets Project Charter Outputs from other processes Enterprise environmental factors Planning Develop Project Management Plan Organizational process assets Project Management Plan Approved Change Requests Enterprise environmental factors Execution Direct and Manage project work Organizational process assets Project Management Plan Schedule forecasts Cost forecasts Validated Changes Work performance information Enterprise environmental factors Monitoring & Ctl Monitor and control project work Organizational process assets Project Management Plan Work performance information Change Requests Enterprise environmental factors Monitoring & Ctl Perform Integrated Change Control Organizational process assets Project Management Plan Accepted deliverables Organizational process assets Closure Close Project or Phase Page 21 Tools Expert Judgement Expert Judgement Facilitation Techniques Output Project charter Expert Judgement Project Management Information System Meetings Project Management Plan Deliverables Work performance data Change Requests Project MAnagement plan updates Project document updates Expert judgement Analytical techniques Project Management information system Meetings Change Requests Work performance reports Project management plan updates Project document updates Expert Judgement Meetings Change Control Tools Expert Judgement Analytical techniques Meetings Approved Change Requests Change log Project management plan updates Project document updates Final product, service or result transition Organizational process assets updates
  • 22. Integrated Change Control • Integrated Change Control is the process of reviewing all change requests, approving changes and managing changes to the deliverables, organizational process assets, project documents and the project management plan. • Configuration Management System with integrated change control provides a standardized, effective and efficient way to centrally manage approved changes and baselines within a project. • Configuration control is focused on the specification of both the deliverables and the processes while change control is focused on identifying, documenting and controlling changes to the project and the product baselines. Change Requests – Corrective, Preventive, Defect Repair Page 22
  • 23. Sample Project Charter Project Objectives Project Timeline Milestone Due Date Project Team Project Business Drivers Steering Committee Members Core Team Members Key Success Factors Page 23
  • 24. Project Scope Management Page 24
  • 25. Scope Management Processes • Plan Scope Management • Collect Requirements • Define Scope • Create Work Breakdown Structure (WBS) • Validate Scope • Control Scope Page 25
  • 26. Processes : Inputs -> Tools -> Output Process Group Planning Process Plan Scope Management Inputs Project Management Plan Project charter Enterprise environmental factors Organzational Process assets Tools Collect Requirements Planning Define Scope Planning Scope management plan Project Scope Statement Requirements Documentation Enterprise environmental factors Create Work Breakdown Structure (WBS) Organizational Process Assetss Expert Judgement Meetings Interviews Focus groups Facilitated workshops Group creativity techniques Group decision-making techniques Questionnaires and surveys Observations Prototypes Benchmarking Context diagrams Document analysis Expert judgement Product analysis Alternatives generation Facilitated workshops Scope management plan Requirements management plan Decomposition Expert Judgement Scope Baseline Project Document Updates Inspection Group decision-making techniques Scope management plan Requirements management plan Stakeholder management plan Project charter Stakeholder register Scope management plan Project Charter Requirements documentation Organizational process assets Planning Accepted Deliverables Change Requests Work performance information Project Document Updates Variance Analysis Work Performance information Organizational Process Assets Updates Change Requests Project Management Plan Updates Project Document Updates Project management plan Requirements Documentation Requirements Traceability Matrix Validated Deliverables Work performance data Monitoring & Ctl Monitoring & Ctl Page 26 Validate Scope Control Scope Output Project Management Plan Work Performance data Requirements Documentation Requirements Traceability Matrix Organizational Process Assets Requirements documentation Requirements traceability matrix Project scope statement Project document updates
  • 27. Group Related Techniques • Group Creativity Techniques • Brainstorming • Nominal group technique : voting process to prioritize ideas for brainstorming or the ideas are vetted by a smaller group before being reviewed by larger • Delphi technique • Idea/mind mapping : ideas from brainstorming are placed on single map • Affinity diagram : large number of ideas sorted into groups for analysis • Group Decision Making Techniques • Unanimity : Everyone agrees on single course of action • Majority : more than 50% agree • Plurality : largest block in a group decides though they are not majority • Dictatorship Page 27
  • 28. Work Breakdown Structure (WBS) • WBS is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables, with each descending level of the WBS representing an increasingly detailed definition of the project work. • Work package is the lowest level WBS component where the planned work is contained. A work package can be scheduled, cost estimated, monitored and controlled. • Decomposition is the subdivision of project deliverables into smaller, more manageable components until the work and deliverables are defined to the work package level. • Scope Baseline : Project Scope Statement, WBS, WBS Dictionary Page 28
  • 29. Quiz from Day 1 Page 29
  • 30. Project Time Management Page 30
  • 31. Time Management Processes • Plan Schedule Management • Define Activities • Sequence Activities • Estimate Activity Resources • Estimate Activity Durations • Develop Schedule • Control Schedule Page 31
  • 32. Processes : Inputs -> Tools -> Output Process Group Planning Process Plan Schedule Management Planning Define Activities Planning Sequence Activities Planning Planning Planning Monitoring & Ctl Page 32 Estimate Activity Resources Estimate Activity Durations Develop Schedule Control Schedule Inputs Project management plan Project Charter Enterprise environmental factors Organizational process updates Schedule Management Plan Scope Baseline Enterprise Environmental Factors Organizational Process Assets Schedule Management Plan Activity List Activity Attributes Milestone List Project Scope Statement Organizational Process Assets Schedule Management Plan Activity List Activity Attributes Resource Calendars Risk register Activity Cost Estimates Enterprise Environmental Factors Organizational Process Assets Schedule management plan Activity List Activity Attributes Activity Resource Requirements Resource Calendars Project Scope Statement Risk Register Resource breakdown structure Enterprise Environmental Factors Organizational Process Assets Schedule Management plan Activity List Activity Attributes Project Schedule Network Diagrams Activity Resource Requirements Resource Calendars Activity Duration Estimates Project Scope Statement Risk register Project staff assignments Resource breakdown structure Enterprise Environmental Factors Organizational Process Assets Project Management Plan Project Schedule Schedule data Project calendars Work Performance data Organizational Process Assets Tools Output Expert Judgement Analytical techniques Meetings Schedule Management Plan Decomposition Rolling Wave Planning Expert Judgment Activity List Activity Attributes Milestone List Precedence Diagramming Method (PDM) Dependency Determination Applying Leads and Lags Project Schedule Network Diagrams Project Document Updates Expert Judgment Alternatives Analysis Published Estimating Data Bottom-up Estimating Project Management Software Activity Resource Requirements Resource Breakdown Structure Project Document Updates Expert Judgment Analogous Estimating Parametric Estimating Three-point Estimates Group decision making techniques Reserve Analysis Activity Duration Estimates Project Document Updates Schedule Network Analysis Critical Path Method Critical Chain Method Resource Optimization techniques Modeling techniques Leads and Lags Schedule Compression Scheduling Tool Performance Reviews Project Management Software Resource optimization techniques Modeling techniques Leads and Lags Schedule Compression Scheduling Tool Project Schedule Schedule Baseline Schedule Data Project calendars Project management plan updates Project Document Updates Work Performance information Schedule forecasts Change Requests Project Management Plan Updates Project Document Updates Organizational Process Assets Updates
  • 33. Activities • Project Work packages are decomposed into smaller components called activities that represent the work necessary to complete the work package. • Work package represents deliverable, where activity represents actual work • Rolling Wave Planning is a form of progressive elaboration planning where the work to be accomplished in the near term is planned in detail and future work is planned at a higher level of the WBS. Page 33
  • 34. Sequence Activities • Precedence Diagramming Method (PDM): Used in CPM to construct project schedule network diagram using rectangles (called nodes) to represent activities and using arrows to show logical relationships. Also called as Activity-on-Node Four types of relationships: F2F, F2S, S2F, S2S • Dependency determination • Mandatory dependencies (hard logic) • Discretionary dependencies (preferred or soft logic) • External dependencies • • Page 34 Applying leads and lags : Leads allow acceleration of the successor activity. Lags delay the successor activity Schedule Network Templates : Used to expedite the preparation of networks of project activities. Portions of it are called subnetwork or fragmented network. Used when a project includes identical deliverables (multiple floors of a high-rise buildings)
  • 35. Estimate Activity Resources (Man, machines etc) • • Published Estimating Data :Using published updated production rates and unit costs of resources • Page 35 Alternatives Analysis : Look at alternative methods of accomplishment including various levels of resource capability or skills, different size or type of machines etc. Bottom-Up Estimating : Used when an activity cannot be estimated with a reasonable degree of confidence. The activity is decomposed and then the estimates are aggregated into a total quantity for each of the activity’s resources.
  • 36. Estimate Activity Durations • Analogous Estimating : Uses parameters such as duration, budget, size, weight and complexity from a previous project as the basis for estimating the same parameter for a future project. Less accurate and less expensive. • Parametric Estimating : Uses a statistical relationship between historical data and other variables to calculate an estimate for activity parameters. • Three point Estimates : Uses three estimates considering uncertainty and risk : Most likely – tm, optimistic – to and pessimistic - tp • Beta distribution : Based on PERT and Expected duration Te= (to + 4 tm + tp )/6 • • Page 36 Triangular distribution : Expected duration Te= (to + tm + tp )/3 Reserve Analysis: Includes contingency reserves (also called time reserves or buffers) into overall project schedule to account for uncertainty. Management reserve is not included in scheduled baseline but part of overall project duration
  • 37. Develop Schedule : Tools • Schedule Network Analysis : Employs various analytical techniques, such as CPM, critical chain method, what-if analysis and resource leveling to calculate the early and late start and finish dates for the uncompleted portions of activities. • Critical Path Method (CPM) : Calculates early start and finish dates and late start and finish dates by performing a forward and backward pass analysis through the schedule network. They indicate the time periods within which the activity could be scheduled. • Schedule flexibility is measured by the positive difference between early and late dates and called “total float” • Critical paths have zero or negative total float – that means no flexibility. Activities on this path are critical activities. • Free float is the amount of time an activity can be delayed without delaying the early start date of the successor. • FLOAT=delay Page 37
  • 38. Develop Schedule : Tools • Critical Chain Method : This is a schedule network analysis technique that modifies the project schedule to account for limited resources. This method adds duration buffers that are non-work schedule activities to manage uncertainty. • Feeding buffers are placed at each point that a chain of dependent tasks not on the critical chain feeds into the critical chain • Size of each buffer = uncertainty in the duration of the cahin of dependent tasks leading to that buffer • Buffer placed at the end of critical chain is called Project buffer • Resource Optimization techniques • Resource Leveling : used when shared or critical resources are available only at certain times. Necessary when resources are over-allocated. Alters completion date and critical path • Resource Smoothing : adjusts the schedule so that resources do not exceed predefined limits. Does not alter critical path and hence completion date Page 38
  • 39. Develop Schedule : Tools • What-If Scenarios : Simulating different scenarios calculating multiple project durations with different sets of activity assumptions. Eg Monte Carlo Analysis : distribution of possible activity durations is defined for each activity and used to calculate a distribution of possible outcomes of the project. • Schedule Compression : Shortens the project schedule without changing the project scope. • Crashing : A schedule compression technique in which cost and schedule tradeoffs are analyzed to determine how to obtain compression for the least incremental cost. Ex., approving overtime, bringing in additional resources etc. Crashing works where additional resources will shorten the duration • Fast tracking : This is a technique where activities are performed in parallel which would otherwise be in sequence. • Both these techniques can increase risk, rework and/or cost. Page 39
  • 40. Control Schedule : Tools • Performance Reviews : Measure, compare and analyze schedule performance like start and finish dates, % complete etc. • Utilize Schedule Variance (SV) and Schedule Performance Index (SPI) if using Earned Value Management (EVM) • Decide if schedule variation requires corrective action Page 40
  • 41. Project Cost Management Page 41
  • 42. Cost Management Processes • Plan Cost Management • Estimate Costs • Determine Budget • Control Costs Page 42
  • 43. Processes : Inputs -> Tools -> Output Process Group Planning Planning Planning Process Plan Cost Management Estimate Costs Determine Budget Monitoring & Ctl Control Costs Page 43 Inputs Project Management Plan Project Charter Enterprise environmental factors Organizational Process Assets Tools Expert Judgement Analytical techniques Meetings Cost management plan Expert Judgment Human Resource management Analogous Estimating Plan Parametric Estimating Scope Baseline Bottom-up Estimating Project Schedule Three-point Estimates Risk Register Reserve Analysis Enterprise Environmental Cost of Quality Factors Project Management Software Organizational Process Assets Vendor Bid Analysis Group decision-making techniques Cost management plan Scope Baseline Activity Cost Estimates Basis of Estimates Cost Aggregation Project Schedule Reserve Analysis Resource Calendars Expert Judgment Risk register Historical Relationships Agreements Organizational Process Assets Funding Limit Reconciliation Earned Value Management Forecasting To-Complete Performance Index Project Management Plan (TCPI) Project Funding Requirements Performance Reviews Work Performance data Reserve Analysis Organizational Process Assets Project Management Software Output Cost management plan Activity Cost Estimates Basis of Estimates Project Document Updates Cost Performance Baseline Project Funding Requirements Project Document Updates Work Performance information Cost Forecasts Organizational Process Assets Updates Change Requests Project Management Plan Updates Project Document Updates
  • 44. Determine Budget : Tools • Reserve Analysis • Contingency reserves are allowances for unplanned but potentially required changes due to realized risks • Management reserves are budgets reserved for unplanned changes to project scope and cost. These are not part of cost baseline but may be included in the total budget for the project. They are not part of EVM calculations Page 44
  • 45. Determine Budgets : Outputs • Cost Performance Baseline: This is an authorized time-phased budget at completion (BAC) used to measure, monitor and control overall cost performance of the project. Represented by an S-curve. In EVM, the cost performance baseline is referred to as Performance Measurement Baseline (PMB) Project Budget Cumulative Values Management reserve BAC Cost Baseline Funding requirements Expenditures Time Page 45
  • 46. Control Costs: Tools • Earned Value Management : integrates project scope, cost and schedule measures to help the project management team assess and measure project performance and progress. Forms an integrated baseline against which performance can be measured • Planned Value (PV) : total PV is called performance measurement baseline (PMB) or Budget at Completion (BAC). This is the authorized budget for the work • Earned Value (EV) : value of work performed • Actual Cost (AC) : cost of work performed • Schedule Variance (SV) : EV - PV • Cost Variance (CV) : EV - AC • Schedule Performance Index (SPI) : EV/PV (if >1, more work completed than planned and vice versa) • Cost Performance Index (CPI) : EV/AC (if >1, cost underrun of performance to date and vice versa) Page 46
  • 47. Earned Value, Planned Value and Actual Cost ETC Cumulative Values Management reserve Planned Value (PV) Actual Costs (AC) Budget At Completion (BAC) Earned Value (EV) Time Page 47
  • 48. Control Costs: Tools • Forecasting : Develop a forecast for Estimate at Completion (EAC) that may differ from Budget at Completion (BAC). Typically based on actual costs. EAC = Estimate at Completion which takes into account Estimate to Complete (ETC) the remaining work EAC = AC + bottom-up Estimate to Complete (ETC) EAC = AC + BAC – EV EAC = BAC/cumulative CPI = BAC/ (EV/AC) EAC = AC + [(BAC – EV) / cumulative CPI x cumulative SPI)] • To-Complete Performance Index (TCPI) : calculated projection of cost performance that must be achieved on the remaining work to meet BAC or EAC • • Page 48 TCPI = Work remaining / Funds Remaining TCPI = (BAC – EV) / (BAC – AC) = (BAC – EV) / (EAC – AC)
  • 49. Project Quality Management Page 49
  • 50. Quality Management Processes • Plan Quality Management • Perform Quality Assurance • Control Quality Page 50
  • 51. Processes : Inputs -> Tools -> Output Process Group Planning Process Plan Quality Management Execution Perform Quality Assurance Monitoring & Ctl Control Quality Page 51 Inputs Tools Cost-Benefit Analysis Project management plan Cost of Quality Stakeholder Register Seven basic quality tools Risk Register Benchmarking Requirements documentation Design of Experiments Enterprise Environmental Statistical Sampling Factors Additional quality planning tools Organizational Process Assets Meetings Quality Management Plan Process Improvement Plan Quality management and Control Quality Metrics Tools Project documents Quality Audits Quality Control Process Analysis Measurements Project Management Plan Quality Metrics Quality Checklists Work Performance Data Approved Change Requests Seven basic quality tools Statistical Sampling Deliverables Inspection Project documents Organizational Process Assets Approved Change Requests Review Output Quality Management Plan Quality Metrics Quality Checklists Process Improvement Plan Project Document Updates Organizational Process Assets Updates Change Requests Project Management Plan Updates Project Document Updates Quality Control Measurements Validated Changes Validated Deliverables Work performance information Change Requests Project Management Plan Updates Project Documents Updates Organizational Process Assets Updates
  • 52. Costs of Quality • Cost of Conformance • Prevention Costs - Training, document processes, equipment, time to do right • Appraisal Costs - Testing, destructive testing loss, inspections • Cost of Nonconformance • Internal - Rework, scrap • External - Liabilities, warranty work, lost business Page 52
  • 53. Perform Quality Control : Tools Seven Basic Quality Tools •Cause and Effect diagrams : also called Ishikawa or fishbone diagrams •Flow Charts •Check sheets •Pareto Diagrams : based on 80/20 principle, where 80% of problems happen due to 20% of the causes •Histogram •Control Charts •Scatter Diagram Page 53
  • 54. Perform Quality Assurance : Tools PDPC : Process Decision Program Chart Page 54
  • 55. Quiz from Day 2 Page 55
  • 56. Project Human Resources Management Page 56
  • 57. Human Resources Management Processes • Plan Human Resource Management • Acquire Project Team • Develop Project Team • Manage Project Team Page 57
  • 58. Processes : Inputs -> Tools -> Output Process Group Planning Execution Execution Execution Page 58 Process Plan Human Resource Management Acquire Project Team Develop Project Team Manage Project Team Inputs Project Management Plan Activity Resource Requirements Enterprise Environmental Factors Organizational Process Assets Human Resource management Plan Enterprise Environmental Factors Organizational Process Assets Tools Output Organization Charts and Position Descriptions Networking Organizational Theory Expert judgement Human Resource management Meetings plan Pre-Assignment Negotiation Acquisition Virtual Teams Multi-criteria decision analysis Interpersonal Skills Training Team-Building Activities Project Staff Assignments Ground Rules Human Resource Co-Location management Plan Recognition and Awards Resource Calendars Personnel assessment tools Human Resource Management Plan Project Staff Assignments Team Performance Assessments Issues Log Observation and Conversation Work Performance Project Performance Appraisals Reports Conflict Management Organizational Process Interpersonal Skills Assets Project Staff Assignments Resource Calendars Project Management Plan Updates Team Performance Assessments Enterprise Environmental Factors Updates Enterprise Environmental Factors Updates Organizational Process Assets Updates Change Requests Project documents updates Project Management Plan Updates
  • 59. Develop Human Resource Plan : Tools • Org Charts • Hierarchical : like WBS, there is Organizational Breakdown Structure (OBS) • Text Oriented formats • Matrix-Based Charts : A responsibility assignment matrix (RAM) is used to illustrate the connections between work packages or activities and project team members. Example of RAM is RACI (next slide) Page 59
  • 60. RACI Sponsor Business Head Business Manager Project Manager IT Head IT Analyst Developer Tester Project charter A C C R C I I I Budget A C I R I I I I Requirements Gathering I C C C C R C C Solution Design and Architecture I C C C C R C C Build I I I I C C R C Test I I I I I C C R Go-Live I A C C C R R C TASKS R=Responsible, A=Accountable, C=Consulted, I=Informed Page 60
  • 61. Develop Project Team: Tools : Team building activities Different stages of team building •Forming : Team members meet and understand about the project and their roles and responsibilities •Storming : Team begins to address project work, PM approach and technical decisions •Norming : Members begin to work together and adjust their work habits to support the team. The team learns to trust each other •Performing : The team works as a well-organized unit •Adjourning : The team completes the work and moves on from the project Page 61
  • 62. Develop Project Team: Tools : Colocation • • Involves keeping all key team members in one physical location • Page 62 Also called Tight matrix Good strategy but virtual teams can still bring more skilled resources, reduced costs, less travel and relocation expenses
  • 63. Manage Project Team: Tools : Conflict Management • Withdraw/Avoid • Smooth/Accommodate : emphasizing areas of agreement rather than areas of difference • Compromise/Reconcile • Force/Direct • Collaborate/Problem Solve Effective inter-personal skills that a PM should have : • • Influencing • Page 63 Leadership Effective Decision-making
  • 64. Project Communications Management Page 64
  • 65. Communications Management Processes • Plan Communications Management • Manage Communications • Control Communications Page 65
  • 66. Processes : Inputs -> Tools -> Output Process Group Planning Execution Process Plan Communications Management Manage Communications Monitoring & Ctl Control Communications Page 66 Inputs Stakeholder Register Project Management Plan Enterprise Environmental Factors Organizational Process Assets Communications Management Plan Work Performance Reports Organizational Process Assets Enterprise Environmental Factors Project Management Plan Project communications Work Performance data Issue Log Organizational Process Assets Tools Communication Requirements Analysis Communication Technology Communication Models Communication Methods Meetings Communication Technology Communication Models Communication Methods Information management systems Performance reporting Information management systems Expert judgement Meetings Output Communications Management Plan Project Document Updates Project communications Project documents updates Project Management Plan updates Organizational Process Assets Updates Work Performance Information Organizational Process Assets Updates Change Requests Project Management Plan Updates Project Documents updates
  • 67. Sample Communication Plan • Weekly Status Report sent out by Project Manager by Friday EOB • Weekly Status Meetings every Tuesday at a specified time • Steering Committee meetings once a month • Adhoc meetings to address items that came out during weekly status meetings • Minutes of all meetings where action items have been identified and decisions made Page 67
  • 68. Sample Status Report Project Timeline Project Deliverables Milestone Project Accomplishments Last Week Page 68 Due Date Project Activities Next Week Status
  • 69. Sample Project Plan Sl. No Page 69 Activity Owner Planned Start Date Planned End Date Actual Start Date Actual End Date % Complete Comments
  • 70. Project Risk Management Page 70
  • 71. Risk Management Processes • Plan Risk Management • Identify Risks • Perform Qualitative Risk Analysis • Perform Quantitative Risk Analysis • Plan Risk Responses • Control Risks Page 71
  • 72. Processes : Inputs -> Tools -> Output Process Group Process Planning Plan Risk Management Planning Identify Risks Planning Planning Planning Inputs Tools Project Management Plan Expert Judgement Project Charter Analytical techniques Stakeholder register Enterprise Environmental Factors Meetings Organizational Process Assets Risk Management Plan Cost Management Plan Schedule Management Plan Quality Management Plan Human Resource management plan Scope baseline Documentation Reviews Activity Cost Estimates Information Gathering Techniques Activity Duration Estimates Checklist Analysis Stakeholder Register Assumptions Analysis Project Documents Diagramming Techniques Procurement documents Enterprise Environmental Factors SWOT Analysis Expert Judgment Organizational Process Assets Perform Quantitative Risk Analysis Risk Management Plan Scope baseline Risk Register Enterprise Environmental Factors Organizational Process Assets Risk Management Plan Cost Management Plan Schedule Management Plan Risk Register Enterprise Environmental Factors Organizational Process Assets Plan Risk Responses Risk Register Risk Management Plan Perform Qualitative Risk Analysis Project Management Plan Risk Register Work Performance Data Work Performance Reports Monitoring & Ctl Page 72 Control Risks Risk Probability and Impact Assessment Probability and Impact Matrix Risk Data Quality Assessment Risk Categorization Risk Urgency Assessment Expert Judgment Data Gathering and Representation Techniques Quantitative Risk Analysis and Modeling Techniques Expert Judgment Strategies for Negative Risks or Threats Strategies for Positive Risk or Opportunities Contingent Response Strategies Expert Judgment Risk Reassessment Risk Audits Variance and Trend Analysis Technical Performance Measurement Reserve Analysis Meetings Output Risk Management Plan Risk Register Project Document Updates Project Document Updates Project Management Plan Updates Project Document Updates Work performance information Organizational Process Assets Updates Change Requests Project Management Plan Updates Project Document Updates
  • 73. Quiz from Day 3 Page 73
  • 74. Project Procurement Management Page 74
  • 75. Procurement Management Processes • Plan Procurements • Conduct Procurements • Control Procurements • Close Procurements Page 75
  • 76. Processes : Inputs -> Tools -> Output Process Group Planning Execution Monitoring & Ctl Closure Page 76 Process Conduct Procurements Inputs Project Management Plan Requirements Documentation Risk Register Activity Resource Requirements Project Schedule Activity Cost Estimates Stakeholder register Enterprise Environmental Factors Organizational Process Assets Procurement Management Plan Procurement Documents Source Selection Criteria Seller Proposals Project documents Make-or-Buy Decisions Procurement statement of work Organizational Process Assets Control Procurements Project Management Plan Procurement Documents Agreements Approved Change Requests Work Performance Reports Work Performance Data Bidder Conferences Proposal Evaluation Techniques Independent Estimates Expert Judgment Advertising Analytical techniques Procurement Negotiations Contract Change Control System Procurement Performance Reviews Inspections and Audits Performance Reporting Payment Systems Claims Administration Records Management System Close Procurements Project Management Plan Procurement Documents Procurement audits Procurement negotiations Records Management System Plan Procurements Tools Make-or-Buy Analysis Expert Judgment Market research Meetings Output Procurement Management Plan Procurement Statements of Work Procurement Documents Source Selection Criteria Make-or-Buy Decisions Change Requests Project documents updates Selected sellers Agreements Resource Calendars Change Requests Project Management Plan Updates Project Documents Updates Work Performance Information Change Requests Project Management Plan Updates Project documents updates Organizational Process Assets Updates Closed Procurements Organizational Process Assets Updates
  • 77. Project Stakeholder Management Page 77
  • 78. Stakeholder Management Processes • Identify stakeholders • Plan stakeholder management • Manage stakeholder engagement • Control stakeholder engagement Page 78
  • 79. Processes : Inputs -> Tools -> Output Process Group Initiation Planning Execution Process Identify stakeholders Project Management Plan Stakeholder register Enterprise environmental factors Organizational process Plan stakeholder management assets Stakeholder management plan Communications management plan Change log Manage stakeholder Organizational process engagement assets Monitoring & Control stakeholder Ctl engagement Page 79 Inputs Tools Project Charter Procurement Documents Enterprise Environmental Stakeholder Analysis Factors Expert Judgment Organizational Process Meetings Assets Output Stakeholder Register Expert judgement Meetings Analytical techniques Stakeholder management plan Project documents updates Communication methods Interpersonal skills Management skills Issue log Change requests Project management plan updates Project documents updates Organizational process assets updates Information management Project management plan systems Issue log Expert judgement Work performance data Meetings Project documents Work performance information Change requests Project management plan updates Project documents updates Organizational process assets updates
  • 80. Quiz from Day 4 Page 80
  • 81. Q&A Thanks for your attention! Sigmora Technologies www.sigmora.com balaji.gadicharla@sigmora.com Page 81