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. Condition or capability that must be met or possessed by a system - product - service result or component to satisfy a contract - standard - specification or other formally imposed document.






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






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






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






5. Subdivision (fragment) of a project schedule network diagram - usually representing a subproject or work package.






6. Deliverable that is subject to approval by the project sponsor or customer






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






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






9. Depiction in a diagram format of the inputs - process actions - and outputs of one or more processes within a system






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






11. Identifying and documenting relationships among project activities






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






13. The smallest unit of time used in scheduling a project. calendar units are generally in hours - days - or weeks - but can also be in quarters years - months - shifts - or even minutes






14. A diagram that describes a decision under consideration and the implications of choosing one or another of the available alternatives. it is used when some future scenarios or outcomes of actions are uncertain. it incorporates probabilities and costs






15. Document describing how project risk management will be structured and performed on the project. contains the list of project risks - the results of risk analysis and risk responses






16. Processes required to manage the timely completion of a project






17. Degree - amount or volume of risk that an organization or individual will withstand






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






19. Information gathering technique examines the project from the perspective of each projects strengths - weaknesses - opportunities - and threats to increase the breadth of the risks considered by risk management






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






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






22. Form of progressive elaboration planning where the work to be accomplished in the near term is planned in detail at a low level of the work breakdown structure - while the work far in the future is planned at a relatively high level of the work break






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






24. Someone with management authority over an organizational unit within a functional organization.






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






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






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






28. Implementing risk response plans - tracking identified risks - monitoring residual risks - identifying new risks and evaluating risk process throughout the project






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






30. One of the defining points of a schedule network; a junction point joined to some or all of the other dependency lines






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






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






33. Processes required to ensure timely and appropriate generation - collection - distribution - storage - retrieval - and ultimate disposition of project information






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






35. Aggregation of the processes - tools - techniques - methodologies - resources and procedures to manage a project






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






37. The time in calendar units between the start and finish of a schedule activity






38. Analytical technique that uses three cost or duration estimates to represent optimistic - most likely and pessimistic scenarios.






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






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






41. Deliverable or project work component at the lowest level of each branch of the work breakdown structure






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






43. Requests to expand or reduce the project scope - modify policies - processes - plans or procedures - modify costs or budgets - or revise schedules






44. List of project team members - their project roles and communication information






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






46. Any numbering system used to uniquely identify each component of the work breakdown structure






47. Communicating and working with stakeholders to meet their needs and address issues as they occur






48. A point that is not settled or is under discussion or over which there are opposing views or disagreements






49. The expected total cost of a schedule activity - a work breakdown structure component or the project when the defined scope of work will be completed. Calculated based on performance to date or estimated by the project team based on other factors






50. A documented tabulation of schedule activities that shows the activity description - activity identifier - and a sufficiently detailed scope of work description so project team members understand what work is to be performed