For a specific Sprint Backlog item that has been started, what is the best chart (analytic) to
determine when it will be finished?
(choose the best answer)
The Work Item Aging Chart is the best chart to determine when a specific Sprint Backlog item that has been started will be finished. This chart provides a visual representation of how long each work item has been in progress, without being completed. It focuses on items that are currently active and helps teams identify which items are aging too much in the workflow, which might require attention to ensure they are completed promptly. The Work Item Aging Chart helps to quickly identify items that might be taking longer than expected, making it ideal for forecasting when a started item will be finished
What is Kanban?
(choose the best answer)
Kanban is:
* A strategy for optimizing the flow of value through a process (Option B): Kanban focuses on improving flow and efficiency by using a visual pull system with limited WIP. This strategy helps teams balance demand against throughput and enhance productivity by limiting the number of work items in progress.
Options A (methodology for visualizing workflow) and C (set of practices additive to Scrum) are partially correct but do not fully capture Kanban's purpose. Kanban is not just a visualization tool (A), and while it can be additive to Scrum (C), it is fundamentally a flow-based strategy
True or False: Little's Law is used to forecast a Scrum Team's output.
Little's Law is a formula used to understand the relationship between system throughput, work-in-progress (WIP), and lead time. While it can be used to analyze and optimize the flow of work, it is not specifically designed for forecasting a Scrum Team's output.
Scrum Teams typically use techniques like story point estimation and historical velocity to forecast their output.
True or False: When the Developers add Kanban to Scrum, the way they use the Sprint Goal
during their Daily Scrum changes.
When Developers add Kanban to Scrum, the way they use the Sprint Goal during their Daily Scrum can change. In traditional Scrum, the Sprint Goal is a shared commitment for the Sprint. However, in Professional Scrum with Kanban, the focus shifts to the flow of work and delivering value incrementally.
While the Sprint Goal still provides direction, the Daily Scrum may involve discussions about:
Progress towards the Sprint Goal: How are we progressing towards the overall goal?
Work in Progress (WIP): Are we adhering to WIP limits?
Blockers and impediments: What is preventing the team from progressing?
Prioritization: Are we working on the highest-value items?
By focusing on these aspects, the team can ensure that they are delivering value continuously and efficiently.
Which of these is NOT a good description of Cycle Time?
(choose the best answer)
Cycle Time in the context of Professional Scrum with Kanban is defined as the time it takes for a single work item to move from the start to the end of a specific process or workflow. This metric is crucial for understanding how efficiently a team can process individual work items through their defined workflow stages.
* Option A describes a broader measurement from the initial concept to customer feedback post-release. This could align more with the concept of Lead Time rather than Cycle Time.
* Option B correctly describes a possible measurement for Cycle Time --- the time a work item spends in one specific column (workflow stage). This is in line with the definitions provided in the Kanban Guide for Scrum Teams, where Cycle Time can measure time within distinct parts of the workflow.
* Option D accurately reflects the definition of Cycle Time, which measures the elapsed time from when work starts on an item until it is completed.
* Option C describes 'Throughput,' which is a measure of the number of items delivered over a specific time period (e.g., daily or weekly). This is not related to Cycle Time but is a separate flow metric often used alongside Cycle Time to understand team performance and capacity better(
Thus, Option C is the correct answer as it does not correctly describe Cycle Time. This explanation is verified with resources from Scrum.org that define Cycle Time within the scope of Professional Scrum with Kanban practices.
Tayna
5 hours agoRonna
4 days agoRueben
14 days agoCarolynn
1 months agoAllene
1 months agoShasta
1 months agoMelita
2 months agoLea
2 months agoCarmen
2 months agoGeorgeanna
3 months agoChandra
3 months agoFranklyn
3 months agoIn
4 months agoVivan
4 months agoEthan
4 months agoLucina
4 months agoJesus
4 months agoNan
5 months agoNelida
5 months agoRuth
5 months agoJesus
5 months agoCassie
5 months agoFrance
6 months agoJacklyn
6 months agoRikki
6 months agoAyesha
6 months agoCharlette
6 months agoLashawnda
7 months agoMatt
7 months agoVicki
7 months ago