Professional Scrum with Kanban level I 온라인 연습
최종 업데이트 시간: 2024년11월08일
당신은 온라인 연습 문제를 통해 Scrum PSK-I 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 PSK-I 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 138개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
Kanban is a strategy for optimizing the flow of value through a process that uses a visual, work-in-progress limited pull system. The flow-based perspective of Kanban is used to enhance and complement the Scrum framework and its implementation.
정답:
Explanation:
Probabilistic forecasting is an alternative to an estimates based approach. Rather than asking your teams to break down a lot of work up front, and then estimate it, we can use past data generated by the team from the work they've already done to extrapolate a forecast of what may happen in the future. A probabilistic forecast is one that acknowledges a wide array of possible outcomes and assigns a probability, or likelihood of happening, to each. Every probabilistic forecast should have 2 components: a range and a probability.
정답:
Explanation:
Throughput: The number of work items finished per unit of time. Throughput is the theoretical bandwidth of the team. For example, a team has delivered 10, 8, 12 and 10 Product Backlog items (PBIs) in each of the last 4 Sprints. The average throughput is 10 PBIs per Sprint. So based on historical data, the team can complete 1-10 PBIs in 1 Sprint. 1-15 PBIs in 2 Sprints, and so on. Remember, that 'can complete'
and 'will complete' is different. 'Will complete' is absolute where as 'can complete' is not and can have dependencies.
정답:
Explanation:
In case the item is pulled into the Sprint Backlog, then the Developers need to figure out whether they can actually start it right away. This depends on the WIP limits and the current WIP. If the team is at their WIP limit they shouldn't pull in that new item until some room frees up.
The longer it might take to get a normal pull slot ready, the more pressure there might be to actually expedite this card. This means going beyond the current WIP limits and pushing this item along on top of the existing flow. The typical way to do this is NOT to change the WIP limit definition but to go above WIP and note a WIP exception. These exceptions can then be a topic for inspection and adaptation at the Sprint Retrospective.
정답:
Explanation:
Visualization using the Kanban board is the way the Scrum Team makes its workflow transparent. The board's configuration should prompt the right conversations at the right time and proactively suggest opportunities for improvement. Visualization should include explicit policies such as the WIP limit for each lane or each person, escalation/class of service policies, how to visualize and deal with blockers, how to prioritize work.
정답:
Explanation:
Kanban is a strategy for optimizing the flow of value through a process that uses a visual, work-in-progress limited pull system. Central to the definition of Kanban is the concept of flow. Kanban optimizes flow by improving the overall efficiency, effectiveness, and predictability of a process.
정답:
Explanation:
The fundamental result of Little's Law is that for a given process, in general, the more things that you work on at any given time (on average) the longer it is going to take for each of those things to finish (on average). Average Cycle Time = Average Work In Progress / Average Throughput
정답:
Explanation:
Work in Progress (WIP) limits restrict the maximum amount of work items in the different stages of the workflow. This would be the defined boundaries/container of which the Scrum Team works from.
The Sprint Backlog is owned by the Developers so it would make sense for them to self-manage and own their workflow and WIP Limits in this case. If the Developers want to involve the Product Owner in their Sprint flow then the Scrum Team will self-manage to define the WIP Limits.
정답:
Explanation:
When Kanban practices are applied to Scrum, they provide a focus on improving the flow through the feedback loop; optimizing transparency and the frequency of inspection and adaptation for both the product and the process. The Scrum framework itself does not change and is only supplemented with Kanban practices.
This can result in additional collaboration, lower cycle times, additive transparency, and helping identify process improvements.
정답:
Explanation:
The four basic metrics of flow that Scrum Teams using Kanban need to track are as follows:
Work in Progress (WIP): The number of work items started but not finished.
Cycle Time: The amount of elapsed time between when a work item starts and when a work item finishes.
Work Item Age: The amount of time between when a work item started and the current time. This applies only to items that are still in progress.
Throughput: The number of work items finished per unit of time.
정답:
Explanation:
Scrum Teams can achieve flow optimization by using the following four practices:
Visualization of the workflow
Limiting Work in Progress (WIP)
Active management of work items in progress
Inspecting and adapting the team’s definition of "Workflow"
정답:
Explanation:
One of the keys to effective visualization for a Scrum Team is to make sure it sees the flow of Product Backlog items from the Product Backlog (idea identification, through refinement, analysis), Sprint Backlog (design, coding, testing, and deployment); all the way to "Done" (Definition of Done).
정답:
Explanation:
The Kanban complementary practices don’t replace Scrum’s Sprint. The Scrum Framework has built in components that are the starting point (foundation) for Kanban practices to enhance and expand. The Sprint is still a cadence or a regular heartbeat for inspection and adaptation of both product and process. Teams using Scrum with Kanban use the Sprint events as a feedback improvement loop by collaboratively inspecting and adapting their definition of "Workflow" and flow metrics.
정답:
Explanation:
Work Item Age is a leading indicator for what a team’s cycle time (i.e. the length of the feedback loop) is likely to be for a certain item.
It is also a leading indicator to determine when an item, that is in progress, is likely to be 'finished' in
order for the team to adapt their Sprint.
정답:
Explanation:
The four basic metrics of flow that Scrum Teams using Kanban need to track are as follows:
Work in Progress (WIP): The number of work items started but not finished.
Cycle Time: The amount of elapsed time between when a work item starts and when a work item finishes.
Work Item Age: The amount of time between when a work item started and the current time. This applies only to items that are still in progress.
Throughput: The number of work items finished per unit of time.