Sprint length \/ iteration length by methodology<\/h3>\n\n\n\n
Methodology<\/th>
Correct term<\/th>
Typical length<\/th>
Explanation<\/th><\/tr><\/thead>
Agile<\/strong><\/td>
Iteration \/ sprint, depending on framework<\/td>
Usually 1\u20134 weeks<\/strong><\/td>
Agile is a broad mindset, not one fixed process. Different Agile frameworks use different time-boxes.<\/td><\/tr>
Scrum<\/strong><\/td>
Sprint<\/strong><\/td>
Usually 1\u20134 weeks<\/strong><\/td>
Scrum uses a fixed-length sprint to plan, build, review, and improve. Your slides define a sprint as a time-boxed period of 1\u20134 weeks<\/strong> that creates a potentially shippable product increment.<\/td><\/tr>
XP \/ Extreme Programming<\/strong><\/td>
Iteration<\/strong><\/td>
Usually 1\u20132 weeks<\/strong>, sometimes up to 3 weeks<\/td>
XP uses short iterations to support frequent feedback, continuous integration, testing, refactoring, and small releases.<\/td><\/tr>
Kanban<\/strong><\/td>
No sprint required<\/td>
No fixed sprint length<\/strong><\/td>
Kanban is based on continuous flow. Work is pulled through the board as capacity becomes available, rather than being planned into fixed sprints. Your slides describe Kanban as continuous flow with no fixed iterations.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Simple explanation<\/h3>\n\n\n\n
A sprint<\/strong> is a fixed time-box used mainly in Scrum<\/strong>. For example, a team may choose a 2-week sprint<\/strong>. At the beginning, they plan the work. During the sprint, they execute and track progress. At the end, they review the completed increment and hold a retrospective.<\/p>\n\n\n\n
In XP<\/strong>, the idea is similar, but the term iteration<\/strong> is more common. XP iterations are usually short because XP emphasizes quick feedback, frequent releases, testing, and continuous improvement.<\/p>\n\n\n\n
In Kanban<\/strong>, there is normally no sprint length<\/strong> because work flows continuously. Instead of saying, \u201cWhat can we finish in the next two weeks?\u201d, a Kanban team asks, \u201cWhat is the next highest-priority item we can pull now, based on available capacity and WIP limits?\u201d<\/p>\n\n\n\n
For students, you can say:<\/p>\n\n\n\n
\n
Scrum works in fixed sprints. XP works in short iterations. Kanban works in continuous flow. Agile is the umbrella concept that can include all of these approaches.<\/p>\n<\/blockquote>\n\n\n\n
<\/p>\n\n\n\n
WIP Limits:<\/h2>\n\n\n\n
WIP limits<\/strong> means Work-In-Progress limits<\/strong>.<\/p>\n\n\n\n
In Kanban, a WIP limit sets the maximum number of work items allowed in one workflow stage at the same time<\/strong>. For example, a team may decide that only 3 user stories<\/strong> can be in In Progress<\/strong> at once. Your slides define WIP limits as a constraint-based approach used to optimize flow and prevent overloading the team.<\/p>\n\n\n\n
Term<\/strong><\/td>
Meaning<\/strong><\/td><\/tr><\/thead>
WIP<\/strong><\/td>
Work currently started but not yet finished<\/td><\/tr>
WIP Limit<\/strong><\/td>
Maximum number of items allowed in a stage<\/td><\/tr>
Purpose<\/strong><\/td>
Prevent too much work from being started at once<\/td><\/tr>
Benefit<\/strong><\/td>
Helps reveal bottlenecks and improves delivery speed<\/td><\/tr>
Common Kanban columns<\/strong><\/td>
Backlog \u2192 To Do \u2192 In Progress \u2192 Review\/Testing \u2192 Done<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Example:<\/p>\n\n\n\n
Kanban Column<\/strong><\/td>
WIP Limit<\/strong><\/td>
Meaning<\/strong><\/td><\/tr><\/thead>
To Do<\/td>
No limit<\/td>
Work waiting to be started<\/td><\/tr>
In Progress<\/td>
3<\/td>
Only 3 items can be actively worked on<\/td><\/tr>
Review \/ Testing<\/td>
2<\/td>
Only 2 items can wait for review\/testing<\/td><\/tr>
WIP limits stop the team from starting too many things at the same time. Instead of everyone beginning new tasks, the team focuses on finishing existing work first.<\/p>\n\n\n\n
What the action looks like:<\/strong><\/p>\n\n\n\n
A team has 3 stories already in In Progress<\/strong>, and the WIP limit is 3. A developer cannot pull another story into In Progress<\/strong> until one of the current stories moves to Review<\/strong> or Done<\/strong>.<\/p>\n\n\n\n
This helps the team ask:<\/p>\n\n\n\n
\u201cWhy is work stuck here?\u201d \u201cDo we need to help finish current work before starting new work?\u201d \u201cIs testing or review becoming a bottleneck?\u201d<\/p>\n\n\n\n
In Jira or a Kanban board, WIP limits usually appear as a number on top of a column, such as:<\/p>\n\n\n\n
In Progress 3\/3<\/strong><\/p>\n\n\n\n
That means the column is full. The team should finish or move existing work before starting more.<\/p>\n","protected":false},"excerpt":{"rendered":"
Sprint length \/ iteration length by methodology Methodology Correct term Typical length Explanation Agile Iteration \/ sprint, depending on framework Usually 1\u20134 weeks Agile is a broad mindset, not one fixed process. Different Agile frameworks use different time-boxes. Scrum Sprint Usually 1\u20134 weeks Scrum uses a fixed-length sprint to plan, build, review, and improve. Your … <\/p>\n