CAPM Domain 3: Agile Frameworks, Scrum, and Kanban

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/44

encourage image

There's no tags or description

Looks like no tags are added yet.

45 Terms

1
New cards

What is the Agile mindset?

A way of working that values adaptability, collaboration, customer feedback, and delivering useful outcomes in small increments.

2
New cards

What does 'responding to change' mean in Agile?

Evaluate the change, discuss its value, and prioritize it in the product backlog. Do not automatically disrupt work already underway.

3
New cards

What is a self-managing team?

A team that decides internally how to organize and complete its work while remaining accountable for delivering the agreed outcome.

4
New cards

What is the Scrum Master's role?

Support Scrum, coach the team, facilitate events when needed, and help remove impediments. The Scrum Master is not the team's boss.

5
New cards

What is the Product Owner's role?

Maximize product value by managing and ordering the Product Backlog and clarifying product priorities.

6
New cards

What do Developers do in Scrum?

Create a usable Increment each Sprint and decide how to turn selected backlog items into completed work.

7
New cards

What is the Daily Scrum for?

A brief daily event for Developers to inspect progress toward the Sprint Goal and adapt their plan for the next day.

8
New cards

What is the Sprint Review for?

Inspect the Sprint's outcome with stakeholders, gather feedback, and discuss adaptations to the product backlog.

9
New cards

What is the Sprint Retrospective for?

Inspect how the team worked and identify practical improvements to its process, collaboration, and effectiveness.

10
New cards

What is the Product Backlog?

The ordered, evolving list of work that may be needed to improve the product, including features, fixes, and other items.

11
New cards

What is the Sprint Backlog?

The Sprint Goal, selected Product Backlog items, and the Developers' plan for delivering them during the Sprint.

12
New cards

What is backlog refinement?

An ongoing activity to clarify, split, estimate, and reorder backlog items so they are understandable and ready for future selection.

13
New cards

What is the Definition of Done (DoD)?

A shared quality standard that an Increment must meet to be considered complete.

14
New cards

How are acceptance criteria different from the Definition of Done?

Acceptance criteria describe conditions a particular requirement or story must satisfy. The Definition of Done is the shared standard applied to all completed work.

15
New cards

What are story points?

A relative estimate of a backlog item's effort, complexity, and uncertainty—not a direct number of hours.

16
New cards

What is Planning Poker?

A collaborative estimation technique in which team members independently choose estimates, reveal them together, and discuss differences.

17
New cards

What is velocity?

The amount of work a team typically completes in a Sprint, often measured in story points; it can help forecast future work.

18
New cards

Why should velocity not be used to compare teams?

Teams use different estimation scales, work contexts, and definitions. Comparing their velocity can distort behavior and encourage gaming.

19
New cards

What is a spike?

A time-boxed research or experiment used to reduce uncertainty about a technical, product, or requirements question.

20
New cards

What is an MVP?

A Minimum Viable Product: the smallest usable product or version that can test an important assumption and generate meaningful feedback.

21
New cards

What is a Minimum Viable Product?

The smallest usable product or version that can test an important assumption and generate meaningful feedback.

22
New cards

What does a burndown chart show?

Work remaining over time, commonly across a Sprint or release.

23
New cards

What does a burnup chart show?

Work completed over time, often alongside total scope so scope changes are visible.

24
New cards

What does a Cumulative Flow Diagram (CFD) show?

The amount of work in different workflow states over time; widening bands can reveal bottlenecks or growing work in progress.

25
New cards

What is a Work-in-Progress (WIP) limit?

A cap on how many items may be in a workflow state at once, helping reduce multitasking and encourage finishing work.

26
New cards

What is the purpose of an Increment?

A usable, integrated piece of product value that meets the Definition of Done and builds on previous increments.

27
New cards

What is the Agile approach to customer feedback?

Seek feedback frequently, use it to learn, and adapt the product backlog and future work based on what is valuable.

28
New cards

What is the difference between iterative and incremental development?

Iterative development improves or refines a solution through repeated cycles. Incremental development delivers the solution in usable pieces.

29
New cards

What is a timebox?

A fixed duration for an activity or event; the work or discussion is constrained to that time.

30
New cards

What should a team do when it discovers it will not finish all Sprint work?

Keep focus on the Sprint Goal, collaborate, and discuss scope adjustments with the Product Owner; do not lower quality standards or hide the issue.

31
New cards

What is the best response when a stakeholder asks for a change during a Sprint?

Discuss the request with the Product Owner. The Product Owner can reprioritize the Product Backlog; protect the Sprint Goal and avoid casually adding work mid-Sprint.

32
New cards

What is the purpose of Kanban?

Visualize work, manage flow, limit work in progress, and improve delivery by identifying and reducing bottlenecks.

33
New cards

What is a Kanban board?

A visual representation of work moving through workflow stages, such as To Do, In Progress, and Done.

34
New cards

What is the difference between Scrum and Kanban?

Scrum organizes work into timeboxed Sprints with defined accountabilities and events. Kanban focuses on visualizing and managing continuous flow with WIP limits.

35
New cards

What is an Agile retrospective action item?

A specific, actionable improvement the team agrees to try, ideally with ownership and a way to check whether it helped.

36
New cards

What should a project manager consider when comparing Scrum teams by their story-point velocity?

Velocity is team-specific and based on each team's estimation scale and context; use it for that team's forecasting, not cross-team ranking.

37
New cards

When to use adaptive approach

Best used when requirements are subject to high level of uncertainty and volatility

Likely to change throughout the project

38
New cards

Organizational breakdown structure

a hierarchical representation of the project organization which illustrates the relationship between project activities and the organizational units that will perform those activities

39
New cards

Incremental vs Iterative

Iterative = REFINE

Repeatedly improve or revise what already exists.

Example: You build a basic website, get feedback, redesign the layout, improve the navigation, and refine it again.

Think: Same product, progressively better.

Incremental = ADD

Deliver the product in separate, usable pieces of functionality.

Example: You build a website with a working homepage first, then add a login system, then add online payments.

Think: More features or components with each delivery.

40
New cards

Stakeholder engagement process

1. Identify Stakeholders

2. Conduct Stakeholder Analysis

Determine Stakeholder Engagement and Communication Approach

4. Conduct Business Analysis Planning

5. Prepare for Transition to Future State

6. Manage Stakeholder Engagement and Communication

7. Assess Business Analysis Performance

41
New cards

Retrospectives

meetings scheduled on a regular basis or conducted when a body of work is completed, such as the conclusion of an iteration.

Retrospectives are most commonly used in adaptive life cycles

42
New cards

Tailoring

the deliberate adaptation of approach, governance, and processes to make them more suitable for the given environment and the work at hand

43
New cards

Lessons learned

meeting to discuss, analyze, and document feedback about completed project activities. They are typically conducted by teams that develop solutions using a predictive life cycle

44
New cards

Defining acceptance criteria

the process of obtaining agreement as to what would constitute proof that one or more aspects of a solution have been developed successfully

45
New cards

Validate requirements

is the process of checking that the requirements meet business goals and objectives

• The key benefit of this process is that it minimizes the risks of missing stakeholder expectations or delivering the wrong solution.