Initiate and Plan - Memorization

Question 1

Project Charter

Answer 1

Document that formally authorizes the project.

Question 2

Assumption log

Answer 2

Used to record and track assumptions and constraints throughout the project.

Question 3

Performance measurement baseline

Answer 3

Combination of the scope, schedule and cost baseline used by the earned value management technique.

Question 4

Planning iterations

Answer 4

Establishes the project baselines and defines how the project will be managed.

Question 5

Assumptions

Answer 5

Factors that, although uncertain, are accepted as givens for planning purposes.

Question 6

Project baseline

Answer 6

Formally approved version of project objectives that may be used to assess project performance.

Question 7

Planning

Answer 7

Define, refine and formalize project objectives and establish the actions and approach required to pursue those objectives.

Question 8

Initiation

Answer 8

Authorize the project of phase and understand the project context, define a common vision and establish boundaries.

Question 9

Product overview statement

Answer 9

Statement that briefly summarize the project’s objectives, business need and acceptance criteria.

Question 10

Project management plan

Answer 10

Planning effort required to balance the different project management plan elements.

Question 11

Tolerance

Answer 11

Limits of decision-making authority levels for specific project targets and management levels.

Question 12

Governance framework

Answer 12

Establishes the set of procedures, rules, systems, relationships, decision-making authority levels, roles and responsibilities that will govern projects.

Question 13

Tailoring

Answer 13

Adapting the project management processes to the project’s needs, size, complexity, risk, importance, and environment.

Question 14

Vision

Answer 14

Early high-level understanding of the project’s objectives, outcomes, products or solutions.

Question 15

Subsidiary management plans

Answer 15

Project management elements used to define management rules for specific project management areas.

Question 16

Product box technique

Answer 16

Using the different sides of a physical box to record
potential users, user needs, key requirements to
address user needs, alternative products to
address user needs, reasons to fund the project
and existing constraints.

Question 17

Minimum viable product

Answer 17

Minimum set of requirements that must be developed to release a viable and valuable product.

Question 18

Kanban board

Answer 18

Board used to visualize the process flow and limit work in progress when adopting a flow-based agile.

Question 19

Release

Answer 19

Aggregates the features of multiple iterations and deploys them to end users.

Question 20

Incremental product development

Answer 20

Develops usable partial products.

Question 21

Product backlog preparation

Answer 21

Agile practice of creating a prioritized list of product requirements.

Question 22

Timeboxing

Answer 22

Limiting the time dedicated to project events (e.g., iterations and planning meetings).

Question 23

Iteration planning meeting

Answer 23

Agile event in which the team reviews the prioritized items in the product backlog to agree on what can be done in the upcoming iteration.

Question 24

Product review

Answer 24

Agile event in which the team inspects and adapts the emerging product as well as engages stakeholders.

Question 25

Iterative product development

Answer 25

Develop a partial version of the product and then expand that product version through repetitive, short-term development cycles.

Question 26

Retrospective

Answer 26

Agile event in which the team inspects and adapts the process.

Question 27

Disciplined agile

Answer 27

Principle-based framework that aggregates different agile practices and techniques used to scale agile to the organization.

Question 28

Scrumban

Answer 28

Hybrid framework that combines elements of Scrum and Kanban.

Question 29

Crystal methods

Answer 29

Family of agile methodologies with different levels of depth designed to suit projects with different sizes and criticality levels.

Question 30

Kanban

Answer 30

Method that reduces delivery cycles and improves workflow by limiting the work in progress to available capacity.

Question 31

Scrum

Answer 31

Lightweight product development framework based on empirical processes and founded on the principles of inspection, adaptation and transparency.

Question 32

Scaled agile framework

Answer 32

Knowledge base of agile software development, lean and system thinking practice and information that can be used to implement agile at the team, program, large solution or portfolio level.

Question 33

Empirical processes

Answer 33

Processes that may be adjusted with the acquired experience and knowledge.

Question 34

Large-scale scrum

Answer 34

Framework that extends the single-team scrum model to multiple cross-functional teams collaborating to create a common product.

Question 35

Agile

Answer 35

Broad term that refers to any concept, practice or framework that embeds the agile manifesto’s values and principles.

Question 36

Scrum of scrums

Answer 36

Scaled agile technique used to synchronize and integrate the work of several teams working on the same product.

Question 37

Predictive approach

Answer 37

Project approach by which work flows downward, like a waterfall, through linear and sequential phases.

Question 38

Product backlog refinement

Answer 38

Process of regularly updating the backlog, by removing, adding, disaggregating, estimating or updating items.

Question 39

Iterative approach

Answer 39

Project approach by which the product is developed through continuous cycles or iterations to maximize learning.

Question 40

Scrum events

Answer 40

Time-boxed ceremonies that sustain the Scrum process and provide an opportunity to inspect and adapt.

Question 41

Hybrid approach

Answer 41

Project approach that combines other project approaches.

Question 42

Scrum artifacts

Answer 42

Outputs of the Scrum framework that provide key project information to the Scrum team and other stakeholders, ensuring that performance is completely transparent.

Question 43

Incremental approach

Answer 43

Project approach by which product components may be developed in parallel and be integrated whenever they are built.

Question 44

Agile approach

Answer 44

Project approach by which the scope is vaguely defined at the beginning of the projects and each iteration or cycle may enhance or add components to the existing product version.

Question 45

Collaboration

Answer 45

Team members work closely throughout the project in an open environment and engage with key stakeholders to create a common sense of purpose.

Question 46

Feature-driven development

Answer 46

Software development agile approach focused on releasing valuable features repeatedly and frequently.

Question 47

Extreme programming

Answer 47

Software development agile approach designed to quickly respond to a very dynamic and uncertain environment based on core values and a holistic set of practices.

Question 48

Increment

Answer 48

Set of features deliveres at the end of the iteration.

Question 49

Self-organization

Answer 49

Teams are empowered to manage their own work instead of relying on the project manager direction.

Question 50

Iteration

Answer 50

Short fixed-duration period of time during which the team designs, develops, and tests features.

Question 51

Generalizing specialists

Answer 51

Team members that combine a deep specialization in their area of expertise with some experience and skills in other related areas.

Question 52

Timeboxes

Answer 52

Short, fixed-duration units of time.

Question 53

I-Shaped People

Answer 53

Team members with a deep specialization in their area of expertise but no experience and skills in other associated areas.

Question 54

Daily standup

Answer 54

Short term, time-boxed meeting to coordinate the team’s work, share information and provide transparency.