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. Graphic display of schedule related information.






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






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






4. The time in calendar units between the actual start date of the schedule activity and either the data date of the project schedule if the schedule activity is in progress or the actual finish date if the schedule activity is complete






5. Smaller portion of the overall project created when a project is subdivided by their logical relationship






6. Processes that organize and manage the project team






7. Process which generates hundreds or thousands of probable performance outcomes based on probability distributions for cost and schedule on individual tasks. the outcomes are used to generate a probability distribution for a project as a whole.






8. Schedule activity that follows a predecessor activity as determined by their logical relationship






9. The degree to which a set of inherent characteristics fulfills requirements






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






11. Specific type of management activity that contributes to the execution of a process and that may employ one or more techniques and tools






12. Making relevant information available to project stakeholders






13. Permission and direction to begin work on a specific schedule activity or work package or control account. sanctions project work to ensure that the work is done by the identified organization - at the right time - and in the proper sequence






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






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






16. Person or group that provides financial resources in cash or in kind for the project






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






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






19. Management methodology for integrating scope - schedule and resources and for objectively measuring project performance and progress. performance is measured by determining the budgeted cost of work performed (earned value) and comparing it to the ac






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






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






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






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






24. Centralized management of one or more portfolios - which includes identifying - prioritizing - authorizing - managing and controlling projects - programs and related work - to achieve specific strategic business objectives






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






26. Reserve






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






28. Group of persons with a shared objective who fulfill their roles with little or no time spent meeting fact to face.






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






30. A source of variation that is inherent in the system and predictable. on a control chart - it appears as part of the random process variation and is indicated by random pattern of points within the control limits. also referred to as random cause






31. Processes to purchase or acquire the products - services or results needed from outside the project team to perform the work






32. Group of related schedule activities aggregated at some summary level and displayed as a single activity at that summary level. same as summary activity.






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






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






35. Collection of schedule activity dependencies that makes up a project schedule network diagram






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






37. Graphical representation of situations showing causal influences - time ordering of events and other relationships among variables and outcomes






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






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






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






41. Formalizing acceptance of the completed project deliverables






42. Documenting project purchasing decisions - specifying the approach and identifying potential sellers






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






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






45. Document describing how roles and responsibilities - reporting relationships and staffing management will be addressed and structured for the project






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






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






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






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






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