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. Dependencies determined by the Project Management Team; involve a relationship between project activities and non-project activities (i.e. - dependencies on issues that are beyond the scope of the project). These dependencies are outside the project






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






3. Process of documenting project purchasing decisions - specifying the approach - and identifying potential sellers.






4. Changing the project management plan to eliminate the threat entirely.






5. They possess a blend of functional and projectized characteristics. Weak matrices maintain many of the characteristics of a functional organization - and the Project Manager's role is more that of a coordinator or expediter than that of a manager. Si






6. Risk Audits examine and document the effectiveness of risk responses in dealing with identified risks and their root causes - as well as the effectiveness of the risk management process.






7. Involves setting a fixed total price for a defined product or service to be provided.






8. Descriptions of which resources will be available at what times and in what patterns necessary for schedule development






9. Terms used when the source selection decision will be based on price






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






11. A matrix that assigns risk ratings to risks or conditions based on a combining probability and impact scales. Risks with high probability and high impact will require further analysis.






12. Process of defining how to conduct risk management activities for a project.






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






14. The process of identifying all people or organizations impacted by the project and documenting relevant information regarding their interests - involvement - and impact on project success.






15. Collection of generally sequential project phases.






16. The expected total cost of a schedule activity - a work breakdown structure component - or the project when the defined scope of work will be completed.






17. Defines the procedures by which project scope can be changed; includes paperwork - tracking systems and approval levels necessary for authorizing changes.






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






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






20. Any modification to the agreed upon project scope as defined by the approved WBS






21. Describes the processes required to acquire goods and services from outside the project team. It includes planning procurements - conducting procurements - administering procurements - and closing procurements.






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






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






24. Formal written notice from a person or organization responsible for contract administration - informing that the contract has been completed.






25. Meetings held to assess project status and/or progress.






26. A collection of formal (note: not informal) documented procedures - which defines how the documentation and project deliverables will be managed - changed and approved.






27. A hierarchically organized depiction of the project organization arranged so as to relate the work packages to the performing organizational units.






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






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






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






31. Outcome of activities performed to accomplish the project.






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






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






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






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






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






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






38. A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it.






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






40. Seller prepared documents that describe the seller's ability and willingness to provide the requested product.






41. Activities specifically taken by management and team members to help individual team members work together effectively - thereby improving team performance






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






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






44. Reduce the probability and/or consequence of an adverse risk event to be within acceptable threshold limits.






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






46. Hybrid type of contractual agreements that contain aspects of both cost-reimbursable and fixed- price contracts. Some characteristics: · Open-ended - i.e. - full value of the agreement and the exact quantity of items to be delivered may not be define






47. If the performing organization does not have a formal contracting group - then the project team will have to supply both the resources and expertise to support procurement activities






48. Quantities to be performed for each specific category - and can be used to estimate activity durations






49. Process of monitoring the status of the project and product scope and managing changes to the scope baseline.






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