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






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






3. Activities should have a coding structure to allow sorting and/or extractions based on different attributes assigned to the activities.






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






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






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






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






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






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






10. Meetings that are regularly scheduled to exchange and analyze information about the project and its performance.






11. It is used to identify stakeholders that can provide information on detailed project and product requirements. It contains the following information regarding the identified stakeholders: identification information (name - designation - location - co






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






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






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






15. Process of defining and documenting stakeholders' needs to meet the project objectives






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






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






18. The process in which the estimated costs of individual activities or work packages are aggregated to establish an authorized cost baseline.






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






20. Measuring - examining and testing undertaken to determine whether results conform to requirements; also called reviews - product reviews - audits - and walkthroughs






21. Outcome of activities performed to accomplish the project.






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






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






24. Provides a documented basis for making future project decisions and for confirming or developing common understanding of the project scope among the stakeholders






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






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






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






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. Process of identifying the specific actions to be performed to produce the project deliverables.






30. Documents how requirements will be analyzed - documented - and managed throughout the project






31. A modification of a logical relationship that directs a delay in the successor activity.






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






33. Charts that are used to show positions and relationships in a graphical format.






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






35. The process of approximating the number of work periods needed to complete individual activities with estimated resources






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






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






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






39. Subdivision of project deliverables into smaller - more manageable components






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






41. The total amount of time that a schedule activity may be delayed from its early start without delaying the project finish date - or violating a schedule constraint. Calculated using the critical path method technique and determining the difference be






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






43. Factors which - for planning purposes - are considered to be true - real or certain.






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






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






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






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






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






49. A requirement imposed by a governmental body and its compliance is mandatory.






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