6 Flashcards

1
Q

The process of establishing the policies, procedures, and documentation for planning, developing, managing, executing, and controlling the project schedule

A

Plan Schedule Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

The process of identifying and documenting the specific actions to be performed to produce the project deliverables.

A

Define Activities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

The process of identifying and documenting relationships among the project activities.

A

Sequence Activities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

The process of estimating the number of work periods needed to complete individual activities with the estimated resources.

A

Estimate Activity Durations

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

The process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule model for project execution and monitoring and controlling.

A

Develop Schedule

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

The process of monitoring the status of the project to update the project schedule and manage changes to the schedule baseline.

A

Control Schedule

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

This approach, typically used in a Kanban system, is based on the theory-of constraints and pull-based scheduling concepts from lean manufacturing to limit a team’s work in progress in order to balance demand against the team’s delivery throughput.
It does not rely on a schedule that was developed previously for the development of the product or product increments, but rather pulls work from a backlog or intermediate queue of work to be done immediately as resources become available.

A

On-demand scheduling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

This is a form of rolling wave planning based on adaptive life cycles, such as the agile approach for product development.
This approach is often used to deliver incremental value to the customer or when multiple teams can concurrently develop a large number of features that have few interconnected dependencies.

A

Iterative scheduling with a backlog

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

The key benefit of this process is that it provides guidance and direction on how the project schedule will be managed throughout the project. This process is performed once or at predefined points in the project.

A

Plan Schedule Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

It´s a component of the project management plan that establishes the criteria and the activities for developing, monitoring, and controlling the schedule. It may be formal or informal, highly detailed, or broadly framed based on the needs of the project and includes appropriate control thresholds.

A

Schedule management plan

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

The key benefit of this process is that it decomposes work packages into schedule activities that provide a basis for estimating, scheduling, executing, monitoring, and controlling the project work.
This process is performed throughout the project.

A

Define Activities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

It´s an iterative planning technique in which the work to be accomplished in the near term is planned in detail, while work further in the future is planned at a higher level. It is a form of progressive elaboration applicable to work packages, planning packages, and release planning when using an agile or waterfall approach.

A

Rolling wave planning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

It includes the schedule activities required on the project. It will be updated periodically as the project progresses. It includes an 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.

A

Activity list

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Extend the description of the activity by identifying multiple components associated with each activity, for each activity evolve over time. During the initial stages of the project, they include the unique activity identifier (ID), WBS ID, and activity label or name.
They´re used for schedule development and for selecting, ordering, and sorting the planned schedule activities in various ways within reports

A

Activity attributes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

The key benefit of this process is that it defines the logical sequence of work to obtain the greatest efficiency given all project constraints. This process is performed throughout the project.

A

Sequence Activities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

It´s a technique used for constructing a schedule model in which activities are represented by nodes and are graphically linked by one or more logical relationships to show the sequence in which the activities are to be performed.

A

Precedence diagramming method (PDM)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

PDM includes four types of dependencies or logical relationships:

A

 Finish-to-start (FS)
 Finish-to-finish (FF)
 Start-to-start (SS)
 Start-to-finish (SF)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Dependencies may be characterized by the following attributes:

A

Mandatory or discretionary, internal or external.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Dependencies are those that are legally or contractually required or inherent in the nature of the work.

A

Mandatory dependencies

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Dependencies 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. This order is not mandatory and both activities may occur at the same time (in parallel) but performing the activities in sequential order reduces the overall project risk.

A

Discretionary dependencies

21
Q

Involve a relationship between project activities and nonproject activities. These dependencies are usually outside of the project team’s control. The project management team determines which dependencies during the process of sequencing the activities.

A

External dependencies

22
Q

Involve a dependency relationship between project activities and are generally inside the project team ’s control. The project management team determines them during the process of sequencing the activities

A

Internal dependencies

23
Q

It’s the amount of time a successor activity can be advanced with respect to a predecessor activity.

A

Lead

24
Q

It’s the amount of time a successor activity will be delayed with respect to a predecessor activity.

A

Lag

25
Q

