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






2. Processes and procedures developed for the closing or canceling of projects.






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






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






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






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






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






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






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






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






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






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






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






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






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






16. Describes the processes required to ensure timely completion of the project. It includes defining activities - sequencing activities - estimating activity resources - estimating activity durations - developing the schedule - and controlling the sched






17. Factors that will limit the project management team's options (e.g. - a predefined budget)






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






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






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






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






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






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






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






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






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






27. Integrates scope - cost (or resource) - and schedule measures to help the project management team assess project performance.






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






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






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






31. Process of developing a detailed description of the project and product






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






33. A method of estimating a component of work. The work is decomposed into more detail. An estimate is prepared of what is needed to meet the requirements of each of the lower - more detailed pieces of work. These estimates are then aggregated into a to






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






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






36. The document that describes the communication needs and expectations for the project; how and in what format information will be communicated; when and where each communication will be made; and who is responsible for providing each type of communica






37. Process of managing procurement relationships - monitoring contract performance - ad making changes and corrections as needed.






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






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






40. Focused sessions that bring key cross-functional stakeholders together to define product requirements






41. Lists or files maintained with information on prospective sellers. These lists will generally have information on relevant past experience and other characteristics of the prospective sellers






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






43. Modifications to the cost estimation prepared for the project






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






45. Describes the processes required to make the most effective use of the people involved with the project. It includes developing the human resource plan - acquiring the project team - developing the project team - and managing the project team.






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






47. Projects are frequently divided into better manageable components or subprojects. Subprojects are often contracted to an external enterprise or another functional unit in the performing organization.






48. Judgment provided based upon expertise in an application area - knowledge area - discipline - industry - etc. as appropriate for the activity being performed. Such expertise may be provided by any group or person with specialized education - knowledg






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






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