Professional Scrum with Kanban level I PSK-I Real Questions

test2022-10-21T03:52:37+00:00

Are you looking for PSK-I exam questions for free? FreeTestShare Professional Scrum with Kanban level I PSK-I Real Questions will be very helpful for your preparation. The Professional Scrum with Kanban (PSK I) certification validates your knowledge of how Scrum Teams can use Scrum with Kanban to support value creation and delivery. By learning these PSK-I questions and answers, you will be able to understand the exam objectives of the actual exam. These sample questions help you to obtain a remarkable progress in your PSK-I exam preparation.

Now you may take this PSK-I practice test!

Page 1 of 4

1. Which flow metric is most helpful in indicating when multiple Product Backlog items can be completed? (choose the best answer)

Work Item Age.

Work in Progress (WIP).

Cycle Time.

Throughput.

2. True or False: When it comes to using Kanban for the Sprint Backlog, the Developers own the way they work as well as their Definition of "their" Workflow.

True

False

3. A team is using Kanban to improve the Sprint flow by visualizing and managing flow in the Sprint Backlog.

Which of the following would be most helpful to visualize?

Flow of tasks.

Flow of Product Backlog items.

Flow of Story Points.

Flow of invested effort.

Flow of only User Stories.

4. Which is the LEAST accurate description of Cycle Time? (choose the best answer)

The quantity/number of items that are delivered within a specified period of time.

The length of time a work item takes from idea stage to feedback from users after release to production.

The total amount of time an item is in a state/column.

The length of time from starting work on the item to when it is finished.

5. Work in Progress (WIP) is NOT considered a leading indicator for which of the following measures? (choose the best answer)

Number of Story Points completed.

Throughput.

Number of Product Backlog items finished in a Sprint.

Cycle time.

6. True or False: The Sprint length can be thought of as the team's batch size with Scrum Teams using Kanban.

Choose only ONE best answer.

TRUE

FALSE

7. Which of the following is true about Scrum Teams using Kanban? (choose the best answer)

It is most effective for product maintenance and support work.

Specified Scrum events are optional.

It encourages the Developers to use a phase based workflow.

It encourages collaboration within a team.

8. True or False: The Sprint Retrospective is the only time in which the Work in Progress (WIP) Limit can change.

TRUE

FALSE

9. Which formula best represents Little's Law? (choose the best answer)

Average Cycle Time = Average Work in Progress / Average Throughput.

Average Throughput = Average Cycle Time * Average Work in Progress.

Average Work in Progress = Average Cycle Time / Average Throughput.

Average Throughput = Average Cycle Time / Average Work in Progress.

10. True or False: If Developers use tasks, then their WIP limits should primarily apply to tasks in the Sprint Backlog.

True

False

Page 2 of 4

11. True or False: Work Item Age is a leading indicator for the length of the Scrum Team’s feedback loop for that (in progress) item.

True

False

12. A Scrum Team, that is new to Kanban, asks for your advise on how to start with increasing predictability.

What would be the most appropriate response? (choose the best answer)

Ask the team to begin inspecting and adapting the Product Backlog during the Sprint Review.

Have the team create a CFD, Control Chart and Aging chart to improve transparency.

Setup a Kanban board for them to visualize the workflow.

Teach them about Work in Progress (WIP) Limits and have them reduce the amount of work in progress.

13. Which of the following is the best use of a Work Item Age chart? (Choose the best answer)

To warn the team of when WIP Limits are about to be exceeded.

To show the average age of work in process.

To show the WIP Limit policy age.

To show how long ago an item on the Kanban board has it been pulled into WI

14. Which of the following will help a Scrum Team achieve flow optimization? (choose the best 4 answers)

Padding estimates to allow space in the Sprint Backlog.

Limiting WI

Visualization of the workflow

Inspecting and adapting their definition of "Workflow".

Active management of work items in progress.

15. Which of the following is NOT a metric of flow for Scrum Teams using Kanban? (choose the best answer)

Cycle Time.

Work in Progress (WIP).

Throughput.

Work Item Age.

All of the above are flow metrics.

16. An existing Scrum Team wants to apply Kanban practices.

What can the team start doing get begin achieving flow? (choose the best 4 answers)

Ensuring the product backlog is refined frequently.

Limiting Work in Progress (WIP).

Visualizing their workflow.

Actively managing WI

Inspecting & adapting their workflow.

17. How does Kanban support empiricism? (choose the best two answers)

The Kanban board provides transparency that helps the Scrum Teams inspect and adapt their process.

