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. The process in which the estimated costs of individual activities or work packages are aggregated to establish an authorized cost baseline.






2. A documented list of project team members - their project roles - and communication information.






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






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






5. The document that sets out the format and establishes the activities and criteria for planning - structuring - and controlling the project costs. The cost management plan is contained in - or is a subsidiary plan of - the project management plan.






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






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






8. Used to solicit proposals from prospective sellers






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






10. Involves procedures required to close a contract as specified in the prescribed procedures for close procurements. Includes product verification and administrative closure.






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






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






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






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






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






16. Considers the characteristics of those prospective staff who are available to join the project team.






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






18. Any form of schedule network analysis in which scheduling decisions are driven by resource constraints.






19. Includes the processes that help to estimate - budget - and control costs - so that the project can be completed within the approved budget.






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






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






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






23. Process of obtaining seller responses - selecting a seller - and awarding a contract






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






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






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






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






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






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






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






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






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






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






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






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






36. Structured review of the project plans and assumptions - prior project files - contracts - and other information.






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






38. Action taken to bring a defective or nonconforming item into compliance with requirements or specifications. It is a frequent cause of project overruns in most application areas.






39. A subdivision (fragment) of a project schedule network diagram - used to illustrate or study some potential or proposed schedule condition - such as changes in preferential schedule logic or project scope.






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






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






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






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






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






45. An analytical technique used to determine the basic underlying reason that causes a variance or a defect or a risk. Root cause may underlie more than one variance or defect or risk. Root cause analysis is done as part of corrective action - Helps ide






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






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






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






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






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