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. Describes the extent to which a risk is known or understood. Measures extent of data available as well as reliability of data.






2. Technique that explores the validity of assumptions basing on which every identified project risk is conceived and developed. It identifies risks to the project from inaccuracy - instability - inconsistency - or incompleteness of assumptions.






3. Process of implementing risk response plans - tracking identified risks - monitoring residual risks - identifying new risks - and evaluating risk process effectiveness throughout the project.






4. Process of assessing and combining the impact and the likelihood of identified risks. Prioritizes risks according to their potential effect on project objectives for further analysis or action.






5. Policies - guidelines and procedures that can help the project management team with various aspects of organizational planning.






6. Responses to emerging risks that was previously unidentified or accepted. These were not planned in advance of the occurrence of the risk event.






7. A schedule compression technique in which cost and schedule tradeoffs are analyzed to determine how to obtain the greatest amount of compression for the least incremental cost. Crashing only works for activities where additional resources will shorte






8. Forecasts of potential project schedule and cost results listing the possible completion dates or project duration and costs with their associated confidence levels.






9. Process to monitor the status of the project to update the project budget and manage changes to the cost baseline.






10. Broader view of Project Cost Management - whereby other than project costs - we consider the effect of project decisions on the cost of using the project's product.






11. Process of changing the schedule baseline. It is done when schedule delays are very severe - and the project schedule has to be completely changed.






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






13. Modifications to the cost estimation prepared for the project






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






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






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






17. A group of documented procedure used to apply technical and administrative direction and surveillance to: a) Identify and document the system's functional and physical characteristics; b)Control any changes to such characteristics; c) Record and repo






18. 1. Operations do not have any timelines. Projects are temporary and have finite time duration. 2. Operation's objective is usually to sustain the business. Project's objective is to achieve the target and close the project.






19. Schematic displays of the logical relationships (dependencies) among the project schedule activities; always drawn from left to right to reflect project work chronology






20. Activities that assist in developing/enhancing the ability of team members to work together effectively and contribute to the success of the project team. It improves the people skills - technical competencies - and overall team environment and proje






21. A documented list of project team members - their project roles - and communication information.






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






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






24. A modification of a logical relationship that allows an acceleration of the successor activity. A negative lead is equivalent to a positive lag.






25. Factors that - for planning purposes - will be considered true - real or certain.






26. The planned dates to perform schedule activities and the planned dates for meeting schedule milestones. Includes planned start and finish dates for the project's activities - milestones - work packages - planning packages - and control accounts. This






27. In a projectized organization - most of the organization's resources are involved in project work - and Project Managers have a great deal of independence and authority.






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






29. Allows for probabilistic treatment of both network logic and activity duration estimates






30. Describes the procurement item in sufficient detail to allow prospective sellers to determine if they are capable of providing the products - services - or results.






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






32. A formal - approved document used to define how the project is executed - controlled and monitored. It can either be at a detailed or high level and may contain one or more subsidiary plans.






33. A formal or informal approach to obtain information from stakeholders by talking to them directly






34. Documentation resulting from project activities. These files may also maintain records of other projects that are detailed enough to aid in developing cost estimates.






35. The process of analyzing activity sequences - durations - resource requirements - and schedule constrains to create the project schedule






36. Describes how the procurement processes (from developing procurement documentation through contract closure) will be managed






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






38. Any form of schedule network analysis in which scheduling decisions are driven by resource constraints.






39. Involves developing a better understanding of the product of the project






40. Collection of generally sequential project phases.






41. A structured review of the seller's progress to deliver project scope and quality - within cost and on schedule - as compared to the contract.






42. Features or services that characterize a product - result - or service






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






44. Bring together prequalified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product - service - or result






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






46. An accepted action performed to bring projected future project performance in line with the project plan. These actions have to be documented.






47. Includes identified risks - risk owners - results of Perform qualitative risk analysis process - agreed upon response strategies - etc.






48. Used to rate or score seller proposals






49. An uncertain event or condition that - if it occurs - has a positive or negative effect on the project objective.






50. Used to identify project and product requirements; some of the techniques used are: Brainstorming - Nominal group technique - The Delphi technique - Idea/mind mapping - and Affinity diagram.