The Product Owner uses Kanban metrics to inspect the Throughput and adapt the Developers' Cycle Time accordingly.

Kanban prescribes specific practices that reduces the need for empiricism.

Kanban brings more rapid transparency about the product by enhancing and expanding the practices of Scrum. This enables a more effective inspection and adaptation loop.

18. Which of the following is NOT true about cycle time when applied to Scrum? (choose the best answer)

Cycle time should be the same length as the Sprint time-box.

Cycle time for some Product Backlog items might be longer than the Sprint time-box.

Average cycle time should be shorter than a Sprint time-box.

19. For teams practicing Scrum with Kanban, which of the following can provide the most appropriate metrics for inspecting their flow? (choose the best answer)

Control Chart. Cumulative Flow Diagram (CFD) and Aging Work in Progress (Aging Chart).

Story points and past velocity.

User stories and t-shirt size.

All of the answers.

None of these are Kanban for Scrum Teams metrics.

20. Which three statements best describe a Scrum Team's definition of "Workflow"? (choose the best 3 answers)

It helps management track a work item's percentage of completeness.

It provides a common understanding of when the Scrum Team considers work to be started and finished.

It describes how value flows through the system.

It creates transparency over policies related to Work in Progress (WIP) Limits.

It is used as a check off list for state that each work item must go through before it is considered 'done'.

It provides policies that create quality gateways between development handoff phases.

Page 3 of 4

21. Which of the following are considered lagging indicators? (choose the best three answers)

Work Item Aging metrics.

Throughput metrics.

Cycle Time metrics.

Work in Progress metrics.

Velocity metrics.

22. Kanban can help enhance visibility for: (choose the best three answers)

The Definition of Done.

The Sprint Backlog.

The Product Backlog.

The Sprint Retrospective.

23. The goal of the WIP Limit is to:

increase the utilization rate of the Developers.

reduce the amount of actual work in process.

maximize the amount of actual work in process.

allow the team to release multiple times per Sprint.

make it easier for the Scrum Master to manage the tasks.

24. True or False: 'On-demand' work item place holders are used in place of Sprint Goals for Scrum Teams using Kanban. Choose only ONE best answer.

B. TRUE

C. FALSE

25. If new urgent work emerges during the Sprint, who must change the Work in Progress (WIP) Limits in the team’s definition of "Workflow"? (choose the best answer)

The Product Owner.

Work in Progress (WIP) Limits cannot be changed during a Sprint.

The Scrum Master.

No one. New urgent work is not a valid reason to change Work in Progress (WIP) Limits.

The Developers.

26. Which is the best description of probabilistic forecast? (choose the best answer)

A forecast based on empirical data as an input on the likelihood of achieving a goal given certain time period.

A formula that calculates a team's future performance.

A commitment of when a specific scope will be finished.

27. True or False: The Service Level Expectations (SLE) is an agreement created during the Sprint Planning as a commitment to deliver certain work items by specified dates.

TRUE

FALSE

28. The basic metrics of flow that Scrum Teams using Kanban will need to track are: (choose the four best answers)

Lead Time

Velocity

Work in Progress (WIP)

Cycle Time

Throughput

Work Item Age

29. Which of the following will a Scrum Team most likely use as an input to Sprint Planning? (choose the best answer)

Throughput.

Work in Progress (WIP).

Work Item Age.

Service Level Expectation (SLE).

30. What can occur if you were to reduce batch sizes? (Choose all that apply)

Improved efficiency due to faster feedback loops.

Higher motivation due to seeing your work get done and deliver value earlier.

Lower efficiency due to overhead / transaction costs in case the batch size is too small.

Highlight a need to work to improve processes/infrastructure to reduce the pain of frequent costly overhead.

Page 4 of 4

31. True or False: A positive side effect of limiting WIP is that it creates a "pull system".

TRUE

FALSE

32. True or False: Scrum Events, Scrum Team Accountabilities, and Scrum Artifacts are changed when using Scrum with Kanban. For example, the Scrum Team might choose to omit the Sprint Retrospective when using Kanban with Scrum.

True

False

33. True or False: The WIP Limit can only be changed during the Sprint Retrospective.

True

False

34. Workflow can be thought of as the Scrum Team's policy for which of the following? (choose the best answer)

Defining when development is complete and validation begins.

How to get work done.

How to increase the Team's WIP limit.

What completed work looks like.

35. In the context of Kanban, which statement best describes flow? (choose the best answer)

An undesirable effect of too much work being present in the system.

A software development technique.

The movement of customer value throughout the product development system.

The movement of tasks between workflow stages.