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. The point at which an authority is granted.
Authorization
Agile Methods
Exception Plan
Fallback (risk response)
2. The procedure that ensures that all changes that may affect the project's agreed objectives are identified - assessed and either approved - rejected or deferred.
Change Control
Exception Assessment
Customer
Accept (Risk Response)
3. 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)
Approval
Exception
Baseline
Corporate or Program Standards
4. An off-specification that is accepted by the Project Board without corrective action.
End Stage Assessment
Concession
Communication Management Strategy
End Project Report
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.
Embedding (Prince2)
Closure Notification
Exception Plan
Center of Excellence
6. The restrictions or limitations that the project is bound by.
Exception Plan
Avoid (risk response)
Constraints
Customer's Quality Expectations
7. 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.
Approval
Benefit
Cost Tolerance
Approver
8. The right to allocate resources and make decisions (applies to project - stage - and team levels)
Benefit
Authority
Benefits Review Plan
Constraints
9. A team-level - time-driven review of progress.
Checkpoint Report
Checkpoint
Contingency
Agile Methods
10. 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.
Benefits Review Plan
Benefit
Dependencies (plan)
Exception Report
11. 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.
Communication Management Strategy
Closure Recommendation
Exception
Authority
12. The formal act of acknowledging that the project has met agreed acceptance criteria and thereby met the requirements of its stakeholders
Acceptance
Baseline
Baseline Management Product
Avoid (risk response)
13. 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.
Configuration Management Strategy
Benefit
Configuration Management System
Benefits Review Plan
14. 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.
Configuration Management
Closure Notification
Dis-benefit
Communication Management Strategy
15. 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
Embedding (Prince2)
Contingency
End Stage Report
Concession
16. The money allocated to the Change Authority available to be spent on authorized requests for change.
Activity
Change Authority
DSDM Atern
Change Budget
17. A description of how and by whom the project's products will be controlled and protected.
Configuration Management Strategy
Business Case
End Stage Assessment
Authority
18. A description of the means and frequency of communication between the project and the project stakeholders.
Cost Tolerance
Constraints
Communication Management Strategy
Checkpoint
19. 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.
Exception Plan
Assumption
Enhance (risk response)
Agile Methods
20. 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.
Exception Plan
Benefit
Authorization
Configuration Item
21. The person or group who commissioned the work and will benefit from the end results.
Fallback (risk response)
Checkpoint
Customer
Exception Report
22. 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
Deliverable
Acceptance
Accept (Risk Response)
Exception Plan
23. The measurable improvement resulting from an outcome perceived as an advantage by one or more stakeholders.
Closure Recommendation
Benefit
Daily Log
Acceptance
24. This is a review by the Project Board to approve (or reject) an Exception Plan.
Change Authority
Configuration Management System
Constraints
Exception Assessment
25. Principally - software development methods that apply the project approach of using short time-boxed iterations where products are incrementally developed. Prince2 is compatible with agile principles.
Agile Methods
Checkpoint Report
Dis-benefit
Customer's Quality Expectations
26. 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
Closure Notification
Concession
Authority
Benefits Review Plan
27. A record that describes the status - version and variant of a configuration item - and any details of important relationships between them.
Corporate or Program Standards
Avoid (risk response)
Configuration Item Record
Exception Report
28. A risk response to a threat where the threat either can no longer have an impact or can no longer happen
Configuration Item Record
Avoid (risk response)
Daily Log
Deliverable
29. An agile delivery framework developed and owned by the DSDM consortium. Atern uses a time-boxed and iterative approach to product development and is compatible with Prince2.
DSDM Atern
Approval
Baseline Management Product
Configuration Item Record
30. Technical and administrative activities concerned with the creation - maintenance and controlled change of configuration throughout the life of the product.
Configuration Management
Approver
Fallback (risk response)
Baseline
31. Used to record problems/concerns that can be handled by the Project Manager informally.
Exploit (risk response)
Acceptance Criteria
Daily Log
Constraints
32. A corporate coordinating function for portfolios - programs and projects providing standards - consistency of methods and processes - knowledge management - assurance and training.
Authority
Center of Excellence
Customer's Quality Expectations
Embedding (Prince2)
33. 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
Assurance
End Stage Report
Communication Management Strategy
Fallback (risk response)
34. The review by the Project Board and Project Manager of the End Stage Report to decide whether to approve the Stage Plan. According to the size and criticality of the project - the review may be formal or informal. The authority to process should be
End Stage Assessment
Exception Assessment
Accept (Risk Response)
Configuration Management Strategy
35. A statement that is taken as being true for the purposes of planning - but which could change later. An assumption is made where some facts are not yet known or decided - and is usually reserved for matters of such significance that - if they chan
Dis-benefit
Acceptance Criteria
Exception
Assumption
36. Reference levels against which an entity is monitored and controlled.
End Project Report
Benefit
Checkpoint
Baseline
37. The permissible deviation in the expected benefit that is allowed before the deviation needs to be escalated to the next level of management. Benefits tolerance is documented in the Business Case . See also 'tolerance'
Benefits Tolerance
Corporate or Program Standards
Daily Log
Executive
38. A set of actions to resolve a threat to a plan's tolerances or a defect in a product.
Corrective Action
Change Control
Benefits Review Plan
Exploit (risk response)
39. 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'.
Event-Driven Control
Cost Tolerance
Deliverable
Checkpoint
40. A type of management product that defines aspects of the project and - once approved - is subject to change control.
Exception Assessment
Avoid (risk response)
Baseline Management Product
End Stage Report
41. 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
Configuration Management Strategy
Acceptance Criteria
Authority
Center of Excellence
42. 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.
Accept (Risk Response)
Communication Management Strategy
End Stage Assessment
Fallback (risk response)
43. The justification for an organizational activity (project) - which typically contains costs - benefits - risks and time scales - and against which continuing viability is tested.
Avoid (risk response)
Business Case
Configuration Management
Acceptance
44. A statement about the quality expected from the project product - captured in the Project Product Description.
45. 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
Concession
Communication Management Strategy
Deliverable
Customer's Quality Expectations
46. The formal confirmation that a product is complete and meets its requirements (less any concessions) as defined by its Product Description.
Change Control
Authority
Baseline
Approval
47. 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.
Authorization
End Stage Report
Change Control
End Project Report
48. 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.
Contingency
Customer's Quality Expectations
End Project Report
Assurance
49. 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
Approval
Executive
Contingency
Checkpoint Report
50. The set of processes - tools and databases that are used to manage configuration data. Typically - a project will use the configuration management system of either the customer or supplier organization.
Contingency
Center of Excellence
Configuration Management System
Constraints