Test your basic knowledge |

Comptia Project + Project Management

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. Document containing the results of the qualitative risk analysis - quantitative risk analysis and risk response planning. details all identified risks including description - category - cause - probability of occurring - impact on objectives - propos






2. Identifying - documenting - approving or rejecting and controlling changes to the project baselines






3. 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.






4. 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






5. 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.






6. Type of procurement document used to request price quotations from prospective sellers of common or standard products or services






7. Documenting project purchasing decisions - specifying the approach and identifying potential sellers






8. The formally documented identification of a defect in a project component with a recommendation to either repair the defect or completely replace the component






9. Defining how to conduct risk management activities for a project






10. Requirements imposed by a government body. government mandated compliance






11. 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






12. Estimate of the amount of work that has been completed on an activity or a work breakdown structure component






13. 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






14. Process of numerically analyzing the effect of identified risks on overall project objectives






15. Significant point or event in the project






16. Request for proposal - but may have a narrower or more specific meaning






17. The process of prioritizing risks for further analysis or action by assessing and combining their probability of occurrence and impact






18. 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






19. 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






20. 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






21. Describes when and how human resource requirements will be met






22. Learning gained from the process of performing the project






23. Source of variation that is not inherent in the system - is not predictable - and it intermittent. also referred to as assignable cause.






24. 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






25. Deliverable oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables






26. Developing a document that formally authorizes a project or phase and documenting initial requirement that satisfy the stakeholders needs and expectations






27. Technique for estimating that applies a weighted average of optimistic - pessimistic and most likely estimates when there is uncertainty with the individual activity estimates






28. Modification that allows an acceleration of the successor activity.






29. Assumptions are factors that - for planning purposes - are considered to be true - real - or certain without proof or demonstration






30. 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






31. Change to project scope. almost always requires an adjustment to the project cost or schedule






32. 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






33. A table that links requirements to their origin and traces them throughout the project life cycle






34. Calendar of working days and non-working days that determines those dates on which each specific recourse is idle or can be active






35. Document that describes how procurement processes from developing procurement documentation through contract closure will be managed






36. Judgment provided based upon expertise in an application area - knowledge area - discipline - industry - etc. as appropriate for the activity being performed.






37. The earliest point in time on which the uncompleted portions of a schedule activity can start - based on the schedule network logic - the data date and any schedule constraints.






38. Information system consisting of tools and techniques to gather - integrate and disseminate the outputs of project management processes.






39. Documents and data on prior project including project files - records - correspondence - closed contracts - and closed projects






40. Store of historical information and lessons learned about both the outcomes of previous project selection decisions and previous project performance






41. Project schedule compression that changes network logic to overlap phases that would normally be done in sequence






42. The acquirer of products - services or results for an organization






43. Schedule network diagramming technique in which schedule activities are represented by boxes or nodes. schedule activities are graphically linked by one or more logical relationships to show the sequence in which the activities are performed






44. Summary level project schedule that identifies the major deliverables and work breakdown structure components and key schedule milestones






45. Assurance that a product - service or system meets the needs of the customer and other identified stakeholders






46. 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






47. Expected cost needed to complete all the remaining work for a schedule activity - work breakdown structure component or project.






48. Describes how the project management team will implement the performing organizations quality plan.






49. Analyzing activity sequences - durations - resource requirements and schedule constraints to create the project schedule






50. Slack - 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.