
PSK-I PDF問題集で2025年05月17日最近更新された問題
PSK-I試験問題有効なPSK-I問題集PDF
質問 # 28
Who is in the best position to decide if Kanban may be a valuable complementary practice for a Scrum Team?
(choose the best answer)
- A. The Developers.
- B. The Scrum Team.
- C. The Product Owner
- D. The Scrum Master.
- E. Stakeholders
正解:B
解説:
The decision on whether Kanban is a beneficial complement to Scrum lies with the entire Scrum Team. This includes the Product Owner, Scrum Master, and Developers, who collaboratively evaluate their workflow and decide if Kanban practices would improve flow and meet their specific needs. This is not the responsibility of a single role but a collective decision for effective self-management and ownership.
質問 # 29
What are the benefits of having early, frequent, and consistent feedback loops? (choose the best answer)
- A. Increased customer satisfaction.
- B. Identifying and addressing problems early.
- C. All of the above.
- D. Improved workflows.
正解:C
質問 # 30
Which statements best describe the purpose of a Scrum Team's Definition of Workflow?
(Choose the best three answers)
- A. It is used as a checklist of all the states that every work item should go through before it is considered to be done.
- B. It helps Service Request Manager track the percent completeness of a work item.
- C. It provides a mutual understanding of when the work is considered to be started and finished.
- D. It makes handoff policies explicit by defining clear quality gates between the development stages.
- E. It creates transparency over the Work in Progress (WIP) limiting rules.
- F. It defines how value flows through the system.
正解:C、E、F
解説:
The Definition of Workflow clarifies how value moves through the system, establishes a shared understanding of when work items are considered to be in progress and completed, and enhances transparency, particularly around WIP limits. This provides structure to the Kanban system within Scrum and helps the team optimize their flow and maintain consistency. Reference: The Kanban Guide for Scrum Teams.
質問 # 31
A Scrum Team's Definition of Workflow must have defined points at which the Scrum Team considers work to have started and to have finished. This allows the team to track their Work in Progress (WIP). How are these points defined?
(choose the best answer)
- A. How it is defined and who within the Scrum Team defines it depends on the boundaries and scope of the Definition of Workflow.
- B. Any refined Product Backlog item in the Product Backlog is WIP.
- C. In any way the Scrum Team chooses to define it. They have the final say on the Sprint Backlog.
- D. Any Product Backlog item in the Sprint Backlog is a WIP.
正解:A
解説:
The Definition of Workflow includes the agreed-upon points at which the Scrum Team considers work to have started and finished. These points are determined based on the boundaries and scope of the team's workflow. This definition must be clearly understood by the entire team to track Work in Progress (WIP) effectively and manage flow efficiently. It is up to the Scrum Team to define these boundaries to suit their specific context and workflow needs.
質問 # 32
A cumulative flow diagram can show you:
(Choose the best two answers)
- A. The average Throughput for a specific date range.
- B. The exact average Cycle Time for all items completed on a specific date.
- C. The Cycle Time for an item that completed on a specific date.
- D. The total amount of Work in Progress (WIP) for a specific date.
正解:C、D
解説:
A cumulative flow diagram (CFD) provides insights into the amount of WIP and helps track Cycle Time by showing how long items stay in each stage of the workflow. This visualization tool is valuable for teams using Scrum with Kanban as it highlights bottlenecks and helps manage flow through the stages of the workflow.
References: The Kanban Guide for Scrum Teams.
質問 # 33
Which of the following are considered Kanban practices for Scrum Teams? (choose the best answer)
- A. T-shirt size estimation, service level expectations, limiting Work in Progress (WIP).
- B. Visualizing flow, limiting Work in Progress (WIP), actively manage the Work in Progress (WIP), inspecting & adapting the workflow.
- C. Small batch sizes, limiting Work in Progress (WIP), eliminating waste, Kaizen.
- D. Kaizen, removing bottlenecks, policies radiators, pull system.
- E. Class of service, measuring cost of delay, visualizing the workflow, limiting Work in Progress (WIP), managing flow.
正解:B
質問 # 34
Which formula best represents Little's Law? (choose the best answer)
- A. Average Cycle Time = Average Work in Progress / Average Throughput.
- B. Average Throughput = Average Cycle Time * Average Work in Progress.
- C. Average Throughput = Average Cycle Time / Average Work in Progress.
- D. Average Work in Progress = Average Cycle Time / Average Throughput.
正解:A
質問 # 35
Which of the following are lagging indicator metrics?
(choose the best three answers)
- A. Work in Progress.
- B. Velocity.
- C. Cycle Time.
- D. Throughput.
- E. Work Item Aging.
正解:B、C、D
解説:
Lagging indicator metrics are metrics that provide information about past performance:
1. Velocity (Option A): This is a measure of the amount of work a Scrum Team completes in a Sprint. It is a lagging indicator because it reflects what has been done rather than predicting future performance.
2. Cycle Time (Option B): This metric measures the time taken to complete a work item from start to finish. It is a lagging indicator because it provides data on how long work items took to complete in the past.
3. Throughput (Option D): This refers to the number of work items completed in a given period. Like Velocity, it reflects past performance and is considered a lagging indicator.
Work in Progress (Option C) and Work Item Aging (Option E) are not lagging indicators:
* Work in Progress (C): is a current state metric that indicates how much work is currently in progress.
* Work Item Aging (E): is a leading indicator, providing insights into how long a work item has been in progress, helping predict delays or bottlenecks
質問 # 36
Little's Law states that:
(choose the best answer)
- A. Average Cycle Time = Average Work in Progress / Average Throughput.
- B. Average Throughput = Average Cycle Time * Average Work in Progress.
- C. Average Throughput = Average Cycle Time / Average Work in Progress.
- D. Average Work in Progress = Average Cycle Time / Average Throughput.
正解:A
解説:
Little's Law states:
*Average Cycle Time = Average Work in Progress (WIP) / Average Throughput.
Little's Law is used to understand and forecast the performance of a workflow system. It implies that if you know two of these three variables (Cycle Time, WIP, Throughput), you can calculate the third. The correct formula is Option A( Options B, C, and D do not correctly state Little's Law.
質問 # 37
As input for Daily Scrum, which metrics are likely to provide the most actionable data?
(choose the best answer)
- A. Leading indicators.
- B. Lagging indicators.
正解:A
解説:
Leading indicators are the most appropriate metrics for Daily Scrum because they provide information about the current state of the work and potential future issues. By tracking leading indicators, the team can identify potential problems early on and take proactive measures to address them.
Here are some examples of leading indicators that can be useful during Daily Scrum:
* WIP Limits:Are the WIP limits being adhered to?
* Blocked Tasks:Are there any tasks that are blocked or waiting for dependencies?
* Task Progress:How much progress has been made on each task?
* Team Mood:Is the team morale high or low?
By discussing these leading indicators during the Daily Scrum, the team can identify any impediments and take immediate action to keep the work flowing smoothly.
Lagging indicators, on the other hand, provide information about past performance and are not as useful for identifying and addressing current issues. Examples of lagging indicators include cycle time, lead time, and throughput. While these metrics are important for long-term analysis and improvement, they are not as actionable in the context of the Daily Scrum.
質問 # 38
When is the most appropriate time for Scrum Teams practicing professional Scrum with Kanban to inspect and adapt their Work in Progress (WIP) Limits?
(choose the best answer)
- A. During the Sprint Retrospective.
- B. Never. Once set, WIP Limits cannot be modified.
- C. Anytime the Developers see fit.
- D. Every day during Daily Scrum.
正解:A
解説:
In the context of Professional Scrum with Kanban, the Sprint Retrospective is the most suitable time to inspect and adapt WIP Limits. This is because the Retrospective is a dedicated time-box for the Scrum Team to reflect on its performance and identify areas for improvement.
Here's why:
* Continuous Improvement:The Retrospective is a key part of the Scrum framework, designed to foster continuous improvement. By reviewing WIP Limits during this time, the team can assess their effectiveness and make data-driven decisions.
* Data-Driven Decisions:By tracking WIP Limits over time, the team can gather valuable insights into their workflow and identify bottlenecks. This data can inform decisions about adjusting WIP Limits to optimize flow and productivity.
* Team Collaboration:The Retrospective provides an opportunity for the entire team to discuss and agree upon changes to WIP Limits. This collaborative approach ensures buy-in and commitment from all team members.
While it's true that Developers can monitor WIP Limits throughout the Sprint, the Retrospective is the designated time for a formal review and adjustment. This ensures that any changes are aligned with the team's overall goals and strategy.
質問 # 39
Which of the following helps Scrum Teams, that use Kanban, from exceeding their capacity limits? (choose the best answer)
- A. Managing individual workloads of team members.
- B. Setting a robust Kanban workflow.
- C. Explicit Work In Progress (WIP) Limit policies.
- D. Having daily meetings about work in progress.
正解:C
質問 # 40
True or False: The WIP Limit can only be changed during the Sprint Retrospective.
- A. True
- B. False
正解:B
質問 # 41
True or False: Little's Law is used to forecast a Scrum Team's output.
- A. True
- B. False
正解:B
解説:
* Little's Lawestablishes a relationship between three flow metrics:Work in Progress (WIP),Cycle Time, andThroughput. It provides insights into how changes in one metric affect the others in a stable system.
* Little's Law is used to understand and manage flow within a system but isnot a forecasting tool for output or future performance. It assumes a stable and predictable system where the input and output rates are consistent.
Why Not True?
* Forecasting requires variability, historical data, and often different statistical models. While Little's Law supports system predictability and capacity planning, it does not directly project future Scrum Team outputs or delivery dates.
Thus, Little's Law helps teams analyze and optimize flow but is not used for forecasting.
質問 # 42
What should the Developers do if, during the Sprint, the Product Owner asks them to add an urgent unplanned work item that aligns to the Sprint Goal but does not fit into the current Work in Progress (WIP) Limits?
(choose the two best answers)
- A. Adjust the WIP Limits to allow for taking on the extra item and record it as part of their Definition of Workflow.
- B. Take on the urgent item as an exception to the WIP Limits and visualize that they are above their WIP Limit.
- C. Reject the urgent item since the WIP Limits do not allow it. Tell the Product Owner to wait until the next Sprint.
- D. Add the urgent item to their Sprint Backlog but only start working on it when their WIP Limits allow it.
正解:B、D
解説:
If the Product Owner requests that an urgent, unplanned work item be added during the Sprint, and it aligns with the Sprint Goal but does not fit within the current WIP limits, the Developers should:
1.Add the urgent item to their Sprint Backlog but only start working on it when their WIP Limits allow it (Option A): This maintains the integrity of the WIP limits and ensures that the team doesn't overcommit or create too much work in progress, which could affect flow and focus.
2.Take on the urgent item as an exception to the WIP Limits and visualize that they are above their WIP Limit (Option C): By taking on the urgent item as an exception, the team can address the urgency while being transparent about the temporary breach of the WIP limits. This visualization helps the team and stakeholders understand the current state of work and its impact( Options B (Adjust the WIP Limits) and D (Reject the urgent item) are less suitable because they either undermine the WIP control mechanism or fail to accommodate a potentially critical change that aligns with the Sprint Goal.
質問 # 43
Which of these metrics is most valuable for Sprint Planning? (Choose the best answer)
- A. Work Item Age.
- B. Throughput.
- C. Points Delivered.
- D. Cycle time.
正解:B
質問 # 44
What does it mean when a Scrum Team chooses to communicate an 85% 5-day service level expectation (SLE)?
- A. The team can get any critical system backup within 5 days.
- B. The team expects they will complete a work item within 5 days of when they start working on it 85% of the time.
- C. In the last Sprint, the team has been able to complete 85% of Product Backlog items within 5 days of starting work on the item.
- D. The team promises to have 85% of all Product Backlog items done within 5 days.
正解:B
解説:
An SLE of 85% for 5 days signifies that the team anticipates they will complete items within 5 days, 85% of the time. This helps set clear expectations with stakeholders, ensuring transparency around potential delivery timelines. The SLE is based on historical data and provides a probability-based forecast, rather than a commitment. References: The Kanban Guide for Scrum Teams.
質問 # 45
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.
- A. True
- B. False
正解:B
質問 # 46
Scrum Teams using Kanban can start to increase predictability by:
- A. Reducing the amount of work in progress by introducing Work in Progress (WIP) Limits.
- B. Visualizing the Workflow using a Kanban board.
- C. Improving transparency by having a CFD: Control Chart and Aging chart.
- D. Inspecting and adapting the Product Backlog during the Sprint Review.
正解:A
解説:
By limiting WIP, Scrum Teams using Kanban create a more predictable flow, as it prevents the team from overcommitting and encourages them to finish work items before starting new ones. This aligns with Kanban' s principle of optimizing flow and Scrum's iterative delivery approach. References: The Kanban Guide for Scrum Teams.
質問 # 47
How does Kanban support empiricism? (choose the best two answers)
- A. The Kanban board provides transparency that helps the Scrum Teams inspect and adapt their process.
- B. 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.
- C. The Product Owner uses Kanban metrics to inspect the Throughput and adapt the Developers' Cycle Time accordingly.
- D. Kanban prescribes specific practices that reduces the need for empiricism.
正解:A、B
質問 # 48
When using Kanban in a Scrum environment, some resistance toward introducing Work in Progress (WIP) Limits may be encountered. What is an alternative to introducing WIP Limits in Kanban?
- A. Building a strong team identity using Squads and tribes.
- B. Conducting Daily Stand-Up meetings that control not having too much work.
- C. Using Kanban boards that improve visualization and enhance communication.
- D. None, Professional Scrum with Kanban cannot be used without explicit WIP Limits.
正解:C
解説:
Although WIP limits are central to Kanban, enhancing visualization and communication through Kanban boards can be a way to ease into WIP limits gradually. This alternative fosters transparency and alignment without directly imposing WIP constraints, which can be beneficial for teams adjusting to Kanban practices.
References: The Kanban Guide for Scrum Teams.
質問 # 49
When can a Work in Progress (WIP) Limit change?
(choose the best answer)
- A. At any time.
- B. Only during Sprint Planning.
- C. Only during the Daily Scrum.
- D. It never changes.
- E. When the Product Owner decides to change it.
- F. Only during the Sprint Retrospective.
正解:F
解説:
According to the Kanban Guide for Scrum Teams, Work in Progress (WIP) limits are set to control the amount of work in progress in a system, enhancing flow, reducing bottlenecks, and ensuring smoother delivery. WIP limits can be changed as a result of an inspection and adaptation cycle, which primarily occurs during the Sprint Retrospective.
During the Sprint Retrospective, the Scrum Team reflects on its process, practices, and interactions. This is the time when the team inspects its flow, evaluates the effectiveness of the current WIP limits, and can make decisions to adjust them based on observed issues or potential improvements. The goal is to optimize the team's ability to deliver value, and adjusting WIP limits during the Retrospective allows for thoughtful consideration based on the team's experience and data from the completed Sprint.
Changing WIP limits at other times could disrupt the flow and reduce the predictability and stability that the limits are intended to create. Therefore, the best practice is to evaluate and change them during the Sprint Retrospective, where the team can inspect the results of their workflow and make informed decisions for the upcoming Sprints
質問 # 50
......
PSK-I問題集合格確定させる練習には75問があります:https://www.goshiken.com/Scrum/PSK-I-mondaishu.html
PSK-I練習テスト問題解答更新された75問があります:https://drive.google.com/open?id=1eYMDDlBxf2LH4mrUmsPl-eoOMLlO7dEx