It’s a graphical representation of the logical relationships, also referred to as dependencies, among the project schedule activities.

A

Project schedule network diagram

26
Q

o Activities that have multiple predecessor activities indicate a:

A

path convergence

27
Q

Activities that have multiple successor activities indicate a:

A

path divergence

28
Q

The key benefit of this process is that it provides the amount of time each activity will take to complete. This process is performed throughout the project.

A

Estimate Activity Durations

29
Q

When one factor (e.g., resource) used to determine the effort required to produce a unit of work is increased while all other factors remain fixed, a point will eventually be reached at which additions of that one factor start to yield progressively smaller or diminishing increases in output.

A

Law of diminishing returns

30
Q

It’s a technique for estimating the duration or cost of an activity or a project using historical data from a similar activity or project.

A

Analogous estimating

31
Q

It’s an estimating technique in which an algorithm is used to calculate cost or duration based on historical data and project parameters.

A

Parametric estimating

32
Q

helps define an approximate range for an activity’s duration: Most likely, Optimistic and Pessimistic

A

THREE-POINT ESTIMATING

33
Q

It’s a method of estimating project duration or cost by aggregating the estimates of the lower level components of the WBS.

A

Bottom-up estimating

34
Q

It’s used to determine the amount of contingency and management reserve needed for the project.

A

Reserve analysis

35
Q

They’re quantitative assessments of the likely number of time periods that are required to complete an activity, a phase, or a project, may include some indication of the range of possible results.

A

Duration estimates

36
Q

The key benefit of this process is that it generates a schedule model with planned dates for completing project activities.

A

Develop Schedule

37
Q

It’s used to estimate the minimum project duration and determine the amount of schedule flexibility on the logical network paths within the schedule model.
It’s the sequence of activities that represents the longest path through a project, which determines the shortest possible project duration.

A

critical path method

38
Q

A technique in which start and finish dates are adjusted based on resource constraints with the goal of balancing the demand for resources with the available supply.
It can be used when shared or critically required resources are available only at certain times or in limited quantities, or are overallocated, such as when a resource has been assigned to two or more activities during the same time period.

A

Resource leveling

39
Q

A technique that adjusts the activities of a schedule model such that the requirements for resources on the project do not exceed certain predefined resource limits. As opposed to resource leveling, the project’s critical path is not changed and the completion date may not be delayed

A

Resource smoothing

40
Q

They’re used to shorten or accelerate the schedule duration without reducing the project scope in order to meet schedule constraints, imposed dates, or other schedule objectives.

A

Schedule compression techniques

41
Q

It provides a high-level summary timeline of the release schedule (typically 3 to 6 months) based on the product roadmap and the product vision for the product’s evolution.
Also determines the number of iterations or sprints in the release, and allows the product owner and team to decide how much needs to be developed and how long it will take to have a releasable product based on business goals, dependencies, and impediments.

A

Agile release planning

42
Q

The project schedule it is more often presented graphically, using one or more of the following formats:

A

 Bar charts
 Milestone charts
 Project schedule network diagrams

43
Q

It’s an output of a schedule model that presents linked activities with planned dates, durations, milestones, and resources. At a minimum, e includes a planned start date and planned finish date for each activity.

A

The project schedule

44
Q

The project schedule it is more often presented graphically, using one or more of the following formats:

A

 Bar charts
 Milestone charts
 Project schedule network diagrams

45
Q

The key benefit of this process is that the schedule baseline is maintained throughout
the project.

A

Control Schedule

46
Q

Schedule performance measurements such as schedule variance (SV) and schedule performance index (SPI) are used to assess the magnitude of variation to the original schedule baseline.

A

Earned value analysis

47
Q

This chart tracks the work that remains to be completed in the iteration backlog. It is used to analyze the variance with respect to an ideal burndown based on the work committed from iteration planning. A forecast trend line can be used to predict the likely variance at iteration completion and take appropriate actions during the course of the iteration

A

Iteration burndown chart

48
Q

Estimates or predictions of conditions and events in the project’s future based on information and knowledge available at the time, for the schedule.

A

Schedule forecasts