Test your basic knowledge |

Subjects : certifications, capm
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. 1. Performed by people; 2. Constrained by limited resources; 3. Planned - excuted - monitored - and controlled; 4. Ultimate goal is to achieve organizational objectives or stratregic plans






2. They involve measuring value or attractiveness to the project owner. Includes considering the decision criteria and a means to calculate value under uncertainty.






3. Testing identified assumptions against two criteria: assumption stability and consequences on the project if the assumption is false.






4. Project team accepts the risk - i.e. team decides not to change the project plan to deal with the risk - or is unable to identify any other suitable response strategy.






5. A calendar of working days and non- working days that determines those dates on which each specific resource is ideal or can be active; typically defines the resource specific holidays and resource availability periods; the calendars that specify whe






6. Incurred for the exclusive benefit of the project (e.g. - salaries of full-time project staff).






7. Process of developing options and actions to enhance opportunities and to reduce threats to project objectives. Includes the identification and assignment of individuals to take responsibility for each agreed-to and funded risk response.






8. Structured method to guide the project team during development of project plan. Standard forms and templates or even complicated simulations may be used.






9. Process of identifying and documenting relationships among the project activities. Sequencing can be performed by using project management software or by using manual or automated techniques.






10. The total amount of time that a schedule activity may be delayed from its early start without delaying the project finish date - or violating a schedule constraint. Calculated using the critical path method technique and determining the difference be






11. Describes how individual requirements meet the business need for the project.






12. The process of making relevant information available to project stakeholders in a timely manner - as planned. Performed throughout the entire project life cycle and in all management processes.






13. Organize and summarize the information gathered - and present the results of any analysis as compared to the performance measurement baseline. Reports should provide status and progress of the project at the required level of detail.






14. Also known as "job shadowing -" it is usually done externally by the observer viewing the user performing her job.






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






16. A mathematical technique to forecast future outcomes based on historical results. This is performed using run charts.






17. Process of formally authorizing a new project or the next phase of an existing project; links the project to the ongoing work of the performing organization






18. A deliverable is a unique - tangible and verifiable work/product. Each project phase is marked by the completion of one or more deliverables.






19. Documented direction for executing the project work to bring expected future performance of the project work in line with the project management plan.






20. Description of the product of the project - provides important information about any technical issues or concerns that would need to be considered during procurement planning






21. A partially complete document in a predefined format that provides a defined structure for collecting - organizing - and presenting information and data.






22. Allow for non-sequential activities (e.g. Loops or Conditional Branches); e.g. - GERT(Graphical Evaluation and Review Technique) and System Dynamics






23. An estimating technique that uses a statistical relationship between historical data and other variables to calculate an estimate for activity parameters - such as scope - cost - budget - and duration. An example for the cost parameter is multiplying






24. This is done to take care of risks that were not identified in the risk response plan - or their impact on objectives is greater than expected.






25. Describes the processes required to ensure that the project includes only the essential work required to complete the project successfully. It includes collecting the requirements - defining the scope - verifying the scope and controlling the scope o






26. Process of identifying the specific actions to be performed to produce the project deliverables.






27. Document that formally authorizes a project. Provides project manager with the authority to apply organizational resources to project activities.






28. Complete set of indexed contract documentation - including the closed contract - that is prepared for inclusion with the final project files






29. Involves procedures required to close a contract as specified in the prescribed procedures for close procurements. Includes product verification and administrative closure.






30. The expected cost needed to complete all the remaining work for a schedule activity - work break down structure component - or the project.






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






32. It includes the processes required to ensure timely and appropriate generation - collection - dissemination - storage - retrieval - and ultimate disposition of project information.






33. A structure that relates the project organizational breakdown structure to the work breakdown structure to help ensure that each component of the project's scope of work is assigned to a person or team. It illustrates the connections between work pac






34. Collection of generally sequential project phases.






35. A requirement imposed by a governmental body and its compliance is mandatory.






36. Persons or organizations who are actively involved in the project or whose interests may be positively or negatively affected by the performance or completion of the project. They may also exert influence over the project - its deliverables - and the






37. Charts that are used to show positions and relationships in a graphical format.






38. Includes the processes required to purchase or acquire products - services - or results needed from outside the project team.






39. Special category of revised cost estimates to an approved cost baseline.






40. An estimating technique that uses the values of parameters - such as scope - cost - budget - and duration or measure of scale such as size - weight - and complexity - from a previous - similar activity as the basis for estimating the same parameter o






41. Repository that provides for collection - maintenance - and analysis of data gathered and used in the risk management process. Use of this database assists risk management throughout the organization and - over time - forms the basis of a risk lesson






42. It is used to identify stakeholders that can provide information on detailed project and product requirements. It contains the following information regarding the identified stakeholders: identification information (name - designation - location - co






43. A process of systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project. It identifies the interests - expectations - and influence of the stakehold






44. This compares technical accomplishments during project execution with the project management plan's schedule of technical achievement.






45. Activities should have a coding structure to allow sorting and/or extractions based on different attributes assigned to the activities.






46. Requests to expand or reduce project scope - modify policies/ processes/plans/procedures/costs and - if approved - can affect budgets or revise schedules. These change requests are processed through the Perform Integrated Change Control process.






47. Used to generate - classify - and prioritize product requirements. Some methods used to reach group decisions are: unanimity - majority - plurality - and dictatorship.






48. Project team must measure itself periodically against the expectations of those outside the project.






49. Deliverable- oriented grouping of project components that organizes and defines the total scope of the project - work not in the WBS is outside the scope of the project.






50. An estimating technique that uses parameters from a previous - similar project as the basis for estimating the same parameter/measure for a future project. Frequently used to estimate project duration when there is a limited amount of detailed inform