The document discusses project time management processes including: 1. Defining activities by decomposing work packages and identifying specific tasks. 2. Sequencing activities by determining dependencies between tasks using precedence diagramming. 3. Developing schedule attributes like activity lists, relationships, and milestones to build the project schedule network diagram.

1. Project Time Management

2. Knowledge
Area
Process
Initiating Planning Executing
Monitoring &
Control
Closing
Time
Activity Definition
Activity Sequencing
Activity Resource Estimating
Activity Duration Estimating
Schedule Development
Schedule Control
Enter phase/
Start project
Exit phase/
End project
Initiating
Processes
Closing
Processes
Planning
Processes
Executing
Processes
Monitoring &
Controlling Processes
Project Time Management

3. Schedule management plan
• - How will I develop schedule? And control it?
• - Create this Document is not identified as
Separate Process.
• - It is part of Project management plan

4. Work package
decompose
activities

5. Rolling wave planning
• 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

6. Define Activities
• The process of identifying the specific actions to be performed
produce the project deliverables.
• Work package decomposed into activities (schedule activities)
Inputs
1. Scope baseline
2. Enterprise
environmental factors
3. Organizational process
assets
Tools &
Techniques
1. Decompositions
2. Rolling wave planning
3. Templates
4. Expert judgment
Outputs
1. Activity list
2. Activity attributes
3. Milestone list

7. Activity List
• The activity list is a comprehensive list including
all schedule activities required on the project.
• The activity list includes the activity identifier
and a scope of work description for each activity
in sufficient detail to ensure that project team
members understand what work is required to be
completed

8. ACTIVITY LIST
Project Title: Date Prepared:
ID Activity Description of Work
Follow WBS
or schedule
Activity name. Description of activity in enough detail so that the
person(s) performing the work understands what is
required to complete it.

10. Activity attributes
• Activity attributes extend the description of
the activity by identifying the multiple
components associated with each activity.
• The components for each activity evolve over
time. During the initial stages of the project
they include the Activity ID, WBS ID, and
Activity Name, and when completed may
include activity codes, activity description

11. ACTIVITY ATTRIBUTES
Project Title: Date Prepared:
ID:
From activity list
Activity:
From activity list
Description of Work:
A description of the activity in enough detail so that the person(s) performing the work understands what is required to
complete it.
Predecessors Relationship Lead or Lag Successor Relationship Lead or Lag
Any activities that must occur
before the activity.
The nature of
the
relationship,
such as start-
to-start,
finish-to-start,
or finish-to-
finish.
Any required
delays between
activities (lag) or
accelerations
(lead).
Any
activities
that must
occur after
the activity.
The nature of the
relationship, such as start-
to-start, finish-t-start, or
finish-to-finish.
Any required delays
between activities (lag) or
accelerations (lead).
Number and Type of Resources Required:
The number and roles of people needed to
complete the work.
Skill Requirements:
The level of skill necessary to
complete the work (expert,
average, novice or applicable
job level).
Other Required Resources:
Any equipment, supplies, or other types of resources
needed to complete the work.
Type of Effort:
Indicate if the work is a fixed duration, fixed amount of effort, level of effort, apportioned effort or other type of work.
Location of Performance:
If the work is to be completed somewhere other than at the performing organizations site, indicate the location.
Imposed Dates or Other Constraints:
Indicate any fixed delivery dates, milestones or other constraints.
Assumptions:
List any assumptions about resource availability, skill sets, or other assumptions that impact the activity.

12. ACTIVITY ATTRIBUTES
Project Title: Date Prepared:
ID:
Activity:
Description of Work:
Predecessors Relationship Lead or Lag Successor Relationship Lead or Lag
.
.
Number and Type of Resources Required: Skill Requirements: Other Required Resources:
Type of Effort:
Location of Performance:
Imposed Dates or Other Constraints:
I
Assumptions:

13. • A milestone is a
significant point or
event in the project. A
milestone list identifies
all milestones and
indicates whether the
milestone is mandatory,
such as those required
by contract, or optional,
such as those based
upon historical
information.
Milestone List

14. MILESTONE LIST
Project Title: Date Prepared:
Milestone Milestone Description Type
Milestone name. Description of milestone in
enough detail to understand what
is needed to meet the milestone.
Internal or external.
Interim of final.
Mandatory or
optional.

16. • Sequence Activities
• Process of identifying and documenting relationship
among the project activities
Inputs
1. Activity list
2. Activity attributes
3. Milestone list
4. Project scope statement
5. Organizational process
assets
Tools &
Techniques
1. Precedence
diagramming method
(PDM)
2. Dependency
determination
3. Applying leads and lags
4. Schedule network
templates
Outputs
1. Project schedule
network diagram
2. Project document
updates

17. Precedence Diagramming Method (PDM)
• Finish-to-Start (FS)
• Finish-to-Finish (FF)
• Start-to-Start (SS)
• Start-to-Finish (SF)
logical relationships:

18. • Applying Leads & Lags
• Use leads and lags to support realistic and achievable project
schedule.
• Each activity is connected at least to one predecessor and one
successor except the start and the end.
• Leads.
– May be added to start an activity before the predecessor activity is complete.
• Lags
– Inserted waiting time between activities
A B C
predecessor Successor
B
A
B
A

19. Dependency Determination
To define sequence among activity, these type of
dependency are used:
1. Mandatory (hard logic)
– Inherent in the nature of work being done or required by the contract
– E.g. You must design before you can develop
2. Discretionary (preferred, preferential, or soft logic)
– Define base on knowledge
– Can be changed if needed
– Important when how to shorten or re-sequence the project
3. External
– Based on the need t of the party outside the project

20. .1 Project Schedule Network Diagrams
- Project schedule network diagrams are schematic
displays of the project’s schedule activities and the
logical relationships among them, also referred to as
dependencies..
- A project schedule network diagram can be produced
manually or by using project management

21. Activity-On-Node (AON)
Precedence Diagramming Method (PDM)

23. • 1- you are a project manager on a us $5.000.000 software
development Project . While Working with your project team to
develop a network diagram ,your data architects suggest that
quality could be improver if the data model is approved by senior
management before moving on the other design elements. They
support this suggestion with an article from a leading software
development journal. Which of the following best describes what
this type of inputs is called?
• A- mandatory dependency
• B- discretionary dependency
• C- external dependency
• D- heuristic

24. 2- Which of the following is not an activity
attribute:
1-Person responsible for the activity
2-Location where to perform the activity
3-Time when to perform the activity
4-Leads and Lags

25. 3-Lag means:
A-the amount of time an activity can be delaying the project
finish date.
B- the amount of time an activity can be delayed without
delaying the early start date of its successor
C- waiting time
D-the product of a forward and backward Pass

26. •4-Activity Definition is typically performed by
which of the following
A-Project Manager who created the WBS
B.Project Team Members responsible for the
work package
C.Project Officer
D.Project Stakeholder

27. 5- A schedule activity may begin 10
days before the predecessor activity
finishes This is an example of
A-ADM
2-PDM
C- A dependency with lag
D- A dependency with lead

28. Thank you