Agile Charts
Burn up charts
1. Burn up charts allow the team to track performance visually while also tracking
changes in the scope of work that could affect their velocity or completion of
stories in an iteration
2. Burn up charts can be converted to cumulative flow diagrams by the addition of
WIP
3. Burn up charts that track total scope (rather than burn down charts) separate out
the rate of progress from the scope fluctuations
4. The main reason agile teams use burn charts is to show their progress and make
it easy to see the expected completion date based on the current velocity trend.
5. is not true is “Burn down charts indicate whether rate of effort changes are due
to changes in progress rates or scope
6. A burnup chart shows the accumulation of tested and working feature over time.
Burn Down charts
Bottom of the bar is lowered when additional work is added. Bottom of the bar is
raised when scope is removed. Top of the bar will be lowered when work is
delivered.
Kanban Board
A whiteboard with columns for various stages of work, on which you post sticky
notes that represent the tasks you are working on.
A Kanban board will show user stories progress through a series of phases that
being with requirements, followed by development, and finally completed by
testing.
Kanban teams use their WIP limits to control the number of items that can be in
a given stage of work at a time.
Kanban board shows work in progress (WIP), which represents work started but
not completed. Therefore, the WIP should be limited and carefully managed to
maximize performance. More WIP does not equal more output; in fact, it is quite
often the opposite. Also, WIP is any work that is in progress, regardless of what
stage the work is at,
Kanban teams typically use cumulative flow diagrams to visualize the flow of
work through the process. This allows them to get a visual sense of the average
arrival rate (how frequently work items are added), lead time (the amount of
time between when a work item is requested and when it's delivered), and work
in progress (the number of work items in the process at any time).
, When teams use a kanban board to visualize their workflow, they use columns to
represent workflow steps, and typically use sticky notes or index cards to show
individual work items flowing through the process. If items tend to accumulate in
one column, it tells the team that step is a potential root cause for the process
flow slowing down. The way to fix it is to work with the stakeholders to impose a
work in progress (WIP) limit, usually by writing the maximum allowable number
of work items for that step.
In a pull system, the later step in a process pulls work from the previous one. This
keeps the workload even and is the least wasteful way to get work from the
beginning to the end of a process.
The order of the practices in Kanban is: visualize workflow, limit WIP, manage
flow, make process policies explicit, implement feedback loops, improve
collaboratively, evolve experimentally
Why Kanban may be considered controversial: Kanban does reduce planning and
may eliminate estimation
Characteristics of Kanban:
A) Kanban focuses on delivering value
B) Kanban relies on staff specialization in each phase
C) Kanban includes reflection as part of its process
D) Kanban is as adaptable as other agile methods
one limitation of Kanban, which is in conflict with the best agile practices, is its reliance on staff
specialization in each phase, while agile preaches for generalizing specialists. Some argue that
this may be considered a reason why Kanban is not considered agile ‘enough’.
Cumulative Flow Diagram (CFD)
1. Cumulative flow diagrams help tracking and forecasting the delivery of value
2. Reveals the total in progress and completed work
3. A cumulative flow diagram allows the team to track the work in progress, the
work performed over time, and cycle time. It also provides a means to interpret
bottlenecks in process steps
4. To visually analyze their work in progress for each step in a process in order to
determine quickly where bottlenecks exist in the overall process. What tool
would help them the most?
WIP:
Q1: What is the main purpose of imposing limits on working progress ?
A. To optimize throughput
B. To minimize resource allocation
C. To visualize lead time
D. To balance workflow
For the exam, it's important to understand that the purpose of using WIP limits is to
Burn up charts
1. Burn up charts allow the team to track performance visually while also tracking
changes in the scope of work that could affect their velocity or completion of
stories in an iteration
2. Burn up charts can be converted to cumulative flow diagrams by the addition of
WIP
3. Burn up charts that track total scope (rather than burn down charts) separate out
the rate of progress from the scope fluctuations
4. The main reason agile teams use burn charts is to show their progress and make
it easy to see the expected completion date based on the current velocity trend.
5. is not true is “Burn down charts indicate whether rate of effort changes are due
to changes in progress rates or scope
6. A burnup chart shows the accumulation of tested and working feature over time.
Burn Down charts
Bottom of the bar is lowered when additional work is added. Bottom of the bar is
raised when scope is removed. Top of the bar will be lowered when work is
delivered.
Kanban Board
A whiteboard with columns for various stages of work, on which you post sticky
notes that represent the tasks you are working on.
A Kanban board will show user stories progress through a series of phases that
being with requirements, followed by development, and finally completed by
testing.
Kanban teams use their WIP limits to control the number of items that can be in
a given stage of work at a time.
Kanban board shows work in progress (WIP), which represents work started but
not completed. Therefore, the WIP should be limited and carefully managed to
maximize performance. More WIP does not equal more output; in fact, it is quite
often the opposite. Also, WIP is any work that is in progress, regardless of what
stage the work is at,
Kanban teams typically use cumulative flow diagrams to visualize the flow of
work through the process. This allows them to get a visual sense of the average
arrival rate (how frequently work items are added), lead time (the amount of
time between when a work item is requested and when it's delivered), and work
in progress (the number of work items in the process at any time).
, When teams use a kanban board to visualize their workflow, they use columns to
represent workflow steps, and typically use sticky notes or index cards to show
individual work items flowing through the process. If items tend to accumulate in
one column, it tells the team that step is a potential root cause for the process
flow slowing down. The way to fix it is to work with the stakeholders to impose a
work in progress (WIP) limit, usually by writing the maximum allowable number
of work items for that step.
In a pull system, the later step in a process pulls work from the previous one. This
keeps the workload even and is the least wasteful way to get work from the
beginning to the end of a process.
The order of the practices in Kanban is: visualize workflow, limit WIP, manage
flow, make process policies explicit, implement feedback loops, improve
collaboratively, evolve experimentally
Why Kanban may be considered controversial: Kanban does reduce planning and
may eliminate estimation
Characteristics of Kanban:
A) Kanban focuses on delivering value
B) Kanban relies on staff specialization in each phase
C) Kanban includes reflection as part of its process
D) Kanban is as adaptable as other agile methods
one limitation of Kanban, which is in conflict with the best agile practices, is its reliance on staff
specialization in each phase, while agile preaches for generalizing specialists. Some argue that
this may be considered a reason why Kanban is not considered agile ‘enough’.
Cumulative Flow Diagram (CFD)
1. Cumulative flow diagrams help tracking and forecasting the delivery of value
2. Reveals the total in progress and completed work
3. A cumulative flow diagram allows the team to track the work in progress, the
work performed over time, and cycle time. It also provides a means to interpret
bottlenecks in process steps
4. To visually analyze their work in progress for each step in a process in order to
determine quickly where bottlenecks exist in the overall process. What tool
would help them the most?
WIP:
Q1: What is the main purpose of imposing limits on working progress ?
A. To optimize throughput
B. To minimize resource allocation
C. To visualize lead time
D. To balance workflow
For the exam, it's important to understand that the purpose of using WIP limits is to
