Chap 6.3 Sequence Activity

PMBOK 6 - All rights reserved; By: Anand Bobade (nmbobade@gmail.com)
Trainer: Anand BobadePMBOK 6th Edition, 2019, All rights reserved.
Sequence
Activities
PMPChapter 6 –
Project Schedule Management
SIXTH EDITION

6.3 Sequence Activities
Overview
Sequence activity Process definition
Sequence Activity: ITTO
Activity dependencies?
What is PDM?
Logical Relationship?
What is Project schedule network diagram?
Review

Schedule Management processes
Plan Schedule
management
Define Activities Sequence Activities
Estimate Activity
Duration
Develop Schedule Control Schedule
P P P
MCP P

Sequence Activities -> Overview
Prepare Training
Presentation
Identify
Participants
Schedule
Training
Setup Training
environment
Arrange Training
Facility
Conduct Training
Identify
Participants
Schedule Training
Prepare Training
Presentation
Arrange Training
Facility
Setup Training
environment
Conduct Training
Activities are logically sequenced
Activities are randomly listed

The process of identifying & documenting relationships
among project activities.
Defines logical sequence of work to obtain greatest
efficiency within project constraints.
Sequence Activities->Definition
Project
Activities
Identifying &
Documenting
Relationship

6.3 – Sequence Project Activities -> ITTO
Precedence Diagramming
method
Dependency determination
& Integration
Leads & Lags
PMIS
Project Management
plan
Project Documents
Enterprise
environmental factors
Organizational process
assets
Project Schedule
Network Diagram
Project Documents
updates
Inputs Tools & Techniques Outputs

Sequence Activities -> Input
PMP
Project
Documents
EEF
Organizational
process assets

Project
Management plan
Following plans & baseline will be key inputs:
Schedule Management plan:
• Identifies scheduling method & tools to be
used for project, which will guide on
sequencing activities.
Scope baseline:
• Assumptions, constraints, acceptance
criteria's etc.
Sequence Activities -> Input -> Project Management plan
Project scope
statement:
WBS: WBS dictionary

Project Documents
Following Project Documents will be key inputs:
Activity list:
•All schedule activities required which are to be
sequenced. Dependencies & constraints can
influence sequencing.
Activity attributes:
•Describes necessary sequence of events or defined
predecessor & successor activities.
Milestone list:
•It will have schedule date for specific milestone,
which may influence the way activities are
sequenced.
Assumption log:
•The assumptions may influence the way the
activities are sequenced.
Sequence Activities -> Input -> Project Documents

Enterprise
environmental factors
Sequence Activities -> Input -> Enterprise environmental factors
PMIS
Work authorization
systems
Government or
industry standards
Following EEF may be input to this process:

Organizational
process assets
Following OPA may be input to this process:
Sequence Activities -> Input -> Organizational process assets
Procedures &
Policies
Templates
Lessons Learned
Register

Sequence Activities -> Tools & Techniques
Dependency
determination &
Integration
Precedence
Diagramming
method
Leads & Lags PMIS

Dependency
determination &
Integration
Determine how one activity is dependent of another
Types:
Mandatory
dependency
Discretionary
dependency
External
dependency
Internal
dependency
Sequence Activities->T&T->Dependency Determination

Dependency
determination &
Integration
• Legally or contractually required
• Inherent in the nature of work
Mandatory
dependency
(Hard logic)
Requirements
Documentation
Client Approval Raise Invoice
Lay Building Foundation Construct Floor

Dependency
determination &
Integration
• There could be more than one way to define the sequence
between 2 activities.
• Based on best practices, or Defined by project team (Flexible)
Discretionary
dependency
(Soft logic)
Develop Module A Develop Module B
You can always change development sequence
from A->B->C to sequence A->C->B, if required.
While fast-tracking, discretionary dependencies are
reviewed, modification or removed.

Dependency
determination &
Integration
• Relationships between project and non-project activities
• Activities are done by external people.
• Outside project control.
External
dependencies
Delivery of Equipment Start work
Vendor team on
boarding
Start project work

Dependency
determination &
Integration
• Inside project team’s control.
• Can be easily modified if necessary as compared to external
dependencies.
Internal
dependencies
Build Software
application
Code Review System Testing

Precedence
Diagramming
method
Method of constructing a project schedule network diagram, that represent
activities & their relationship.
Sequence Activities -> Tools & Techniques -> PDM

