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. The process of finalizing all activities across all of the project management process groups to formally complete the project or phase






2. Point in time that work was scheduled to start on a schedule activity. called planned start date.






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






4. Approved specific version of the detailed scope statement - work breakdown structure (WBS) and its associated WBS dictionary






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






6. Formally documented change request that is submitted for approval to the integrated change control process






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






8. Document that graphically depicts the project team members and their interrelationships for a specific project






9. Estimating the type and quantities of material - people - equipment or supplies required to perform the activity






10. Collection of projects or programs and other work that are grouped together to facilitate effective management of that work to meet strategic business objectives






11. Point in time associated with a schedule activities' start.






12. Logical relationship where completion of the successor schedule activity is dependent upon the initiation of the predecessor schedule activity






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






14. Developing a detailed description of the project and product






15. Fixed date imposed on a schedule activity or schedule milestone. usually - start no earlier than - finish no later than






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






17. Work that must be performed to deliver a product - service or result with the specified features and functions






18. A category of projects that have common components significant in such projects - but are not needed or present in all projects. application areas are usually defined in terms of either the product or the type of customer or industry sector






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






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






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






22. The process of obtaining seller responses - selecting a seller and awarding a contract






23. Document that specifies in a complete precise verifiable manner the requirements - design behavior or other characteristics of a system component - product - result or service






24. Subsystem of overall project management system. collection of formal documented procedures that defines how project work will be authorized to ensure that the work is done by the identified organization - at the right time and in the proper sequence.






25. Area of project management defined by its knowledge requirements and described in terms of its component processes - practices - inputs - outputs - tools and techniques






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






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






28. Processes and activities needed to identify - define - combine - unify and coordinate the various processes and project management activities within the project management process groups






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






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






31. Schedule activity that has a low total float.






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






33. Logical relationship where initiation of the work of the successor schedule activity depends upon the initiation of the work of the predecessor schedule activity






34. Performed to defined a new project or a new phase of an existing project by obtaining authorization to start the project or phase






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






36. Information and data on the status of the project schedule activities being performed to accomplish the project work collected as part of the direct and manage project execute processes. Information includes: status of deliverables - implementation s






37. Dependency between two project schedule activities or between project schedule activity and schedule milestone.






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






39. Documenting the actions necessary to define - prepare - integrate and coordinate all subsidiary plans






40. Budgeted cost of work performed






41. Defined function to be performed by a project team member






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






43. Specific version of the schedule model used to compare actual results to the plan to determine if preventive or corrective action is needed to meet the project objectives






44. Monitoring and recording results of executing the quality activities to assess performance and recommend necessary changes






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






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






47. Reserve






48. Making relevant information available to project stakeholders






49. Uncertain event or condition that has a positive or negative effect on projects objectives






50. A mutually binding agreement that obligates the seller to provide the specified product or service or result and obligates the buyer to pay for it