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. Aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline






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






3. Organizational body or entity assigned various responsibilities related to the centralized and coordinated management of those projects under its domain.






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






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






6. Shortening the project schedule duration without reducing the project scope






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






8. Sum of products - services and results to be provided as a project






9. The approved estimate for the project or any work breakdown structure component or any schedule activity






10. Collection of generally sequential project phases whose name and number are determined by the control needs of the organization involved in the project






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






12. A short unique numeric or text identification assigned to each schedule activity to differentiate that project activity from other project activities. typically unique within any one project schedule network diagram






13. Schematic display of the logical relationships among the project schedule activities. drawn from left to right.






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






15. Temporary endeavor undertaken to create a unique product - service or result






16. Defined systematic procedure employed by a human resource to perform an activity to produce a product or result or deliver a service that may employ one or more tools






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






18. Response to a negative risk that has occurred - workaround is not planned in advance of the occurrence of the risk event






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






20. The aggregate of things used by an organization in any undertaking such as equipment - apparatus - tools - machinery - gear - material.






21. The area on either side of the centerline - or mean - of data plotted on a control chart that meets the customer's requirements for a product or service.






22. A technique that explores the accuracy of assumptions and identifies risks to the project from inaccuracy - inconsistency - or incompleteness of assumptions






23. A formal approved document that defines how the project is executed - monitored - and controlled.






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






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






26. Provider of products - services or results






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






28. The process of defining and documenting stakeholder needs to meet project objectives






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






30. Document that establishes criteria and activities for developing and controlling the project schedule






31. Total number of work periods required to complete a schedule activity or work breakdown structure component.






32. Learning gained from the process of performing the project






33. Structure in which the project manager shares responsibility with the functional managers for assigning priorities and directing the work of persons assigned to the project






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






35. Developing an approximation of the monetary resources needed to complete project activities






36. A group of related projects managed in a coordinated way to obtain benefits and control not available from managing them individually.






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






38. Schedule activity that determines when the logical successor activity can begin or end






39. Documented direction to perform an activity that can reduce the probability of negative consequences associated with project risks






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






41. Determining project stakeholder information needs and defining a communication approach






42. Category or rank used to distinguish items that have the same functional use but do not share the same requirements for quality






43. The degree to which a set of inherent characteristics fulfills requirements






44. Group of related schedule activities aggregated at some summary level and displayed as a single activity (at the summary level)






45. Partially complete document in a predefined format that provides a defined structure for collecting - organizing and presenting information and data






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






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






48. Formalizing acceptance of the completed project deliverables






49. Modification of a logical relationship that directs a delay in the successor activity. activity with a 10 day lag - cannot start until 10 days after an activity is finished






50. The process of confirming human resource availability and obtaining team necessary to complete project assignments