Schedule Management Flashcards
Plan Schedule Management
2.3.1 (Planning Process, Schedule Mgmt KA)
The Process of establishing the policies, procedures, and documentation for planning, developing, managing, executing, and controlling the project schedule.
Inputs: Project Charter, Project Management Plan, EEF, OPA
Tools & Techniques: Expert Judgement, Data Analysis, Meetings
Outputs: Schedule Management Plan
Schedule Management Plan
2.3.1 Plan Schedule Management Output
Establishes the criteria and the activities for developing, monitoring, and controlling the schedule. May be formal or informal, highly detailed or broadly framed, based on the needs of the project.
Includes:
- Project schedule model development (tools & methodology)
- Level of accuracy
- Units of measure
- Organizational procedures links
- Project schedule model maintenance
- Control thresholds
- Rules of performance measurement
- Reporting formats
- Process descriptions
Define Activities
2.3.2 (Planning Phase, Schedule Mgmt KA)
Process of identifying and documenting the specific actions to be performed to produce the project deliverables.
Inputs: Project Management Plan, EEF, OPA
Tools & Techniques: Expert Judgement, Decomposition, Rolling Wave Planning, Meetings
Outputs: Activity List, Activity Attributes, Milestone List, Change Requests, Project Management Plan Updates
Decomposition
2.3.2 Define Activities TT
Technique used for dividing and subdividing the project scope and deliverables into smaller, more manageable parts.
Also done in Create WBS process
Rolling Wave Planning
2.3.2 Define Activities TT
Iterative planning technique in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level.
Only to be used if there is no other way to plan
Activity List
2.3.2 Define Activities Output
Comprehensive list that includes all schedule activities required on the project.
Lower level than WBS.
Includes activity identifier and a scope of work description for each activity in sufficient detail to ensure the team understands what work is required to be completed.
Activity Attributes
2.3.2 Define Activities Output
Extend the description of the activity by identifying the multiple components associated with each activity.
May include predecessor activities, successor activities, constraints, resource requirements, logical relationships, leads and lags, assumptions, imposed dates, etc.
Milestone List
2.3.2 Define Activities Output
List identifying all project milestones (significant point or event in the project) and indicates whether the milestone is mandatory or optional.
They do not have a duration since they are a moment in time.
Sequence Activities
2.3.3 (Planning Process, Schedule Mgmt KA)
Process of identifying and documenting relationships among the project activities
Inputs: Project Management Plan, Project Documents, EEF, OPA
Tools & Techniques: Precedence Diagramming Method, Dependency Determination and Integration, Leads and Lags, Project Management Information System
Outputs: Project Schedule Network Diagrams, Project Documents Updates
Precedence Diagramming Method
2.3.3 Sequence Activities TT
Technique used for constructing a schedule model in which activities are represented by nodes and are graphically linked by one or more logical relationship to show the sequence in which the activities are to be performed
Finish-to-Start (FS)
2.3.3 Sequence Activities TT
Used in PDMs
Logical relationship in which successor activity cannot start predecessor activity has finished
Finish-to-Finish (FF)
2.3.3 Sequence Activities TT
Used in PDMs
Logical relationship in which a successor activity cannot finish until a predecessor activity has finished
Start-to-Start (SS)
2.3.3 Sequence Activities TT
Used in PDMs
Logical relationship in which a successor activity cannot start until a predecessor activity has started
Start-to-Finish
2.3.3 Sequence Activities TT
Used in PDMs
Logical relationship in which a successor activity cannot finish until a predecessor activity has started.
Mandatory Dependencies
2.3.3 Sequence Activities TT
Legally or contractually required or inherent in the nature of the work
Discretionary Dependencies
2.3.3 Sequence Activities TT
Also known as preferred/preferential/soft logic
Established based on knowledge of best practices within a particular application area or some unusual aspect of the project where a specific sequence is desired even though there may be other acceptable sequences
External Dependencies
2.3.3 Sequence Activities TT
Involve relationship between project activities and non-project activities. Usually outside the project team’s control
Internal Dependencies
2.3.3 Sequence Activities TT
Involve a precedence relationship between project activities and are generally inside the project team’s control.
Lead
2.3.3 Sequence Activities TT
The amount of time a successor activity can be advanced with respect to a predecessor activity.
When you let a task get started before its predecessor is done
Lag
2.3.3 Sequence Activities TT
The amount of time a successor activity will be delayed with respect to a predecessor activity.
When you purposefully put a delay between the predecessor and successor tasks.