1. Activity Sequencing Inputs
The inputs to the Activity Sequencing process are spread across two knowledge areas. The Scope
Definition Process within the Project Scope Management Knowledge Area produces the Project Scope
Statement input. In addition the organization which employs the project team may also provide
Organizational Process Assets relevant to the Activity Sequencing process. And finally the Activity
Definition Process within the Time Management Knowledge Area produces three of the five inputs to
our Activity Sequencing process area; Activity List, Activity Attributes and Milestone List are all outputs
to the Activity Definition process area.
Fig 1.3
Activity List
Activity Attributes
Milestone List
Project Scope Statement
Organizational Process Assets
1

2. Activity List
The activity list is a comprehensive list of all activities required on the project. The activity list contains
the work descriptions for project team members. The description needs to be clear enough that
everyone 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. Example Initial Activity List
The Activity Sequencing process evolves; meaning initially activity list contain minimal detail however
as information is obtained more pertinent detail is documented in Attribute List and Milestone List. The
activity sequencing process organizes data about project activity that will aid planning to carryout the
work related to delivering the project. Examples of relevant detail and considerations may include what
needs to happen before an activity can be completed (predecessor activities), what will happen after the
activity is completed (successor activities), and adjustments to relationships between activities that
govern start, and completion times. The Activity list is a tool used to capture all scheduled activities by
name and number, describe the activity clearly and concisely using language that is easily understood,
and to clarify relevant scope boundaries.
Fig 1.5
Task # 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. Activity Attributes
As described on the prior page Activity Sequencing occurs through an evolutionary process. Activity
Attributes evolve from initial information such as Top Down Estimates to more detailed information
such as Bottom Up estimates or Expert Judgment. As more work activities are performed more
information 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. Activity Attributes
Fig. 1.7 illustrates an example Activity Attribute template format. Please note that there are several
Activity List and Activity Attribute formats. Templates are often kept as organizational assets to the
Activity 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. Milestone List
A milestone is a significant event in the project that represents an area, phase or period
of completing or delivering a portion of the project. Often times a quality or acceptance
process is aligned with the milestone list. Milestone List(s) identify all milestones in the
project as well as specifies the type of milestone. There are two types of milestones
Mandatory; an item explicitly defined by contract terms, or Optional; an activity
identified 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. Example Milestone List
There are several methodologies for presenting milestone list information.
Fig 1.9 illustrates an example format.
Project Name:
Project Manager Name:
Date:
TO DATE
Mandatory/ Wk Wk Wk Wk Wk Wk Wk
Event Wk 8
Optional 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. Project Scope Statement
The scope statement provides a documented basis for making future project decisions and for confirming or developing
common understandings of project scope among the stakeholders. As the project progresses, the scope statement may need to be
revised or refined to reflect approved changes to the scope of the project. The scope statement should include, either directly or by
reference to other documents:
Justification—the business need that the project was undertaken to address. The project justification provides the basis for evaluating
future 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 interactive
tutorial. 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 objectives
must 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., “customer
satisfaction”) entail high risk to successful accomplishment.
Fig 1.10
Justification Product
Deliverables Objectives
8

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. Organizational Process Assets
Organizational 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
organization's Project Management Office (PMO).
Project
Files from
Fig 1.12
Past
Projects
Project Organizational
Management Scheduling
Process Assets Methodology
Information
System
Scheduling
Tool
10