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. Temporary endeavor undertaken to create a unique product - service or result
constraint (Input)
project
code of accounts (Tool)
technique
2. Processes required to manage the timely completion of a project
plan quality (Process)
precedence diagramming method (PDM) (Technique)
project time management (Knowledge Area)
program management
3. Process which generates hundreds or thousands of probable performance outcomes based on probability distributions for cost and schedule on individual tasks. the outcomes are used to generate a probability distribution for a project as a whole.
human resource plan
estimate (Output/Input)
Monte Carlo simulation
input (Process) input
4. An artifact that is produced - is quantifiable and can be either an end item in itself or a component item
grade
product
activity
define scope (Process)
5. Point in time that work was scheduled to finish on a schedule activity. called planned finish date
resource histogram
external deliverable
slack
scheduled finish date (SF)
6. Provision in the project management plan to mitigate cost and or schedule risk. modifier: management reserve (unknown risks) - contingency reserve (known - but unplanned risks)
reserve
define scope (Process)
total float
specification limits
7. A table that links requirements to their origin and traces them throughout the project life cycle
configuration management system (Tool)
decomposition (Technique)
requirements traceability matrix
analogous estimating (Technique)
8. An estimating technique that uses the values of parameters - such as scope - cost - budget - and duration or measures of scale such as size - weight - and complexity from a previous similar activity as the basis of estimating the same parameter or me
sequence activities (Process)
analogous estimating (Technique)
project scope management (Knowledge Area)
work package
9. Condition or capability that must be met or possessed by a system - product - service result or component to satisfy a contract - standard - specification or other formally imposed document.
requirement
projectized organization
change control board (CCB)
finish date
10. A mutually binding agreement that obligates the seller to provide the specified product or service or result and obligates the buyer to pay for it
baseline
project communications management (Knowledge Area)
failure mode and effect analysis (FMEA) (Technique)
contract (Output/Input)
11. 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
resource leveling (Technique)
functional manager
successor activity
Monte Carlo analysis
12. The smallest unit of time used in scheduling a project. calendar units are generally in hours - days - or weeks - but can also be in quarters years - months - shifts - or even minutes
triggers
calendar unit
finish to finish (FF)
fast tracking (Technique)
13. Examining or measuring to verify whether an activity - component - product - result of service conforms to specified requirements.
risk acceptance (Technique)
finish to start (FS)
request for quotation (RFQ)
inspection (Technique)
14. Identifying quality requirements and/or standards for the project and product and documenting how the project will demonstrate compliance
triggers
percent complete
plan quality (Process)
invitation for bid (IFB)
15. Summary level project schedule that identifies the major deliverables and work breakdown structure components and key schedule milestones
actual cost (AC)
estimate activity resources (Process)
master schedule (Tool)
procurement documents (Output/Input)
16. Aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline
manage stakeholder expectations (Process)
close procurements (Process)
successor activity
determine budget (Process)
17. Modification that allows an acceleration of the successor activity.
lead (Technique)
distribute information (Process)
brainstorming (Technique)
constraint (Input)
18. A condition or situation favorable to the project - a positive set of circumstances - a positive set of events - a risk that will have a positive impact.
expert judgment (Technique)
stakeholder
Monte Carlo analysis
opportunity
19. Analytical technique to determine the essential features and relationships of components in the project management plan to establish a reserve for the schedule duration - budget - estimated cost or funds for a project
reserve analysis (Technique)
resource
perform quality control (Process)
work authorization system (Tool)
20. Documents utilized in bid and proposal activities - which include the buyer's invitation for bid - invitation for negotiations - request for information - request for quotation - request for proposal and sellers responses
objective
milestone
procurement documents (Output/Input)
resource breakdown structure
21. Buyer pays the seller a set amount (as defined by the contract) and the seller can earn an additional amount if the seller meets defined performance criteria
identify risks (Process)
progressive elaboration (Technique)
fixed price incentive fee contract (FPIF)
technique
22. Partially complete document in a predefined format that provides a defined structure for collecting - organizing and presenting information and data
template
sub phase
late finish date (LF)
reserve analysis (Technique)
23. Learning gained from the process of performing the project
lessons learned(Output/Input)
sponsor
template
risk avoidance (Technique)
24. Processes concerned with conducting risk management planning - identification - analysis - responses and monitoring and control on a project
develop human resource plan (Process)
influence diagram (Tool)
probability and impact matrix (Tool)
project risk management (Knowledge Area)
25. Project model that translates the uncertainties specified at a detailed level into the potential impact on objectives that are expressed at the level of the total project. Monte Carlo Analysis
lessons learned knowledge base
simulation
opportunity
voice of the customer
26. The acquirer of products - services or results for an organization
secondary risk
claim
expected monetary value (EMV)
buyer
27. Method of resolving the total variance in the set of scope - cost - and schedule variables into specific component variances that are associated with defined factors affecting scope - cost and schedule variables
variance analysis (Technique)
tool
project management team
backward pass
28. Risk response planning technique associated with threats that seeks to reduce the probability of occurrence or impact of a risk to below an acceptable threshold
forecast
risk mitigation (Technique)
actual cost of work performed
methodology
29. 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.
assumptions
defect
milestone schedule (Tool)
expected monetary value (EMV)
30. Type of procurement document used to request proposals from prospective sellers of products or services.
define scope (Process)
subproject
request for proposal (RFP)
scope creep
31. Processes involved in estimating - budgeting - and controlling costs so that the project can be completed within the approved budget
activity attributes (Output/Input)
start to finish (SF)
schedule baseline
project cost management (Knowledge Area)
32. Quantitative risk analysis and modeling technique used to determine which risks have the most potential impact on the project. typical display of results is in the form of a tornado diagram
budget at completion (BAC)
activity identifier
sensitivity analysis
project initiation
33. Collection of generally sequential project phases whose name and number are determined by the control needs of the organization involved in the project
technical performance measurement (Technique)
project management office (PMO)
change control system (Tool)
project life cycle
34. Approximating the number of work periods needed to complete individual activities with estimated resources
estimate activity durations (Process)
backward pass
project schedule (Output/Input)
program evaluation and review technique (PERT)
35. A collection of formal documented procedures that define how project deliverables and documentation will be controlled - changed and approved. in most application areas - the change control system is a subset of the configuration management system
execute
activity code
project quality management (Knowledge Area)
change control system (Tool)
36. Determining project stakeholder information needs and defining a communication approach
logical relationship
lessons learned knowledge base
authority
plan communications (Process)
37. Members of the project team who are directly involved in project management activities
buyer
statement of work (SOW)
manage project team (Process)
project management team
38. Total costs actually incurred and recorded in accomplishing work performed during a given time period for a schedule activity or work breakdown structure component. actual cost can sometimes be direct labor hours alone - direct costs alone - or all c
activity list (Output/Input)
successor activity
actual cost (AC)
precedence diagramming method (PDM) (Technique)
39. Reserve
assumptions analysis (Technique)
buffer
bottom-up estimating (Technique)
value engineering
40. Deliverable that is subject to approval by the project sponsor or customer
historical information
external deliverable
input (Process) input
contingency reserve(Output/Input)
41. The amount of funds - budget - or time needed above the estimate to reduce the risk of overruns of project objectives to a level acceptance to the organization
tool
lessons learned knowledge base
finish to finish (FF)
contingency reserve(Output/Input)
42. Degree - amount or volume of risk that an organization or individual will withstand
imposed date
risk register (Output/Input)
expert judgment (Technique)
risk tolerance
43. Subsystem of overall project management system. collection of formal documented procedures that defines how project work will be authorized to ensure that the work is done by the identified organization - at the right time and in the proper sequence.
work performance information
work authorization system (Tool)
project quality management (Knowledge Area)
project management process group
44. The process of defining and documenting stakeholder needs to meet project objectives
collect requirements (Process)
expected monetary value (EMV)
risk avoidance (Technique)
calendar unit
45. Analytical technique that uses three cost or duration estimates to represent optimistic - most likely and pessimistic scenarios.
network logic
variance
lessons learned(Output/Input)
three point estimate (Technique)
46. Those criteria - including performance requirements and essential conditions which must be met before project deliverables are accepted
project calendar
logical relationship
acceptance criteria
root cause analysis (Technique)
47. Requests to expand or reduce the project scope - modify policies - processes - plans or procedures - modify costs or budgets - or revise schedules
total float
claim
change requests
failure mode and effect analysis (FMEA) (Technique)
48. Indications that a risk has occurred or is about to occur. also called risk symptoms or warning signs. should be watched or monitored in the risk monitoring and control process.
triggers
requirement
human resource plan
to complete performance index (TCPI)
49. Judgment provided based upon expertise in an application area - knowledge area - discipline - industry - etc. as appropriate for the activity being performed.
determine budget (Process)
resource leveling (Technique)
expert judgment (Technique)
conduct procurements (Process)
50. A category of projects that have common components significant in such projects - but are not needed or present in all projects. application areas are usually defined in terms of either the product or the type of customer or industry sector
threshold
precedence relationship
application area
project management knowledge area