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 formal procedure for authorizing project work to ensure that work is done by the identified organization at the right time and in proper sequence.






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






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






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






5. A documented tabulation of schedule activities that shows the activity description - activity identifier - and a sufficiently detailed scope of work description so project team members understand what work is to be performed.






6. It can include correspondence - memos - meeting minutes - and documents describing the project.






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






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






9. It shortens the project schedule without changing the project scope - in order to meet schedule constraints - imposed dates - or other schedule objectives. -. This technique includes crashing and fast tracking.






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






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






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






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






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






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






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






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






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






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






20. It is a tool and technique which is used to determine the information needs of the project stakeholders. This is a key component for planning the project's actual communications. It would assist in determining and limiting who will communicate with w






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






22. The process of collecting and distributing performance information - including status reports - progress measurements - and forecasts to stakeholders.






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






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






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






26. Describes the processes required to ensure that the project is completed within the approved budget. It includes estimating the cost - determining the budget - and controlling the costs.






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






28. Document that formally authorizes a project. Provides project manager with the authority to apply organizational resources to project activities.






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






30. Describes the need - justification - requirements - and current boundaries for the project.






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






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






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






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






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






36. Responses to emerging risks that was previously unidentified or accepted. These were not planned in advance of the occurrence of the risk event.






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






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






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






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






41. A schedule compression technique in which phases or activities normally performed in sequence are performed in parallel. Fast tracking often results in rework and increased risk. Fast tracking only works if activities can be overlapped to shorten the






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






43. Features or services that characterize a product - result - or service






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






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






46. The work that must be done to deliver a product with the specified features and functions






47. Documented direction for executing the project work to bring expected future performance of the project work in line with the project management plan.






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






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






50. Structured method to guide the project team during development of project plan. Standard forms and templates or even complicated simulations may be used.







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests