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






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






3. Systematic process of planning - identifying - analyzing - responding - and monitoring and controlling project risk. It increases the probability and impact of positive events - and decrease the probability and impact of negative events in the projec






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






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






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. Involves payments (cost reimbursements) to the seller for all legitimate actual costs incurred for completed work - plus a fee representing seller profit






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






9. Process of redefining the cost performance/schedule/performance measurement/technical baseline. If cost variances are severe - re-baselining is needed to provide a realistic measure of performance.






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






11. Defines what kinds of competencies are required from what kind of individuals or groups and in what time frames.






12. Precedence Diagramming Method (PDM) includes four types of dependencies or relationships between activities: 1. Finish to Start; 2. Finish to Finish; 3. Start to Finish; 4. Start to Start






13. Approved modifications to the project schedule that are used to manage the project






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






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






16. Modifications to the cost estimation prepared for the project






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






18. Technologies or methods to transfer information among project stakeholders.






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






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. Describes how risk management will be structured and performed on the project.






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






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






24. The conclusion of a project phase is marked by a review of both key deliverables and project performance till date to determine if the project should continue into its next phase and detect and correct errors cost-effectively. These phase end reviews






25. The calculated projection of cost performance that must be achieved on the remaining work to meet a specified management goal - such as the budget at completion (BAC) or the estimate at completion (EAC). It is the ratio of 'remaining work' to the 'fu






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






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






28. Meetings with all prospective sellers and buyers prior to submittal of a bid or proposal. Used to ensure that all prospective sellers have a clear and common understanding of the procurement - and that no bidders receive preferential treatment.






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






30. A formal procedure for authorizing project work to ensure that work is done by the identified organization at the right time and in proper sequence.






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






32. Risks that remain after planned responses have been implemented - as well as those that have been deliberately accepted.






33. Records of previous project results that can be used to identify risks.






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






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






36. Also called risk symptoms or warning signs - they are indications that a risk has occurred or is about to occur. They may be discovered in the risk identification process and watched in the risk monitoring and control process.






37. It compares cost performance over time - schedule activities or work packages overrunning and under running the budget - and estimated funds needed to complete work in progress.






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






39. Describes how project scope will be managed and how scope changes will be integrated into the project. It should also include an assessment of the expected stability of the project scope






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






41. The amount of time that a schedule activity can be delayed without delaying the early start date of any immediately following schedule activities.






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






43. The process to identify and document project roles - responsibilities - and required skills - report relationships - and create a staffing management plan.






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






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






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






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






48. Estimating or predicting future project status and progress based on knowledge and information available at the time of forecasting.






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






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