Key Terms S Flashcards

1
Q

schedule baseline

A

The final, approved project schedule that is used during project execution to monitor project progress.

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

schedule control

A

The process of documenting and managing changes to the project schedule

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

Schedule development

A

Calculating and preparing the schedule of project activities, which becomes the schedule baseline. It determines activity start and finish dates, finalizes activity sequences and durations, and determines activity duration estimates

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

schedule performance index (SPI)

A

Measures the progress to date against the progress that was planned. The SPI indicator acts as an efficiency rating. If the result is greater than one, performance is better than expected, and you’re ahead of schedule. If it’s less than one, performance is less than expected, and you ’ re behind schedule. The formula is SPI = EV / PV.

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

schedule update

A

Any change that is made to the project schedule as part of the ongoing
work involved with managing the project.

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

schedule variance (SV)

A

The difference between a task’s progress as compared to its estimated progress represented in terms of cost. The formula is SV = EV – PV

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

scope

A

The description of the work involved to complete the project. It defines both what
is included in the project and what is excluded from the project

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

scope control

A

The process of documenting and managing changes to project scope. Any
modification to the agreed - upon WBS is considered a scope change. Changes in product scope will require changes to project scope, and scope changes always require schedule changes.

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

scope creep

A

The minor changes or small additions that are made to the project outside of a formal scope change process that cause project scope to grow and change.

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

scope definition

A

Per the PMBOK Guide, the process of breaking down the major deliverables from the scope statement to create the WBS. For purposes of the CompTIA objectives and exam, scope definition is used in a much broader sense to cover several scope
planning elements, including the scope statement and the scope management plan.

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

scope management plan

A

Defines the process for preparing the scope statement and the WBS. This also documents the process that manages project scope and changes to project
scope

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

scope planning

A

The process of defining the scope management plan, the scope statement,
and the WBS and WBS dictionary.

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

scope statement

A

Documents the product description, key deliverables, success and acceptance criteria, key performance indicators, exclusions, assumptions, and constraints. The scope statement is used as a baseline for future project decisions

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

scope verification

A

A process that concerns formally accepting the deliverables of the project and obtaining sign - off that they’re complete.

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

scoring model

A

One of the benefit measurement methods used for project selection. It contains a predefined list of criteria against which each project is ranked. Each criterion has
a scoring range and a weighting factor. A scoring model can also be used as a tool to select from among competing vendors

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

sequencing

A

Putting the project activities in the order in which they will take place.

17
Q

slack time

A

The amount of time allowed to delay the early start of a task without delaying the finish date of the project. This is also known as float time .

18
Q

sole source

A

A requirement that a product or service must be obtained from a single vendor in government work; also includes justification

19
Q

solictation

A

A requirement that a product or service must be obtained from a single vendor in government work; also includes justification

20
Q

sponsor

A

An executive in the organization with authority to allocate funds, assign resources, and enforce decisions regarding the project.

21
Q

staff acquisition

A

Obtaining human resources and assigning them to the project. Human resources may come from inside or outside the organization

22
Q

staffing management plan

A

Documents when and how human resources will be added to and released from the project team and what they will be working on while they are part of the team.

23
Q

stakeholder

A

A person or an organization that has something to gain or lose as a result of
the project. Most stakeholders have a vested interest in the outcomes of the project

24
Q

start-to-finish

A

A task relationship where the finish of the successor task is dependent on
the start of its predecessor.

25
Q

start-to-start

A

A project task relationship where the start of the successor task depends on the start of the predecessor task

26
Q

starvation

A

A type of project ending where resources are cut off from the project.

27
Q

statement of work (SOW)

A

Contains the details of a procurement item in clear, concise terms and includes the project objectives, a description of the work of the project, and concise specifications of the product or services required.

28
Q

status date

A

The date when the project manager measures how much has been spent on a specific task.

29
Q

success criteria

A

See acceptance criteria

30
Q

successor

A

A task on the network diagram that occurs after another task