Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
127 Cards in this Set
- Front
- Back
What does agile refer to |
Behaviours, concepts, Frameworks and techniques |
|
What is the business case theme |
To establish mechanisms to judge whether the project is (and remains) desirable, viable and achievable as a means to support decision making in its (continued) investment. |
|
What is the organisation theme |
To define and establish the product's structure of accountability and responsibilities (the who?). |
|
What is the quality theme |
Define and implement the means by which the project will verify products that are fit for purpose. |
|
What is the plans theme |
To facilitate communication and control by defining the means of delivering the products (the where and how, by whom, and estimating the when and how much) |
|
What is the risk theme |
Identify, assess and control uncertainty and as a result, improve the ability of the project to succeed |
|
What is the change theme? |
To identify, assess and control any potential and approved changes to the project. Baselines |
|
What is the progress theme? |
The purpose of the program theme is to: Establish mechanisms to monitor and compare actual achievements against those planned Provide a forecast for the project subjectives and continued viability Control any unacceptable deviations? |
|
What are prince2 agile behaviors? |
Transparency Collaboration Rich communication Self-organization Exploration |
|
What are the prince2 principles? |
Continued business justification Learn from experience Defined roles and responsibilities Managed by stages Manage by exception Focus on products Tailor to suit the project |
|
What are the prince2 processes? |
Business case Organization Quality Plans Risk Change Progress |
|
What is the risk management procedure? |
Identify: context and risks Assess: estimate and value Plan Implement |
|
In Prince 2, what are changes identified as? |
Issues |
|
What are the prince 2 prcesses |
Starting up a project Directing a project Initiating a project Managing a stage boundaries Controlling a stage Managing product delivery Closing a project |
|
What is the purpose of starting up a project |
To ensure that the pre-requisites for initiating a project are in place by answering the question: Do we have a viable and worthwhile project? |
|
What is the purpose of directing a project? |
To enable the project board to be accountable for the projects success by making key decisions and exercising overall control while delegating day to day management of the project to the project manager. |
|
What is the purpose of controlling a stage |
To assign work to be done, monitor such work, deal with issues, report progress to the project board, and take corrective actions to ensure that the management stage remains within tolerance. |
|
What is the purpose of managing product delivery |
To control the link between the project manager and the team managers, by agreeing the requirements for acceptance, execution and delivery. |
|
What is the purpose of managing a stage boundary |
To enable the project manager to provide |
|
What is the purpose of managing a stage boundary |
To enable the project manager to provide the project board with sufficient information to be able to: Review the success of the current management stage Approve the next stage plan Review the updated project plan Confirm continued business justification and acceptability of the risks |
|
What is the purpose of closing a project |
To provide a fixed point at which acceptance of the project is confirmed, and to recognise that objectives dry or in the original PID have been achieved |
|
What documentation are products from starting up and initiating a project |
Project brief Business case Product project description Project initiation documentation |
|
How long is an agile scrum time box |
2-4 weeks |
|
Minimum length of a timebox |
1 day |
|
What is the maximum length of a timebox |
6 weeks |
|
What core practises make up the Kanban board |
Visualize Limit work in progress Manage the flow Making policies explicit Implement feedback loops Improve collaboratively, evolve experimentally |
|
|
Focus on products |
|
|
C |
|
|
D |
|
|
A |
|
|
A |
|
|
B |
|
|
A |
|
|
A |
|
|
A |
|
|
D |
|
|
D |
|
|
A |
|
|
D |
|
|
A |
|
|
C |
|
|
B |
|
|
C |
|
|
B |
|
|
C |
|
|
A |
|
|
B |
|
|
C |
|
|
D |
|
|
C |
|
|
C |
|
|
A |
|
|
B |
|
|
C |
|
|
D |
|
|
B |
|
|
D |
|
|
C |
|
|
A |
|
|
B |
|
|
B |
|
|
A |
|
|
A |
|
|
D |
|
|
A |
|
|
B |
|
|
A |
|
|
C |
|
|
D |
|
|
A |
|
|
D |
|
|
B |
|
|
C |
|
|
A |
|
|
D |
|
|
D |
|
|
A |
|
|
A |
|
|
C |
|
|
D |
|
|
A |
|
|
B |
|
|
D |
|
|
C |
|
|
D |
|
|
D |
|
|
A |
|
|
B |
|
|
C |
|
|
B |
|
|
B |
|
|
A |
|
|
B |
|
|
B |
|
|
C |
|
|
B |
|
|
C |
|
|
B |
|
|
C |
|
|
B |
|
|
D |
|
|
B |
|
|
C |
|
|
D |
|
|
C |
|
|
A |
|
|
C |
|
|
D |
|
|
A |
|
|
C |
|
|
B |
|
|
C |
|
|
A |
|
|
D |
|
|
D |
|
|
A |
|
|
D |
|
|
C |
|
|
D |
|
|
C |
|
|
B |
|
|
A |
|
|
B |
|
|
A |
|
|
B |
|
|
B |
|
|
C |