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. Identifying quality requirements and/or standards for the project and product and documenting how the project will demonstrate compliance
activity list (Output/Input)
risk management plan (Output/Input)
identify stakeholders (Process)
plan quality (Process)
2. Deliverable oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables
executing processes (Process Group)
lessons learned knowledge base
request for information (RFI)
work breakdown structure (WBS) (Output/Input)
3. 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
progressive elaboration (Technique)
simulation
risk breakdown structure (RBS)
data date
4. Model used in conjunction with manual methods or project management software to perform schedule network analysis to generate the project schedule for use in managing the executing or a project
special cause
schedule model (Tool)
strengths - weaknesses - opportunities - threats analysis (SWOT)
preventative action
5. Bar chart showing the amount of time that a resource is scheduled to work over a series of time periods.
specification limits
successor activity
project manager
resource histogram
6. The process of defining and documenting stakeholder needs to meet project objectives
collect requirements (Process)
network logic
risk register (Output/Input)
project management knowledge area
7. 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
calendar unit
risk avoidance (Technique)
slack
early finish date (EF)
8. Analytical procedure in which each potential failure mode in every component of a product is analyzed to determine its effect on the reliability of that component and - by itself or in combination with other possible failure modes - on the reliabilit
analogous estimating (Technique)
failure mode and effect analysis (FMEA) (Technique)
project management knowledge area
finish to start (FS)
9. Smaller portion of the overall project created when a project is subdivided by their logical relationship
network logic
plan communications (Process)
subproject
rolling wave planning (Technique)
10. An information gathering technique used as a way to reach a consensus of experts on a subject. experts on the subject participate in the technique anonymously. a facilitator uses a questionnaire to solicit ideas about the important project points rel
project human resource management (Knowledge Area)
Delphi technique (Technique)
manage project team (Process)
risk category
11. Total number of work periods required to complete a schedule activity or work breakdown structure component.
duration (DU or DUR)
project calendar
total float
stakeholder
12. Directing - managing - performing and accomplishing the project work - providing the deliverables and providing work performance information
strengths - weaknesses - opportunities - threats analysis (SWOT)
activity code
execute
master schedule (Tool)
13. An estimating technique that uses a statistical relationship between historical data and other variables (sq. foot in construction - lines of code in software development) to calculate an estimate for activity parameters such as scope - cost - budget
parametric estimating (Technique)
network logic
BCWP
time scaled schedule network diagram (Tool)
14. Total amount of time that a schedule activity maybe delayed from its early start date without delaying the project finish date or violating a schedule constraint.
baseline
historical information
total float
organizational breakdown structure (OBS) (Tool)
15. The date up to or through which the project's reporting system has provided actual status and accomplishments. also called as-of date and time-now date.
threat
data date
collect requirements (Process)
project human resource management (Knowledge Area)
16. Approved integrated scope-schedule-cost plan for the project work against which project execution is compared to measure and manage performance
plan procurements (Process)
sub network
performance measurement baseline
inspection (Technique)
17. Documents and presentations that provide organized and summarized work performance information - earned value management parameters and calculations - and analyses of project work progress and status
budget at completion (BAC)
organizational process assets (Output/Input)
performance reports (Output/Input)
executing processes (Process Group)
18. The approved estimate for the project or any work breakdown structure component or any schedule activity
early start date (ES)
project charter (Output/Input)
budget
claim
19. A method of estimating a component of work. the work is decomposed into more detail. an estimate is prepared of what is needed to meet the requirements of each of the lower - more detailed pieces of work - and these estimates are then aggregated into
bottom-up estimating (Technique)
activity attributes (Output/Input)
calendar unit
plan procurements (Process)
20. Calendar of working days or shifts that establishes those dates on which schedule activities are worked and nonworking days that determine those dates on which schedule activities are idle
threshold
project calendar
verify scope (Process)
schedule compression
21. Processes involved in estimating - budgeting - and controlling costs so that the project can be completed within the approved budget
project human resource management (Knowledge Area)
estimate activity durations (Process)
project cost management (Knowledge Area)
project schedule (Output/Input)
22. Hierarchically organized depiction of the project organization arranged so as to relate the work packages to the performing organizational units
conduct procurements (Process)
project management plan (Output/Input)
organizational breakdown structure (OBS) (Tool)
buffer
23. Sum of products - services and results to be provided as a project
scope
node
work breakdown structure component
defect repair
24. Requirements imposed by a government body. government mandated compliance
project scope management (Knowledge Area)
regulation
develop project team (Process)
identify stakeholders (Process)
25. Improving the competencies - team interaction - and the overall team environment to enhance project performance
expected monetary value (EMV)
defect repair
hammock activity
develop project team (Process)
26. Document describing how roles and responsibilities - reporting relationships and staffing management will be addressed and structured for the project
human resource plan
path divergence
requirement
identify risks (Process)
27. 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
risk management plan (Output/Input)
develop project management plan (Process)
data date
scope change
28. The process of completing each project procurement
perform quality control (Process)
close procurements (Process)
identify stakeholders (Process)
requested change(Output/Input)
29. Approach to optimize project life cycle costs - save time - increase profits - improve quality - expand market share - solve problems - and use resources more effectively
value engineering
finish to finish (FF)
budget
co-location (Technique)
30. The merging or joining of parallel schedule network paths into the same node in a project schedule network diagram. characterized by a schedule activity with more than one predecessor activity
plan communications (Process)
project scope management (Knowledge Area)
sub phase
path convergence
31. Developing a detailed description of the project and product
produce scope
human resource plan
program
define scope (Process)
32. Collection of schedule activity dependencies that makes up a project schedule network diagram
material
plan procurements (Process)
network logic
requested change(Output/Input)
33. Logical relationship where initiation of work of the successor activity depends on the completion of work of the predecessor activity
project team directory
project phase
finish to start (FS)
scope baseline
34. Term used in precedence diagramming method for a logical relationship in current usage. precedence relationship - logical relationship and dependency are interchangeably used
staffing management plan
technique
precedence relationship
project management team
35. Extending or generating parallel schedule network paths from the same node in a project schedule network diagram. characterized by schedule activity with more than one successor activity
path divergence
scope management plan(Output/Input)
preventative action
activity duration
36. Category or rank used to distinguish items that have the same functional use but do not share the same requirements for quality
project quality management (Knowledge Area)
project organization chart (Output/Input)
grade
start date
37. Hybrid contractual arrangement containing aspects of both cost reimbursable and fixed price contracts. time and material contract have no definitive end - can grow. units are preset by the buyer and seller.
time and material contract (T&M)
configuration management system (Tool)
project scope statement (Output/Input)
scope
38. Group of potential causes of risk. such as technical - external - organizational - environmental - project management. a category may include subcategories
validation
risk category
technique
project management team
39. 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
analogous estimating (Technique)
estimate activity durations (Process)
network logic
work breakdown structure (WBS) (Output/Input)
40. 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
estimate to complete (ETC)(Output/Input)
variance analysis (Technique)
risk mitigation (Technique)
administer procurements (Process)
41. Planning technique used to provide products - services and results that truly reflect customer requirements by translating those customer requirements into the appropriate technical requirements for each phase of project product development
voice of the customer
start to finish (SF)
develop project team (Process)
finish to start (FS)
42. 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
functional manager
quality management plan (Output/Input)
backward pass
specification limits
43. The expected total cost of a schedule activity - a work breakdown structure component or the project when the defined scope of work will be completed. Calculated based on performance to date or estimated by the project team based on other factors
influence diagram (Tool)
project manager
template
estimate at completion (EAC)(Output/Input)
44. A point in time associated with schedule activity's completion.
finish date
sub network
risk register (Output/Input)
performance reports (Output/Input)
45. Hierarchically organized depiction of the identified project risks arranged by risk category and subcategory that identifies the various areas and causes of potential risks.
risk breakdown structure (RBS)
summary activity
issue Point or matter in question or dispute
schedule performance index (SPI)
46. The enterprise whose personnel are directly involved in doing the work of the project
budget
virtual team
node
performing organization
47. Analytical technique that uses three cost or duration estimates to represent optimistic - most likely and pessimistic scenarios.
three point estimate (Technique)
project team directory
risk management plan (Output/Input)
predecessor activity
48. Subdivision (fragment) of a project schedule network diagram - usually representing a subproject or work package.
project procurement management (Knowledge Area)
execute
report performance (Process)
sub network
49. 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
fast tracking (Technique)
develop project charter (Process)
planning package
50. 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
estimate to complete (ETC)(Output/Input)
total float
Monte Carlo analysis
execute