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. Point in time that work was scheduled to finish on a schedule activity. called planned finish date






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






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






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






6. Indications that a risk has occurred or is about to occur. also called risk symptoms or warning signs. should be watched or monitored in the risk monitoring and control process.






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






8. The right to apply project resources - expend funds - make decisions or give approvals






9. Processes concerned with conducting risk management planning - identification - analysis - responses and monitoring and control on a project






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






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






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






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






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






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






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






17. The person assigned by the performing organization to achieve the project objectives






18. Those criteria - including performance requirements and essential conditions which must be met before project deliverables are accepted






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






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






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






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






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






24. The latest possible point in time that a schedule activity may begin based upon the schedule network logic - the project completion date and any constraints assigned to schedule activities without violating schedule constraint or delaying project com






25. Number of labor units required to complete a schedule activity or work breakdown structure component






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






27. An information gathering technique used as a way to reach a consensus of experts on a subject. experts on the subject participate in the technique anonymously. a facilitator uses a questionnaire to solicit ideas about the important project points rel






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






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






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






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






32. Measure of schedule efficiency on a project. ratio of earned value (EV) and the planned value (PV). SV = EV minus PV.






33. Quantifiable deviation - departure or divergence away from a known baseline or expected value






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






35. Developing a detailed description of the project and product






36. Any of all process related assets - from any or all of the organizations involved in the project that are or can be used to influence the project's success. these process assets include formal or informal plans - policies - procedures and guidelines.






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






38. Collecting and distributing performance information - including status reports - progress measurements and forecasts






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






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






41. Formalizing acceptance of the completed project deliverables






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






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






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






45. Hierarchically organized depiction of the project organization arranged so as to relate the work packages to the performing organizational units






46. A product - result or service generated by a process






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






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






49. Adding features and functionality (project scope) without addressing the effects on time - costs - and resources or without customer approval






50. Action taken to bring a defective or nonconforming component into compliance with requirements or specifications