SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
Comptia Project + Project Management
Start Test
Study First
Subjects
:
certifications
,
comptia-project-+
,
it-skills
Instructions:
Answer 50 questions in 15 minutes.
If you are not ready to take this test, you can
study here
.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.
This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. The degree to which a set of inherent characteristics fulfills requirements
stakeholder
bottom-up estimating (Technique)
quality
standard
2. Sum of products - services and results to be provided as a project
scope
project schedule (Output/Input)
opportunity
enterprise environmental factors (Input/Output)
3. The calculation of late finish dates and late start dates for uncompleted portions of all schedule activities. determined by working backward through the schedule network logic from the projects end date
request for proposal (RFP)
backward pass
project quality management (Knowledge Area)
virtual team
4. Estimate or prediction of conditions and events in the projects future based on information and knowledge available at the time of the forecast. information is based on the project's past performance and expected future performance
sub phase
forecast
brainstorming (Technique)
specification limits
5. The process of completing each project procurement
time and material contract (T&M)
result
expected monetary value (EMV)
close procurements (Process)
6. Fixed price contract where the buyer pays the seller a set amount regardless of the sellers costs
assumptions analysis (Technique)
objective
firm fixed price contract (FFP)
co-location (Technique)
7. Organizational body or entity assigned various responsibilities related to the centralized and coordinated management of those projects under its domain.
monitor and control project work (Process)
requirement
material
project management office (PMO)
8. Information gathering technique examines the project from the perspective of each projects strengths - weaknesses - opportunities - and threats to increase the breadth of the risks considered by risk management
value engineering
project scope management (Knowledge Area)
strengths - weaknesses - opportunities - threats analysis (SWOT)
workaround
9. Change to project scope. almost always requires an adjustment to the project cost or schedule
early finish date (EF)
bottom-up estimating (Technique)
scope change
project communications management (Knowledge Area)
10. Technique that computes or iterates the project cost or project schedule many times using input values selected at random from probability distributions of possible costs or durations - to calculate a distribution of total project costs or completion
co-location (Technique)
Monte Carlo analysis
procurement documents (Output/Input)
perform quantitative analysis (Process)
11. Degree - amount or volume of risk that an organization or individual will withstand
s-curve
common cause
risk tolerance
earned value (EV)
12. Evaluation of whether or not a product - service - or system complies with a regulation - requirement - specification or imposed condition.
budget
free float
verification
near critical activity
13. Auditing the quality requirements and the results from quality control measurements to ensure appropriate quality standards and operational definitions are used
perform quality assurance (Process)
scheduled finish date (SF)
practice
estimate costs (Process)
14. The latest possible point in time that a schedule activity may begin based upon the schedule network logic - the project completion date and any constraints assigned to schedule activities without violating schedule constraint or delaying project com
specification limits
change control board (CCB)
statement of work (SOW)
late start date (LS)
15. Analysis. a statistical technique that calculates the average outcome when the future includes scenarios that may or may not happen. used in decision tree analysis.
expected monetary value (EMV)
common cause
plan communications (Process)
plan risk response (Process)
16. Document describing how roles and responsibilities - reporting relationships and staffing management will be addressed and structured for the project
special cause
project calendar
regulation
human resource plan
17. Category or rank used to distinguish items that have the same functional use but do not share the same requirements for quality
threat
lessons learned knowledge base
project charter (Output/Input)
grade
18. Calculated projection of cost performance that must be achieved on the remaining work to meet a specified management goal. ratio of remaining work to funds remaining
Delphi technique (Technique)
develop schedule (Process)
to complete performance index (TCPI)
preventative action
19. The document that describes the communications needs and expectations for the project; how and in what format information will be communicated; when and where each communication will be made; wan who is responsible for providing each type of communic
value engineering
Delphi technique (Technique)
authority
communications management plan (Output/Input)
20. Developing an approximation of the monetary resources needed to complete project activities
project cost management (Knowledge Area)
estimate costs (Process)
project management information system (PMIS) (Tool)
scope management plan(Output/Input)
21. Group of related schedule activities aggregated at some summary level and displayed as a single activity (at the summary level)
claim
summary activity
execute
logical relationship
22. Continuously improving and detailing a plan as more detailed and specific information and more accurate estimates become available as the project progresses and thereby producing more accurate and complete plans that result from the successive iterat
project organization chart (Output/Input)
progressive elaboration (Technique)
product
resource breakdown structure
23. Budgeted cost of work performed
acceptance criteria
project management team
BCWP
program
24. The formally documented identification of a defect in a project component with a recommendation to either repair the defect or completely replace the component
time scaled schedule network diagram (Tool)
quality
earned value (EV)
defect repair
25. Learning gained from the process of performing the project
authority
project life cycle
project management knowledge area
lessons learned(Output/Input)
26. Processes and activities needed to identify - define - combine - unify and coordinate the various processes and project management activities within the project management process groups
responsibility assignment matrix (RAM) (Tool)
project initiation management (Knowledge Area)
virtual team
projectized organization
27. Group of potential causes of risk. such as technical - external - organizational - environmental - project management. a category may include subcategories
risk category
project management system (Tool)
predecessor activity
perform qualitative analysis (Process)
28. Specific version of the schedule model used to compare actual results to the plan to determine if preventive or corrective action is needed to meet the project objectives
decision tree analysis (Technique)
schedule performance index (SPI)
manage project team (Process)
schedule baseline
29. Provider of products - services or results
seller
assumptions
pareto chart (Tool)
specification
30. Authorized budget assigned to the scheduled work to be accomplished for a schedule activity or work breakdown structure component
secondary risk
total float
planned value (PV)
special cause
31. Identifying and documenting project roles - responsibilities - and required skills - reporting relationships and creating a staffing management plan.
schedule model (Tool)
pareto chart (Tool)
develop human resource plan (Process)
project cost management (Knowledge Area)
32. Performing the work defined in the project management plan to achieve the project's objectives
direct and manage project execution (Process)
project scope
scope management plan(Output/Input)
earned value (EV)
33. Making relevant information available to project stakeholders
grade
distribute information (Process)
project phase
specification
34. Aggregation of the processes - tools - techniques - methodologies - resources and procedures to manage a project
project management body of knowledge
estimate costs (Process)
probability and impact matrix (Tool)
project management system (Tool)
35. Cost - time - quality - technical or resource value used as a parameter and which may be included in product specification. crossing the threshold should trigger some action.
activity identifier
project management team
technique
threshold
36. Implementing risk response plans - tracking identified risks - monitoring residual risks - identifying new risks and evaluating risk process throughout the project
failure mode and effect analysis (FMEA) (Technique)
define activities (Process)
technique
monitor and control risks (Process)
37. Estimating the type and quantities of material - people - equipment or supplies required to perform the activity
project management system (Tool)
estimate activity resources (Process)
triggers
earned value technique (EVT) (Technique)
38. Defined systematic procedure employed by a human resource to perform an activity to produce a product or result or deliver a service that may employ one or more tools
resource
change control
technique
defect repair
39. Term used in precedence diagramming method for a logical relationship in current usage. precedence relationship - logical relationship and dependency are interchangeably used
earned value (EV)
precedence relationship
work breakdown structure component
actual cost (AC)
40. Number of labor units required to complete a schedule activity or work breakdown structure component
effort
distribute information (Process)
request for information (RFI)
start date
41. The enterprise whose personnel are directly involved in doing the work of the project
log
acceptance criteria
successor activity
performing organization
42. Subdivision (fragment) of a project schedule network diagram - usually representing a subproject or work package.
stakeholder
precedence relationship
sub network
schedule network analysis (Technique)
43. Any of all process related assets - from any or all of the organizations involved in the project that are or can be used to influence the project's success. these process assets include formal or informal plans - policies - procedures and guidelines.
organizational process assets (Output/Input)
standard
project risk management (Knowledge Area)
scope creep
44. Document describing how project risk management will be structured and performed on the project. contains the list of project risks - the results of risk analysis and risk responses
rolling wave planning (Technique)
risk management plan (Output/Input)
influence diagram (Tool)
lag (Technique)
45. An imperfection or deficiency in a project component where that component does not meet requirements or specifications and needs to be either repaired or replaced
defect
milestone
special cause
precedence relationship
46. Identifying - documenting - approving or rejecting and controlling changes to the project baselines
scheduled finish date (SF)
matrix organization
change control
early finish date (EF)
47. Graphic display of schedule related information.
sponsor
resource breakdown structure
Gantt chart (Tool)
project manager
48. The latest possible point in time that a schedule activity maybe completed based upon schedule network logic - the completion date and any constraints assigned to the schedule activities without violating a schedule constraint or delaying the project
co-location (Technique)
output (Process)
late finish date (LF)
project management team
49. Point in time that work was scheduled to finish on a schedule activity. called planned finish date
executing processes (Process Group)
project schedule (Output/Input)
scheduled finish date (SF)
scope creep
50. Common way to determine whether a risk is considered low - moderate - or high by combining the two dimensions of a risk: its probability of occurrence and its impact on objectives if it occurs
estimate activity durations (Process)
project charter (Output/Input)
practice
probability and impact matrix (Tool)