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