Precedence
Diagramming
method
Method of constructing a project schedule network diagram, that represent
activities & their relationship.
•Activities are represented by boxes, also called as nodes.Nodes
•shows relationships between activities.Arrows
•Activity logically comes before another activity that it is dependent uponpredecessor
•Activity logically comes after another activity in a scheduleSuccessor

Precedence
Diagramming
method
How to develop schedule network diagram.
Activity Activity Description Duration
(days)
Predecessor
A Collect Requirement 50 -
B System Design 25 A
C Build Module 1 40 B
D Build Module 2 50 C
E Build Module 3 10 B
F Build Module 4 15 E
G Build Module 5 30 B
H System Testing 25 D,F,G

Activity Activity Description Duration (days) Predecessor
A Collect Requirement 50 -
B System Design 25 A
C Build Module 1 40 B
D Build Module 2 50 C
E Build Module 3 10 B
F Build Module 4 15 E
G Build Module 5 30 B
H System Testing 25 D,F,G
Collect
Requirements
(A - 50days)
Start
System Design
(B - 20d)
Build module 1
(C - 40 day)
Build module 2
(D - 50 day)
Build module 3
(E-10 day)
Build module 5
(G - 30 day)
Testing
(H-25 days)
Build module 4
(F - 15 day)
End
• = A->B->C->D->H = 50+20+40+50+25 = 185Path1
• = A->B->E->F->H = 50+20+10+15+25 = 120Path2
• = A->B->G->H = 50+20+30+25 = 125Path3
Precedence
Diagramming
method

Precedence
Diagramming
method
Logical Relationships
• Task B can not start until Task
A finishes
Finish to start
- FS
• Task B can not start until Task
A starts
Start to Start
- SS
• Task B can finish until Task A
finishes
Finish to
Finish - FF
• Task A can not finish until Task
B starts
Start to
Finish - SF

Precedence
Diagramming
method
• Drying the car can not start until Car is washedFS
• Levelling of Concrete floor cant not be started until you
start pouring the mixed concrete
SS
Wash a Car (A) Dry a Car (B)
Mix & pour Concrete (A)
Leveling the Concrete (B)

Precedence
Diagramming
method
• Broadcasting of a match cannot finish until the match is finishedFF
• start of the new shift of the security guard signal the finish shift of
the current security guard
SF
Match in progress (A)
Broadcasting (B)
Shift Finished for
Guard1 (A)
Shift started for
Guard2 (B)

Leads & Lags
Lead: It is amount of time where successor activity can be
advanced w.r.t. predecessor activity.
Lag: It is amount of time whereby a successor activity will be
delayed w.r.t. a predecessor activity.
Sequence Activities -> T&T -> Leads & Lags
Business Requirement
(BRS)
System Requirement
(SRS)
Contract
Signed
Team On-
board
Lead
1 week
Lag
3 week
Business Requirement
(BRS – 4 weeks)
System Requirement
(SRS – 4 weeks)
W1 W2 W3 W4 W5 W6 W7 W8 W1 W2 W3 W4 W5 W6 W7 W8
Contract
signed
Team On-
board

PMIS
This is the scheduling software that help sequence the activities (such as
Microsoft Project or Primavera).
Sequence Activities -> Tools & Techniques -> PMIS

Project Schedule
Network Diagram
Project Documents
updates
Sequence Activities -> Output

Project Schedule
Network Diagram
It is a graphical representation of logical relationship between activities.
A summary narrative can accompany the diagram and describe the basic approach
Sequence Activities->Output-> Project Schedule Network Diagram
• Multiple predecessor activities (Activity E)Path convergence
• Multiple successor activities (Ex: Activity H)Path divergence
• Activities with convergence / divergencegreater risk

Project Documents
updates
Activity list:
• The associated list of activity attributes may
be updated
Activity attributes:
• predecessor & successor activities.
• Leads & Lags
Milestone list:
• Milestones may be impacted by changes in
the relationships between activities.
Assumption log:
• New assumptions about dependencies,
relationship, leads and lags etc.
Sequence Activities -> Output->Project Doc. updates
Following Project Documents may get updated:

Sequence Activities -> Review
Overview - Why sequencing is important?
Process definition
Process - ITTO
Why are different types of activity dependencies?
What is PDM?
What are different logical Relationship?
What is Project schedule network diagram?

Chap 6.3 Sequence Activity

More Related Content

What's hot

Similar to Chap 6.3 Sequence Activity

More from Anand Bobade

Chap 6.3 Sequence Activity