Published on

  • Be the first to comment

  • Be the first to like this


  1. 1. Activity Sequencing InputsThe inputs to the Activity Sequencing process are spread across two knowledge areas. The ScopeDefinition Process within the Project Scope Management Knowledge Area produces the Project ScopeStatement input. In addition the organization which employs the project team may also provideOrganizational Process Assets relevant to the Activity Sequencing process. And finally the ActivityDefinition Process within the Time Management Knowledge Area produces three of the five inputs toour Activity Sequencing process area; Activity List, Activity Attributes and Milestone List are all outputsto the Activity Definition process area. Fig 1.3 Activity List Activity Attributes Milestone List Project Scope Statement Organizational Process Assets 1
  2. 2. Activity ListThe activity list is a comprehensive list of all activities required on the project. The activity list containsthe work descriptions for project team members. The description needs to be clear enough thateveryone understands what work is required. In general Activity List will consist of: Fig 1.4 Activity List Comprehensive list of Detailed Scope Activity Identifier scheduled activities Description 2
  3. 3. Example Initial Activity ListThe Activity Sequencing process evolves; meaning initially activity list contain minimal detail howeveras information is obtained more pertinent detail is documented in Attribute List and Milestone List. Theactivity sequencing process organizes data about project activity that will aid planning to carryout thework related to delivering the project. Examples of relevant detail and considerations may include whatneeds to happen before an activity can be completed (predecessor activities), what will happen after theactivity is completed (successor activities), and adjustments to relationships between activities thatgovern start, and completion times. The Activity list is a tool used to capture all scheduled activities byname and number, describe the activity clearly and concisely using language that is easily understood,and to clarify relevant scope boundaries. Fig 1.5Task # Activity Identifier Description Scope Description (WBS ID#)1 1.2 Activity Sequencing Arrange Activities based on logical relationships with task to be performed.2 1.3 Activity Resource Estimate the resources required and the level of effort Estimating to deliver. 3
  4. 4. Activity AttributesAs described on the prior page Activity Sequencing occurs through an evolutionary process. ActivityAttributes evolve from initial information such as Top Down Estimates to more detailed informationsuch as Bottom Up estimates or Expert Judgment. As more work activities are performed moreinformation is acquired and extended Activity Attribute detail is developed. Fig 1.6 Top Down Estimates Extend Description Detail Initial Detail • Predecessors • Activity ID • Successor s • WBSID • Logical Relationships • Activity Name • Resource Requirements • Responsible Parties Bottom Up Estimates/Expert Judgment 4
  5. 5. Activity AttributesFig. 1.7 illustrates an example Activity Attribute template format. Please note that there are severalActivity List and Activity Attribute formats. Templates are often kept as organizational assets to theActivity Sequencing process and used to estimate like or similar project activities. Example Activity Attribute Template Fig 1.7 Task # Activity Description Scope Description Predecessor(s) Successor(s) Logical Resource Required Identifier Relationship Type (WBS ID#) 1 1.2 Activity Arrange Activities 1.1 1.3 FS PM Sequencing based on logical relationships with task to be performed. 2 1.3 Activity Estimate the 1.2 1.2 FS PM Resource resources required Estimating and the level of effort to deliver. 5
  6. 6. Milestone ListA milestone is a significant event in the project that represents an area, phase or periodof completing or delivering a portion of the project. Often times a quality or acceptanceprocess is aligned with the milestone list. Milestone List(s) identify all milestones in theproject as well as specifies the type of milestone. There are two types of milestonesMandatory; an item explicitly defined by contract terms, or Optional; an activityidentified as a milestone by the project stakeholders. Mandatory Milestone Optional Milestone Fig 1.8 • Contract Terms • Historical • Regulatory • Similar Projects Compliance Milestones generally List of Significant don’t have durations in Project Events the project schedule Milestone List 6
  7. 7. Example Milestone ListThere are several methodologies for presenting milestone list information.Fig 1.9 illustrates an example format.Project Name:Project Manager Name:Date: TO DATEMandatory/ Wk Wk Wk Wk Wk Wk Wk Event Wk 8Optional 1 2 3 4 5 6 7 M Sign Contract M Submittal Approval O Obtain Permits O Mobilize O Receive Materials M Begin Construction Planned Completion Date = Fig 1.9 Actual Completion Date = 7
  8. 8. Project Scope StatementThe scope statement provides a documented basis for making future project decisions and for confirming or developingcommon understandings of project scope among the stakeholders. As the project progresses, the scope statement may need to berevised or refined to reflect approved changes to the scope of the project. The scope statement should include, either directly or byreference to other documents: Justification—the business need that the project was undertaken to address. The project justification provides the basis for evaluatingfuture tradeoffs Product—a brief summary of the product description.Deliverables—a list of the summary-level sub products whose full and satisfactory delivery marks completion of the project. For example,the major deliverables for a software development project might include the working computer code, a user manual, and an interactivetutorial. When known, exclusions should be identified, but anything not explicitly included is implicitly excluded Objectives—the quantifiable criteria that must be met for the project to be considered successful. Project objectivesmust include at least cost, schedule, and quality measures. Project objectives should have an attribute (e.g., cost), a metric(e.g., United States [U.S.] dollars), and an absolute or relative value (e.g., less than 1.5 million). Un-quantified objectives (e.g., “customersatisfaction”) entail high risk to successful accomplishment. Fig 1.10 Justification Product Deliverables Objectives 8
  9. 9. Example Scope Statement Template Project Name: Prepared by: Date: Project Justification: The business need that the project was undertaken to address. The project justification provides the basis for evaluating future tradeoffs. Product Description: A brief summary of the product description Project Deliverables: A list of the summary-level sub products whose full and satisfactory delivery marks completion of the project. Deliverable A Deliverable B Deliverable C Known Exclusions Project Objectives: The quantifiable criteria that must be met for the project to be considered successful. Project objectives must include at least cost, schedule, and quality measures. Cost Objectives (quantify) Schedule Objectives (start and stop dates) Quality Measures (criteria that will determine acceptability) Other Objectives 9 Fig 1.11
  10. 10. Organizational Process AssetsOrganizational Process Assets will vary considerably depending upon several considerations.Organizational Process Assets related to the activity sequencing may include checklist, PMIStemplates, manual templates, spreadsheets and potentially other tools implemented by theorganizations Project Management Office (PMO). Project Files from Fig 1.12 Past Projects Project Organizational Management Scheduling Process Assets Methodology Information System Scheduling Tool 10