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. Structure that relates the project organizational breakdown structure to the work breakdown structure to help ensure that each component of the project scope of work is assigned to a person or team
methodology
responsibility assignment matrix (RAM) (Tool)
progressive elaboration (Technique)
work performance information
2. Any continuous series of schedule activities connected with logical relationships in a project schedule network diagram
lead (Technique)
preventative action
network path
monitor and control risks (Process)
3. An artifact that is produced - is quantifiable and can be either an end item in itself or a component item
budget at completion (BAC)
schedule network analysis (Technique)
product
responsibility assignment matrix (RAM) (Tool)
4. Logical grouping of project management inputs - tools and techniques and outputs. includes initiating processes - planning processes - executing processes - monitoring and controlling processes and closing processes. NOT project phases
project management process group
hammock activity
reserve analysis (Technique)
project management team
5. 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
path convergence
residual risk
configuration management system (Tool)
network path
6. Any unique and verifiable product - result - or capability to perform a service that must be produced to complete a process - phase or project.
subproject
performing organization
deliverable (Output/Input)
product
7. Logical relationship where completion of the successor schedule activity is dependent upon the initiation of the predecessor schedule activity
early start date (ES)
start to finish (SF)
project phase
bottom-up estimating (Technique)
8. An organizational placement strategy where the project team members are physically located close to one another in order to improve communication - working relationships and productivity
scheduled start date (SS)
statement of work (SOW)
sub network
co-location (Technique)
9. 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
lessons learned knowledge base
manage stakeholder expectations (Process)
performance reports (Output/Input)
voice of the customer
10. Partially complete document in a predefined format that provides a defined structure for collecting - organizing and presenting information and data
activity identifier
plan communications (Process)
responsibility assignment matrix (RAM) (Tool)
template
11. Collection of logically related project activities - usually culminating in the completion of a major deliverable. project phase is a component of the project life cycle
work breakdown structure component
lead (Technique)
project phase
data date
12. Fixed date imposed on a schedule activity or schedule milestone. usually - start no earlier than - finish no later than
imposed date
closing processes (Process Group)
threat
project life cycle
13. Processes concerned with conducting risk management planning - identification - analysis - responses and monitoring and control on a project
project management
input (Process) input
sub network
project risk management (Knowledge Area)
14. One of the defining points of a schedule network; a junction point joined to some or all of the other dependency lines
input (Process) input
milestone
node
buyer
15. 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
change control system (Tool)
co-location (Technique)
sub network
precedence diagramming method (PDM) (Technique)
16. 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
procurement documents (Output/Input)
resource leveling (Technique)
estimate (Output/Input)
effort
17. Describes when and how human resource requirements will be met
start to finish (SF)
staffing management plan
total float
risk mitigation (Technique)
18. A change request that has been processed through the integrated change control process and approved
conduct procurements (Process)
approved change request (Output/Input)
near critical activity
estimate activity durations (Process)
19. Float (total float - free float)
slack
change requests
acceptance criteria
common cause
20. Risk that remains after risk responses have been implemented
residual risk
acceptance criteria
close project or phase (Process)
regulation
21. Processes to purchase or acquire the products - services or results needed from outside the project team to perform the work
project procurement management (Knowledge Area)
s-curve
develop project management plan (Process)
flowcharting (Technique)
22. Identifying quality requirements and/or standards for the project and product and documenting how the project will demonstrate compliance
plan quality (Process)
path convergence
historical information
forecast
23. System of practices - techniques - procedures and rules used by those who work in a discipline
path divergence
methodology
project management body of knowledge
responsibility assignment matrix (RAM) (Tool)
24. Identifying all people or organizations impacted by the project and documenting relevant information regarding their interest - involvement and impact on project success
external deliverable
functional organization
specification limits
identify stakeholders (Process)
25. Documenting project purchasing decisions - specifying the approach and identifying potential sellers
plan procurements (Process)
finish to finish (FF)
buyer
project management plan (Output/Input)
26. A formally constituted group of stakeholders responsible for reviewing - evaluating - approving - delaying or rejecting changes to a project - with all the decisions and recommendations being recorded
identify risks (Process)
imposed date
change control board (CCB)
manage project team (Process)
27. A table that links requirements to their origin and traces them throughout the project life cycle
time and material contract (T&M)
hammock activity
brainstorming (Technique)
requirements traceability matrix
28. Action taken to bring a defective or nonconforming component into compliance with requirements or specifications
project cost management (Knowledge Area)
claim
duration (DU or DUR)
rework
29. Assumptions are factors that - for planning purposes - are considered to be true - real - or certain without proof or demonstration
analogous estimating (Technique)
assumptions
manage project team (Process)
project communications management (Knowledge Area)
30. Group of related schedule activities aggregated at some summary level and displayed as a single activity (at the summary level)
close procurements (Process)
objective
summary activity
project management team
31. Making relevant information available to project stakeholders
distribute information (Process)
requirement
result
progressive elaboration (Technique)
32. 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
value engineering
early start date (ES)
objective
project calendar
33. Processes required to ensure that the project includes all the work required and only the work required to complete the project successfully
master schedule (Tool)
project scope management (Knowledge Area)
project life cycle
early finish date (EF)
34. The formally documented identification of a defect in a project component with a recommendation to either repair the defect or completely replace the component
reserve
defect repair
scope change
performing organization
35. ACWP
distribute information (Process)
network path
expert judgment (Technique)
actual cost of work performed
36. Point in time that work was scheduled to start on a schedule activity. called planned start date.
requirements traceability matrix
planned value (PV)
scheduled start date (SS)
closing processes (Process Group)
37. Determining project stakeholder information needs and defining a communication approach
plan communications (Process)
late finish date (LF)
constraint (Input)
perform quantitative analysis (Process)
38. Requirements imposed by a government body. government mandated compliance
sponsor
slack
regulation
estimate costs (Process)
39. Defining how to conduct risk management activities for a project
preventative action
finish to start (FS)
plan risk management (Process)
project scope statement (Output/Input)
40. Person or organization that is actively involved in the project or whose interests may be positively or negatively affected by execution or completion of the project
planned value (PV)
project charter (Output/Input)
stakeholder
rework
41. A point in time associated with schedule activity's completion.
initiating processes (Process Group)
monitor
finish date
firm fixed price contract (FFP)
42. Term used in precedence diagramming method for a logical relationship in current usage. precedence relationship - logical relationship and dependency are interchangeably used
schedule baseline
project management team
precedence relationship
project life cycle
43. Schematic display of the logical relationships among the project schedule activities. drawn from left to right.
role
project schedule network diagram (Output/Input)
probability and impact matrix (Tool)
portfolio
44. Monitoring and recording results of executing the quality activities to assess performance and recommend necessary changes
perform quality control (Process)
early finish date (EF)
duration (DU or DUR)
organizational breakdown structure (OBS) (Tool)
45. Approximating the number of work periods needed to complete individual activities with estimated resources
finish to start (FS)
scope creep
project charter (Output/Input)
estimate activity durations (Process)
46. Category or rank used to distinguish items that have the same functional use but do not share the same requirements for quality
grade
input (Process) input
projectized organization
influence diagram (Tool)
47. Analytical technique that uses mathematical models to forecast future outcomes based on historical results. it is a method of determining the variance from a baseline parameter by using prior progress reporting periods data and projecting how much th
subproject
trend analysis (Technique)
early finish date (EF)
variance
48. Group of persons with a shared objective who fulfill their roles with little or no time spent meeting fact to face.
virtual team
float
project risk management (Knowledge Area)
estimate activity durations (Process)
49. Members of the project team who are directly involved in project management activities
risk tolerance
performance reports (Output/Input)
project management team
flowcharting (Technique)
50. One or more numerical or text values that identify characteristics of the work or in some way categorize the schedule activity that allows filtering and ordering of activities within reports
output (Process)
planning package
activity code
BCWS