Kanban is an agile method that uses a visual board with columns to manage work in progress. It focuses on limiting work-in-progress instead of having sprints or deadlines. Kanban can be better than Scrum for small teams, startups, or when tasks are variable since it allows for faster feature deployment without fixed timeboxes and less process overhead. The key aspects of Kanban include a customizable board with columns, optional constraints on work-in-progress per column, and an optional expedite row to prioritize certain tasks.

1. Quick Intro Into Kanban
#SperasoftTalks

2. Agenda
• When Scrum is not so good
• What is Kanban
• Why Kanban
• Kanban board

3. Sometimes Scrum is not so Good
When:
• Startups / prototyping
• Small team (1-2 developers)
• Support tasks
What:
• No fast feature deployment
• Too much time to start new sprint
• Too much time for process
• Variable QA loading

4. What is Kanban
• Kanban is Agile
• Developed in Toyota
• Demand forecasting VS Just-in-time delivery
• Work-in-progress decreasing
• Kanban board and cards
• Not process but tasks oriented
• No timeboxes (no sprints too)
• Task estimation is optional (do we need it?)

5. Have a question?
Like this deck?
Just follow us on twitter
@Sperasoft

6. Why Kanban
• Feature driven development
• Focus on tasks instead of process

7. Kanban Board
• Columns set is customizable
• Expedite row (optional)
• Column constraints (optional)
• Available in JIRA with Greenhopper

8. Follow us on Twitter
@Sperasoft
Visit our site:
sperasoft.com