Key Concepts in Agile and Kanban
Classified in Other subjects
Written on in 
English with a size of 4.74 KB
Work in Progress and Lead Time
As Work in Progress (WIP) increases, the lead time increases.Kanban Board Basics
A Kanban board includes at least the tasks to do and work limits in each phase.Starting with Kanban Practices
Among the 6 Kanban practices, it is best to start from: visualizing the work and limiting the work in progress.Agile Project Management Focus
Agile project management gives more importance to: individuals and interactions over processes and tools.Product Backlog Prioritization
The person responsible for prioritizing the product backlog is the Product Owner.Product Backlog Refinement Objective
The Product Backlog refinement meeting objective is best described as: decomposing large functionalities into smaller ones, such as user stories, that are understood...Review vs. Retrospective Meeting
The review meeting differs from the retrospective meeting in that the review meeting focuses on the product, and the retrospective focuses on the process.Understanding the Bottleneck
The bottleneck is the resource which has the highest ratio of finished work per unit of time.Sizing Product Backlog Items
In Agile, to size a Product Backlog item, Story Points are used.Best Environment for Agile
Agile project management is the best approach for the following environment: uncertain environments where change occurs and we need to adapt...Agile Values
Agile values include: collaboration with the customer, continuous improvement collaboratively, and individuals and interactions.Standard Service Flow
Which is correct: A standard service/task follows a FIFO (First-In, First-Out) system.Agile Environment Suitability
Agile project management is the best approach for the following environment: uncertain environments where change occurs and we need to adapt to those changes.Sprint Planning Example
Sprint Planning 7: Average velocity 15. Items selected: Us1, Us2, Us3, Us5, Us7.Sprint Commitment Rationale
Explain why the team should commit to those story points for Sprint 7: Como la media es 15, cogemos hasta completar 15. (Since the average is 15, we take items until we complete 15).Laws for Managing Kanban Flow
Explain shortly the three laws that should be taken into consideration when managing the flow in a Kanban system:- Little’s Law: Delivery Rate = WIP / Lead Time
- Bottleneck’s Law:
- Part of the system with the lowest capacity.
- The part in which the flow is lowest.
- The slower the bottleneck, the higher the delivery time or lead time.
- Variation’s Law:
- Variation = difference in type of work and complexity.
- High utilization (capacity or usability near 100%) leads to lower efficiency and higher lead time.
Causes of Low Flow Efficiency
Name at least 3 causes of low flow efficiency:- Large number of Work in Progress (WIP).
- Large delivery time.
- Bottlenecks.
- Process variations.
- Focusing on resource saturation (resource utilization near 100%).
Identifying the Bottleneck (Example)
Where is the bottleneck according to this Kanban board: Hay que tener en cuenta que es un sistema pull y cuál es el WIP, por lo que en este caso es test. (Considering it is a pull system and what the WIP is, in this case, it is 'test').Sprint Planning Meeting Details
Explain the Sprint Planning meeting: What is done and who is in that meeting: The Product Owner and the team meet to determine which requirements are most important for the upcoming sprint.
Review Concepts
Variability and Lead Time
As the variability in capability utilization increases, the lead time increases.Cumulative Flow Diagram
A Cumulative Flow Diagram (CFD) shows the number of items (e.g., incidents, tasks) that are in the system over time.Product Backlog Definition
In Agile, the Product Backlog is a list of product functionalities. It contains the description of the functionality, its priority, acceptance criteria, and an estimation of the effort.