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 Assets1 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 ListComprehensive list ofDetailed Scope Activity Identifier scheduled activities Description2 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 easilyunderstood, and to clarify relevant scope boundaries. Fig 1.5Task # Activity IdentifierDescription Scope Description (WBS ID#)11.2Activity Sequencing Arrange Activities based on logical relationships withtask to be performed.21.3Activity Resource Estimate the resources required and the level of effortEstimatingto deliver.3 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.6Top Down EstimatesExtend Description Detail Initial Detail Predecessors Activity ID Successor s WBSID Logical Relationships Activity Name Resource Requirements Responsible Parties Bottom Up Estimates/Expert Judgment4 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 DescriptionPredecessor(s) Successor(s) Logical Resource Required IdentifierRelationship Type (WBS ID#) 1 1.2ActivityArrange Activities 1.11.3FSPMSequencingbased on logicalrelationships withtask to beperformed. 2 1.3ActivityEstimate the 1.21.2FSPMResourceresources requiredEstimatingand the level ofeffort to deliver. 5 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 MilestoneOptional MilestoneFig 1.8 Contract Terms Historical Regulatory Similar Projects Compliance Milestones generallyList of Significantdont have durations in Project Events the project schedule Milestone List6 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 WkWk WkEventWk 8Optional 12345 67 MSign Contract MSubmittal Approval OObtain Permits OMobilize OReceive Materials MBegin Construction Planned Completion Date = Fig 1.9 Actual Completion Date =7 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: Justificationthe business need that the project was undertaken to address. The project justification provides the basis for evaluatingfuture tradeoffs Producta brief summary of the product description.Deliverablesa 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 Objectivesthe 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 JustificationProductDeliverablesObjectives8 9. Example Scope Statement TemplateProject Name:Prepared by:Date:Project Justification:The business need that the project was undertaken to address. The project justificationprovides the basis for evaluating future tradeoffs.Product Description:A brief summary of the product descriptionProject Deliverables: A list of the summary-level sub products whose full and satisfactory delivery marks completionof the project.Deliverable ADeliverable BDeliverable CKnown ExclusionsProject Objectives: The quantifiable criteria that must be met for the project to be considered successful. Projectobjectives must include at least cost, schedule, and quality measures.Cost Objectives (quantify)Schedule Objectives (startand stop dates)Quality Measures (criteria thatwill determine acceptability)Other Objectives9 Fig 1.11 10. Organizational Process AssetsOrganizational Process Assets will vary considerably depending upon several considerations.Organizational Process Assets related to the activity sequencing may include checklist, PMIS templates,manual templates, spreadsheets and potentially other tools implemented by the organizations ProjectManagement Office (PMO). ProjectFiles fromFig 1.12 Past ProjectsProjectOrganizational ManagementScheduling Process Assets Methodology InformationSystem SchedulingTool10