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. A point in time associated with schedule activity's completion.






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






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






4. Continuously improving and detailing a plan as more detailed and specific information and more accurate estimates become available as the project progresses and thereby producing more accurate and complete plans that result from the successive iterat






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






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






7. A subsystem of the overall project management system. it is a collection of formal documented procedures used to apply technical and administrative direction and surveillance to identify and document the functional and physical characteristics of a p






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






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






10. Any continuous series of schedule activities connected with logical relationships in a project schedule network diagram






11. Group of potential causes of risk. such as technical - external - organizational - environmental - project management. a category may include subcategories






12. System of practices - techniques - procedures and rules used by those who work in a discipline






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






14. Any of all external environmental factors and internal organizational environmental factors that surround or influence the projects success. these factors are from any or all of the enterprises involved in the project and include organizational cultu






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






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






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






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






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






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






21. Analytical procedure in which each potential failure mode in every component of a product is analyzed to determine its effect on the reliability of that component and - by itself or in combination with other possible failure modes - on the reliabilit






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






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






24. Identifying the specific actions to be performed to produce the project deliverables






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






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






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






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






29. Work breakdown structure component below the control account with known work content but without detailed schedule activities.






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






31. Structure in which the project manager has full authority to assign priorities - apply resources and direct the work of persons assigned to the project






32. Graphic display of cumulative costs - labor - hours - percentage of work or other quantities - plotted against time. used to depict planned value - earned value and active costs.






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






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






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






36. Features and functions that characterize a product - service or result






37. A specific technique for measuring the performance of work and used to establish the performance measurement baseline






38. Describes each component in the work breakdown structure (WBS). for each WBS component - the WBS dictionary includes a brief definition of the scope of statement of work - defined deliverables - a list of associated activities and list of milestones.






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






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






41. Developing a detailed description of the project and product






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






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






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






45. Any item - internal or external - that is required by a process before that process proceeds






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






47. Term used in precedence diagramming method for a logical relationship in current usage. precedence relationship - logical relationship and dependency are interchangeably used






48. Summary level schedule that identifies the major schedule milestone






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






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