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. Subdivision of project deliverables into smaller - more manageable components






2. Activities that assist in developing/enhancing the ability of team members to work together effectively and contribute to the success of the project team. It improves the people skills - technical competencies - and overall team environment and proje






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






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






5. Includes the processes that organize - manage - and lead the project team.






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






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






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






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






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






11. A deliverable is a unique - tangible and verifiable work/product. Each project phase is marked by the completion of one or more deliverables.






12. A technique for estimating that applies a weighted average of optimistic - pessimistic - and most likely estimates when there is uncertainty with the individual activity estimates.






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






14. Quantities to be performed for each specific category - and can be used to estimate activity durations






15. Meetings held to assess project status and/or progress.






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






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






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






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






20. Special category of revised cost estimates to an approved cost baseline.






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






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






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






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






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






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






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






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






29. Describes the procurement item in sufficient detail to allow prospective sellers to determine if they are capable of providing the products - services - or results.






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






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






32. Used to identify project and product requirements; some of the techniques used are: Brainstorming - Nominal group technique - The Delphi technique - Idea/mind mapping - and Affinity diagram.






33. Forecasts of potential project schedule and cost results listing the possible completion dates or project duration and costs with their associated confidence levels.






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






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






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






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






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






39. Collection of generally sequential project phases.






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






41. This compares technical accomplishments during project execution with the project management plan's schedule of technical achievement.






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






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






44. A management control point where the resource plans - scope - schedule and actual cost are integrated and compared to earned value for performance measurement.






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






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






47. Calculates the theoretical early start and finish dates - and late start and finish dates - for all activities without regard to any resource limitations. This is done by performing a forward and backward pass analysis through the schedule network.






48. Seeking to shift the consequences of the risk to a third party together with the ownership for the response.






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






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