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. Involves procedures required to close a contract as specified in the prescribed procedures for close procurements. Includes product verification and administrative closure.






2. Process of monitoring the status of the project to update project progress and manage changes to the schedule baseline






3. A schedule network analysis technique used to determine the amount of scheduling flexibility on various logical network paths in the project schedule network - and to determine the minimum total project duration. Early start and finish dates are calc






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






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






6. Specify lessons that can be learned from each and every project - even from projects which are failures. They need to be documented. Most companies prefer post-implementation meetings and case studies to document Lessons Learned






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






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






9. A functional organization has a hierarchy in which every employee has one clear superior. Staff members are grouped by areas of specialization. Functional organizations may still have projects - but the perceived scope of the project is defined by th






10. Process of formalizing acceptance of the completed project deliverables






11. Predefined approaches to risk analysis and response in some organizations that have to be tailored to a particular project.






12. The policies - guidelines - or procedures that govern the recruitment of staff.






13. Helps to determine which risks have the most potential impact on the project. Examines the extent to which the uncertainty of each project element affects the objective being examined when all the other uncertain elements are held at their baseline v






14. An authorized time-phased budget at completion (BAC) used to measure - monitor - and control overall cost performance on the project. Developed as a summation of the approved budgets by time period and is typically displayed in the form of an S-curve






15. Describes the processes concerned with identifying - analyzing - and responding to project risk. It includes planning risk management - identifying risks - performing qualitative risk analysis - performing quantitative risk analysis - planning risk r






16. Provide a structure that ensures a comprehensive process of systematically identifying risks to a consistent level of detail and contributes to the effectiveness and quality of the Identify Risks process. They include categories like technical - exte






17. For many procurement items - the procuring organization may elect to either prepare its own independent estimate - or have an estimate of costs prepared by an outside professional estimator - to serve as a benchmark on proposed responses.






18. A subsequent phase of a project is sometimes begun prior to approval of the previous phase deliverables when the risks involved are deemed acceptable. This practice of overlapping phases is often called fast tracking






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






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






21. An authorized time-phased budget at completion (BAC) used to measure - monitor - and control overall cost performance on the project. Developed as a summation of the approved budgets by time period and is typically displayed in the form of an S-curve






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






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






24. The work that must be done to deliver a product with the specified features and functions






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






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






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






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. Structured method to guide the project team during development of project plan. Standard forms and templates or even complicated simulations may be used.






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






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






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






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






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






35. Describes the processes required to ensure timely and appropriate generation - collection - dissemination and ultimate disposition of project information. It includes identifying stakeholders - planning communication - distributing information - mana






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






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






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






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






40. This involves calculating the theoretical early and late start and finish dates for all project activities without regard to any resource pool restrictions.






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






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






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






44. Methods used to distribute information to team members and other stakeholders.






45. Involves immediate corrective or preventive action as a consequence of quality control measurements.






46. Generally used when considerations like technical approach and technical skills are paramount in source selection






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






48. Application of knowledge - skills - tools - and techniques to project activities to meet the project requirements.






49. Documents the characteristics of the product - result - or service which the project is undertaken to create.






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