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. 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.
Activity
Embedding (Prince2)
Closure Notification
Enhance (risk response)
2. An off-specification that is accepted by the Project Board without corrective action.
Customer
DSDM Atern
Concession
Cost Tolerance
3. 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
Center of Excellence
Corporate or Program Standards
Acceptance
Approver
4. 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
Assumption
Event-Driven Control
Benefit
Center of Excellence
5. 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.
End Project Report
Dependencies (plan)
Contingency
Exception Assessment
6. The justification for an organizational activity (project) - which typically contains costs - benefits - risks and time scales - and against which continuing viability is tested.
Benefits Review Plan
Approval
Business Case
Checkpoint
7. 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
Change Budget
End Stage Assessment
Cost Tolerance
Assumption
8. 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
Acceptance Criteria
Dependencies (plan)
Benefits Review Plan
Daily Log
9. 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)
Exception
Closure Recommendation
End Stage Report
Business Case
10. A team-level - time-driven review of progress.
DSDM Atern
Business Case
Acceptance
Checkpoint
11. 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.
Dependencies (plan)
Agile Methods
Acceptance Criteria
Change Authority
12. The measurable improvement resulting from an outcome perceived as an advantage by one or more stakeholders.
Agile Methods
Benefit
Fallback (risk response)
Deliverable
13. 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
Exception Assessment
End Stage Assessment
Contingency
Acceptance Criteria
14. 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.
Closure Recommendation
DSDM Atern
Accept (Risk Response)
Benefits Tolerance
15. 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
Corrective Action
Closure Notification
Customer's Quality Expectations
16. A record that describes the status - version and variant of a configuration item - and any details of important relationships between them.
End Stage Assessment
Configuration Item Record
Dis-benefit
Configuration Management
17. 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
Authorization
Contingency
Concession
Closure Notification
18. 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.
Configuration Item
Corrective Action
Executive
Corporate or Program Standards
19. A description of the means and frequency of communication between the project and the project stakeholders.
Benefit
Communication Management Strategy
Business Case
Customer's Quality Expectations
20. A risk response to an opportunity by seizing the opportunity to ensure that it will happen and that the impact will be realized.
Benefits Review Plan
Corporate or Program Standards
Exploit (risk response)
Exception Assessment
21. The right to allocate resources and make decisions (applies to project - stage - and team levels)
Accept (Risk Response)
Communication Management Strategy
Authority
Exploit (risk response)
22. 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
Exception
Closure Recommendation
Customer
23. This is a review by the Project Board to approve (or reject) an Exception Plan.
Event-Driven Control
Exception Assessment
Customer's Quality Expectations
Authorization
24. A set of actions to resolve a threat to a plan's tolerances or a defect in a product.
Change Control
Benefits Review Plan
Corrective Action
Exception Plan
25. The money allocated to the Change Authority available to be spent on authorized requests for change.
Change Budget
Accept (Risk Response)
Constraints
Benefits Review Plan
26. 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.
End Stage Assessment
Exception Plan
Assumption
Fallback (risk response)
27. 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.
End Stage Report
Approver
Daily Log
Dependencies (plan)
28. Technical and administrative activities concerned with the creation - maintenance and controlled change of configuration throughout the life of the product.
Configuration Management
End Stage Assessment
Change Budget
Customer's Quality Expectations
29. 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
Baseline
Executive
Fallback (risk response)
Constraints
30. The point at which an authority is granted.
Dependencies (plan)
Authorization
Closure Recommendation
Deliverable
31. 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.
Agile Methods
Corporate or Program Standards
Dis-benefit
Change Budget
32. 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.
Configuration Management System
End Stage Assessment
Customer's Quality Expectations
Customer
33. 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
Communication Management Strategy
Daily Log
Agile Methods
34. 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'.
Exception Report
Configuration Management
Cost Tolerance
Concession
35. Used to record problems/concerns that can be handled by the Project Manager informally.
Communication Management Strategy
Daily Log
Authorization
Customer
36. Reference levels against which an entity is monitored and controlled.
Change Budget
Baseline Management Product
Baseline
Deliverable
37. A corporate coordinating function for portfolios - programs and projects providing standards - consistency of methods and processes - knowledge management - assurance and training.
Executive
Benefits Review Plan
Change Budget
Center of Excellence
38. A description of how and by whom the project's products will be controlled and protected.
Closure Recommendation
Configuration Management Strategy
Accept (Risk Response)
DSDM Atern
39. 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.
Configuration Management
Dependencies (plan)
Change Budget
Change Authority
40. A risk response to a threat where the threat either can no longer have an impact or can no longer happen
Exception Plan
Avoid (risk response)
Change Budget
Agile Methods
41. The formal confirmation that a product is complete and meets its requirements (less any concessions) as defined by its Product Description.
End Project Report
Acceptance Criteria
Approval
Exception Assessment
42. 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.
DSDM Atern
Constraints
Exception Report
Benefits Tolerance
43. The person or group who commissioned the work and will benefit from the end results.
Daily Log
Customer
Enhance (risk response)
Center of Excellence
44. 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.
Approval
Change Authority
Concession
Benefits Review Plan
45. The restrictions or limitations that the project is bound by.
Business Case
Benefit
Constraints
Baseline Management Product
46. 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)
Acceptance
Event-Driven Control
Benefits Tolerance
47. 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.
Enhance (risk response)
Closure Recommendation
Configuration Management
Customer
48. The procedure that ensures that all changes that may affect the project's agreed objectives are identified - assessed and either approved - rejected or deferred.
Constraints
Change Control
End Stage Assessment
Exception
49. 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 Report
Dependencies (plan)
Exception Plan
End Stage Assessment
50. 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
End Stage Report
Accept (Risk Response)
Checkpoint Report
Approval