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. Directing - managing - performing and accomplishing the project work - providing the deliverables and providing work performance information






2. Quantitative risk analysis and modeling technique used to determine which risks have the most potential impact on the project. typical display of results is in the form of a tornado diagram






3. An artifact that is produced - is quantifiable and can be either an end item in itself or a component item






4. Processes and activities needed to identify - define - combine - unify and coordinate the various processes and project management activities within the project management process groups






5. Provider of products - services or results






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






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






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






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






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






11. Slack - Total amount of time that a schedule activity maybe delayed from its early start date without delaying the project finish date or violating a schedule constraint.






12. The earliest point in time on which the uncompleted portions of a schedule activity (or the project) can finish - based on the schedule network logic - the data date and any schedule constraints.






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






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






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






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






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






18. A method of estimating a component of work. the work is decomposed into more detail. an estimate is prepared of what is needed to meet the requirements of each of the lower - more detailed pieces of work - and these estimates are then aggregated into






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






20. Describes when and how human resource requirements will be met






21. Summary level schedule that identifies the major schedule milestone






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






23. Document that describes how procurement processes from developing procurement documentation through contract closure will be managed






24. Model used in conjunction with manual methods or project management software to perform schedule network analysis to generate the project schedule for use in managing the executing or a project






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






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






27. Collect project performance data with respect to a plan - produce performance measures and report and disseminate performance information






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






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






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






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






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






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






34. Document that specifies in a complete precise verifiable manner the requirements - design behavior or other characteristics of a system component - product - result or service






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






36. Centralized coordinated management of a program to achieve the program's strategic objectives and benefits






37. Total amount of time that a schedule activity maybe delayed from its early start date without delaying the project finish date or violating a schedule constraint.






38. An imperfection or deficiency in a project component where that component does not meet requirements or specifications and needs to be either repaired or replaced






39. Analysis. a statistical technique that calculates the average outcome when the future includes scenarios that may or may not happen. used in decision tree analysis.






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






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






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






43. Type of procurement document whereby the buyer requests a potential seller to provide various pieces of information related to a product or service or seller capability






44. Technique that computes or iterates the project cost or project schedule many times using input values selected at random from probability distributions of possible costs or durations - to calculate a distribution of total project costs or completion






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






46. Judgment provided based upon expertise in an application area - knowledge area - discipline - industry - etc. as appropriate for the activity being performed.






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






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






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






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