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. Documented direction to perform an activity that can reduce the probability of negative consequences associated with project risks
preventative action
project management team
distribute information (Process)
develop project team (Process)
2. Smaller portion of the overall project created when a project is subdivided by their logical relationship
pareto chart (Tool)
subproject
scope creep
role
3. Hierarchal structure of resources by resource category and resource type used in resource leveling schedules and to develop resource limited schedules and which may be used to identify and analyze project human resource management
historical information
project management knowledge area
resource breakdown structure
specification limits
4. 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
request for proposal (RFP)
risk management plan (Output/Input)
early start date (ES)
voice of the customer
5. Determining project stakeholder information needs and defining a communication approach
earned value (EV)
plan communications (Process)
develop human resource plan (Process)
tool
6. Dependency between two project schedule activities or between project schedule activity and schedule milestone.
quality management plan (Output/Input)
logical relationship
free float
performance reports (Output/Input)
7. Deliverable oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables
external deliverable
work breakdown structure (WBS) (Output/Input)
opportunity
project cost management (Knowledge Area)
8. 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
planned value (PV)
near critical activity
trend analysis (Technique)
procurement management plan (Output/Input)
9. Category or rank used to distinguish items that have the same functional use but do not share the same requirements for quality
project initiation management (Knowledge Area)
grade
strengths - weaknesses - opportunities - threats analysis (SWOT)
estimate activity resources (Process)
10. The process of prioritizing risks for further analysis or action by assessing and combining their probability of occurrence and impact
work authorization
effort
perform qualitative analysis (Process)
finish date
11. Expected cost needed to complete all the remaining work for a schedule activity - work breakdown structure component or project.
project time management (Knowledge Area)
issue Point or matter in question or dispute
node
estimate to complete (ETC)(Output/Input)
12. Risk response planning technique that indicates the project team has decided not to change the project management plan to deal with a risk - or is unable to identify any other suitable response strategy
preventative action
logical relationship
approved change request (Output/Input)
risk acceptance (Technique)
13. Process of numerically analyzing the effect of identified risks on overall project objectives
perform quantitative analysis (Process)
Monte Carlo simulation
virtual team
result
14. 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
near critical activity
progressive elaboration (Technique)
plan risk response (Process)
schedule performance index (SPI)
15. Adding features and functionality (project scope) without addressing the effects on time - costs - and resources or without customer approval
approved change request (Output/Input)
imposed date
scope creep
fast tracking (Technique)
16. Response to a negative risk that has occurred - workaround is not planned in advance of the occurrence of the risk event
project quality management (Knowledge Area)
regulation
workaround
schedule baseline
17. The right to apply project resources - expend funds - make decisions or give approvals
risk register (Output/Input)
rolling wave planning (Technique)
authority
start date
18. The process of obtaining seller responses - selecting a seller and awarding a contract
historical information
project management body of knowledge
baseline
conduct procurements (Process)
19. 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
schedule model (Tool)
perform qualitative analysis (Process)
calendar unit
time scaled schedule network diagram (Tool)
20. Inclusive term - describes the sum of knowledge within the profession of project management. includes proven traditional practices that are widely applied and innovative practices that are emerging.
input (Process) input
backward pass
project management body of knowledge
flowcharting (Technique)
21. An artifact that is produced - is quantifiable and can be either an end item in itself or a component item
triggers
define scope (Process)
product
workaround
22. Documents and data on prior project including project files - records - correspondence - closed contracts - and closed projects
estimate activity durations (Process)
workaround
historical information
threshold
23. Group of related schedule activities aggregated at some summary level and displayed as a single activity (at the summary level)
portfolio
work breakdown structure (WBS) (Output/Input)
summary activity
project initiation
24. A product - result or service generated by a process
claim
close project or phase (Process)
output (Process)
baseline
25. 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
buyer
procurement documents (Output/Input)
early finish date (EF)
scope change
26. An approved plan for a project - plus or minus approved changes. it is compared to actual performance to determine if performance is within acceptable variance thresholds. generally refers to the current baseline - but may refer to the original or so
objective
project management body of knowledge
project charter (Output/Input)
baseline
27. A formal approved document that defines how the project is executed - monitored - and controlled.
budget at completion (BAC)
project management plan (Output/Input)
pareto chart (Tool)
change control system (Tool)
28. Summary level project schedule that identifies the major deliverables and work breakdown structure components and key schedule milestones
scope creep
product
flowcharting (Technique)
master schedule (Tool)
29. A subsystem of the overall project management system. it is a collection of formal documented procedures used to apply technical and administrative direction and surveillance to identify and document the functional and physical characteristics of a p
configuration management system (Tool)
preventative action
technical performance measurement (Technique)
regulation
30. Document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organization resources to the project activities
buyer
sub phase
project charter (Output/Input)
acceptance criteria
31. Point in time associated with a schedule activities' start.
start date
objective
s-curve
data date
32. 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
buyer
performance reports (Output/Input)
fast tracking (Technique)
quality
33. Uncertain event or condition that has a positive or negative effect on projects objectives
risk register (Output/Input)
baseline
activity duration
risk
34. Aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline
Gantt chart (Tool)
project risk management (Knowledge Area)
determine budget (Process)
conduct procurements (Process)
35. 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
near critical activity
late finish date (LF)
schedule model (Tool)
activity
36. Management methodology for integrating scope - schedule and resources and for objectively measuring project performance and progress. performance is measured by determining the budgeted cost of work performed (earned value) and comparing it to the ac
validation
earned value management (EV
determine budget (Process)
regulation
37. Change to project scope. almost always requires an adjustment to the project cost or schedule
communications management plan (Output/Input)
scope change
calendar unit
statement of work (SOW)
38. Members of the project team who are directly involved in project management activities
project human resource management (Knowledge Area)
project management team
role
finish to finish (FF)
39. Identifying and documenting project roles - responsibilities - and required skills - reporting relationships and creating a staffing management plan.
tool
develop human resource plan (Process)
projectized organization
functional organization
40. 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.
time and material contract (T&M)
material
duration (DU or DUR)
threshold
41. Something tangible used in performing an activity to produce a product or result
schedule performance index (SPI)
tool
variance analysis (Technique)
imposed date
42. Application of knowledge - skills - tools and techniques to project activities to meet the project requirements
develop schedule (Process)
project management
duration (DU or DUR)
performing organization
43. Reviewing all change requests - approving changes - and managing changes to the deliverables - organizational process assets - project documents and project management plan
develop project team (Process)
stakeholder
perform integrated change control (Process)
product
44. Point in time that work was scheduled to finish on a schedule activity. called planned finish date
validation
change control system (Tool)
scheduled finish date (SF)
estimate to complete (ETC)(Output/Input)
45. Summary level schedule that identifies the major schedule milestone
early finish date (EF)
precedence diagramming method (PDM) (Technique)
milestone schedule (Tool)
produce scope
46. Document that establishes criteria and activities for developing and controlling the project schedule
early start date (ES)
resource calendar
schedule management plan (Output/Input)
estimate costs (Process)
47. Collection of schedule activity dependencies that makes up a project schedule network diagram
request for quotation (RFQ)
monitor
network logic
s-curve
48. 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
specification
work package
co-location (Technique)
role
49. Number of labor units required to complete a schedule activity or work breakdown structure component
project
develop project team (Process)
effort
opportunity
50. A component of work performed during the course of a project
functional organization
activity identifier
activity
plan quality (Process)