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 acquirer of products - services or results for an organization






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






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






4. The value of work performed expressed in terms of the approved budget assigned to that work for a schedule activity or work breakdown structure component. ALSO BCWP.






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






6. Risk response planning technique that indicates the project team has decided not to change the project management plan to deal with a risk - or is unable to identify any other suitable response strategy






7. Processes and activities of the performing organization that determine quality policies - objectives and responsibilities so that the project will satisfy the needs for which it was undertaken






8. The merging or joining of parallel schedule network paths into the same node in a project schedule network diagram. characterized by a schedule activity with more than one predecessor activity






9. A general data gathering and creativity technique that can be used to identify risks - ideas or solutions to issues by using a group of team members or subject matter experts






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






11. Analytical technique to determine the essential features and relationships of components in the project management plan to establish a reserve for the schedule duration - budget - estimated cost or funds for a project






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






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






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






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






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






17. Expected cost needed to complete all the remaining work for a schedule activity - work breakdown structure component or project.






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






19. Aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline






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






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






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






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






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






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






26. Developing a detailed description of the project and product






27. Bar chart showing the amount of time that a resource is scheduled to work over a series of time periods.






28. Graphic display of schedule related information.






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






30. Skilled human resources - equipment - services - supplies - commodities - material - budgets or funds






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






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. Calculation of the early start and early finish dates for the uncompleted portions of all network activities






34. Identifying and documenting relationships among project activities






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






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. Those processes performed to complete the work defined in the project management plan to satisfy project objectives






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






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






40. Something toward which work is to be directed - a strategic position to be attained - or a purpose to be achieved - a result to be obtained - a product to produced or a service to be performed






41. The document that describes the communications needs and expectations for the project; how and in what format information will be communicated; when and where each communication will be made; wan who is responsible for providing each type of communic






42. Subdivision of a phase






43. Summary level schedule that identifies the major schedule milestone






44. Logical relationship where initiation of work of the successor activity depends on the completion of work of the predecessor activity






45. Hybrid contractual arrangement containing aspects of both cost reimbursable and fixed price contracts. time and material contract have no definitive end - can grow. units are preset by the buyer and seller.






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






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






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






49. Tracking - reviewing - regulating the progress to meet the performance objectives defined in the project management plan






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