SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
Prince2: Project Management In A Controlled Environment2
Start Test
Study First
Subjects
:
certifications
,
prince2
,
business-skills
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. Advice from the Project Board to inform all stakeholders and the host sites that the project resources can be disbanded and support services - such as space - equipment and access - demobilized. It should indicate a closure date for costs t the pr
Contingency
Approval
Exception
Closure Notification
2. This is plan that often follows an Exception Report. For a Stage Plan exception - it covers the period from the present to the end of the current stage - if the exception were at project level - the Project Plan would be replaced.
Executive
Exception Plan
Change Control
Configuration Item Record
3. A statement about the quality expected from the project product - captured in the Project Product Description.
Warning
: Invalid argument supplied for foreach() in
/var/www/html/basicversity.com/show_quiz.php
on line
183
4. A prioritized list of criteria that the project product must meet before the customer will accept it - i.e. measurable definitions of the attributes required for the set of products to be acceptable to key stakeholders
Closure Notification
Authorization
Agile Methods
Acceptance Criteria
5. What an organization needs to do to adopt Prince2 as its corporate project management method. See also - in contrast - 'tailoring' - which defines what a project needs to do to apply the method to a specific project environment.
Dependencies (plan)
Closure Recommendation
Configuration Management Strategy
Embedding (Prince2)
6. A risk response to a threat by putting in place a fallback plan for the actions that will be taken to reduce the impact of the threat should the risk occur.
Corporate or Program Standards
Business Case
Fallback (risk response)
Agile Methods
7. A risk response to an opportunity by seizing the opportunity to ensure that it will happen and that the impact will be realized.
Exploit (risk response)
Customer
Configuration Item
Assurance
8. The right to allocate resources and make decisions (applies to project - stage - and team levels)
Authority
Assurance
Communication Management Strategy
Approval
9. The point at which an authority is granted.
Embedding (Prince2)
Authorization
Change Authority
Acceptance Criteria
10. A description of the means and frequency of communication between the project and the project stakeholders.
DSDM Atern
Baseline Management Product
Communication Management Strategy
Checkpoint Report
11. The permissible deviation in a plan's cost that is allowed before the deviation needs to be escalated to the next level of management. Cost tolerance is documented in the respective plan. See also 'tolerance'.
Cost Tolerance
Checkpoint Report
Agile Methods
Configuration Management
12. All the systematic necessary to provide confidence that the target (system - process - organization - program - project - outcome - benefit - capability - product output - deliverable) is appropriate. Appropriateness might be defined subject
Daily Log
Executive
Assurance
Assumption
13. A description of how and by whom the project's products will be controlled and protected.
Exception Assessment
Agile Methods
Avoid (risk response)
Configuration Management Strategy
14. A set of actions to resolve a threat to a plan's tolerances or a defect in a product.
Checkpoint Report
Activity
Customer's Quality Expectations
Corrective Action
15. This is a review by the Project Board to approve (or reject) an Exception Plan.
Accept (Risk Response)
Exception Plan
Change Authority
Exception Assessment
16. The measurable improvement resulting from an outcome perceived as an advantage by one or more stakeholders.
Configuration Management Strategy
Benefits Review Plan
Benefit
Event-Driven Control
17. A report given by the Project Manager to the Project Board at the end of each management stage of the project. This provides information about the project performance during the stage and the project status at stage end.
Business Case
End Stage Report
Corporate or Program Standards
Authorization
18. The formal act of acknowledging that the project has met agreed acceptance criteria and thereby met the requirements of its stakeholders
Acceptance Criteria
Constraints
Acceptance
Closure Notification
19. A type of management product that defines aspects of the project and - once approved - is subject to change control.
Configuration Management System
Agile Methods
Center of Excellence
Baseline Management Product
20. A team-level - time-driven review of progress.
Change Budget
Deliverable
Embedding (Prince2)
Checkpoint
21. A risk response to an opportunity where proactive actions are taken to enhance both the probability of the event occurring and the impact of the event should it occur.
Enhance (risk response)
Change Budget
Deliverable
Constraints
22. The person or group who commissioned the work and will benefit from the end results.
Customer
Change Authority
Assumption
Benefits Tolerance
23. A plan that defines how and when a measurement of the achievement of the project's benefits can be made. If the project is being managed within a program - this information may be created and maintained at the program level.
Dis-benefit
Benefits Review Plan
Daily Log
Baseline
24. A person or group to which the Project Board may delegate responsibility for the consideration of requests for change or off-specifications. The Change Authority may be given a change budget and can approve changes within the budget.
Change Authority
Embedding (Prince2)
Avoid (risk response)
Executive
25. Used to record problems/concerns that can be handled by the Project Manager informally.
Enhance (risk response)
Benefit
Daily Log
Agile Methods
26. A situation where it can be forecast that there will be a deviation beyond the tolerance levels agreed between Project Manager and Project Board (or between Project Board and corporate or program management)
Benefit
Deliverable
Benefits Review Plan
Exception
27. A progress report of the information gathered at a checkpoint - which is given by a team to the Project Manager and which provides reporting data as defined in the Work Package
Customer
Assurance
Checkpoint Report
Business Case
28. The procedure that ensures that all changes that may affect the project's agreed objectives are identified - assessed and either approved - rejected or deferred.
Customer
Corrective Action
Change Control
Exception Plan
29. An off-specification that is accepted by the Project Board without corrective action.
Configuration Management System
Concession
Change Control
Activity
30. A risk response to a threat where the threat either can no longer have an impact or can no longer happen
Avoid (risk response)
Exploit (risk response)
Approval
Authorization
31. A record that describes the status - version and variant of a configuration item - and any details of important relationships between them.
Corrective Action
Checkpoint Report
Benefits Tolerance
Configuration Item Record
32. The person or group (e.g. a Project Board) who is identified and authorized to approve a (management or specialist) product as being complete and fit for purpose.
Customer
Baseline
Approver
Configuration Item
33. A description of the exception situation - its impact - options - recommendations and impact of the recommendation. This report is prepared by the Project Manager for the Project Board.
Exception Report
Checkpoint Report
Closure Recommendation
Exploit (risk response)
34. An entity that is subject to configuration management. The entity may be a component of a product - a product - or a set of products in a release.
Enhance (risk response)
DSDM Atern
Exception Assessment
Configuration Item
35. A tangible or intangible object produced as a result of the project that is intended to be delivered to a customer (either internal or external). A deliverable could be a report - a document - a server upgrade or any other building block of an over
Accept (Risk Response)
Change Control
End Stage Report
Deliverable
36. The single individual with overall responsibility that the project meets its objectives and delivers the projected benefits. This individual should ensure that the project maintains its business focus - that it has clear authority - and that the wo
Executive
Enhance (risk response)
Accept (Risk Response)
Baseline Management Product
37. A corporate coordinating function for portfolios - programs and projects providing standards - consistency of methods and processes - knowledge management - assurance and training.
Center of Excellence
Acceptance
Approver
Change Control
38. These are over-arching standards that the project must adhere to. They will influence the four project strategies ( Communication Management Strategy - Configuration Management Strategy - Quality Management Strategy and the Risk Management Strategy
Benefit
Concession
Business Case
Corporate or Program Standards
39. A process - function or task that occurs over time - has recognizable results and is managed. It is usually defined as part of a process or plan.
Approval
Activity
Communication Management Strategy
Dependencies (plan)
40. Something that is held in reserve typically to handle time and cost variances - or risks. Prince2 does not advocate the use of contingency because estimating variances are managed by setting tolerances - and risks are managed through appropriate ri
Authority
Contingency
Benefits Tolerance
Benefit
41. The relationship between products or activities. For example - the development of Product C cannot start until Products A and B have been completed. Dependencies can be internal or external. Internal dependencies are those under the control of the P
Dependencies (plan)
Acceptance
Baseline
Exploit (risk response)
42. Technical and administrative activities concerned with the creation - maintenance and controlled change of configuration throughout the life of the product.
Center of Excellence
Customer
Configuration Management
Enhance (risk response)
43. Reference levels against which an entity is monitored and controlled.
Benefits Tolerance
Baseline
Corrective Action
Configuration Item
44. A risk response to a threat where a conscious and deliberate decision is taken to retain the threat - having discerned that it is more economical to do so than to attempt a risk response action. The threat should continue to be monitored to ensure t
Configuration Item Record
Accept (Risk Response)
Dependencies (plan)
Configuration Item
45. An outcome that is perceived as negative by one or more stakeholders. It is an actual consequence of an activity whereas - by definition - a risk has some uncertainty about whether it will materialize.
Checkpoint Report
Benefit
Avoid (risk response)
Dis-benefit
46. A recommendation prepared by the Project Manager for the Project Board to send as a project closure notification when the board is satisfied that the project can be closed.
Checkpoint Report
Executive
Avoid (risk response)
Closure Recommendation
47. A report given by the Project Manger to the Project Board - that confirms the handover of all products and provides and updated Business Case and an assessment of how well the project has done against the original Project Initiation Documentation.
Configuration Management
End Project Report
Corporate or Program Standards
Customer's Quality Expectations
48. A control that takes place when a specific event occurs. This could be - for example - the end of a stage - the completion of the Project Initiation Documentation - or the creation of an Exception Report - it could also include organizational ev
Dependencies (plan)
End Stage Assessment
Avoid (risk response)
Event-Driven Control
49. The restrictions or limitations that the project is bound by.
Acceptance Criteria
Constraints
DSDM Atern
Corrective Action
50. The formal confirmation that a product is complete and meets its requirements (less any concessions) as defined by its Product Description.
Constraints
Exploit (risk response)
Approval
Configuration Management