This document discusses using ScrumBan, a combination of Kanban and Scrum practices, in a typical maintenance project. ScrumBan provides visibility into priorities, bottlenecks, and the sequence of work. It also allows people to focus on their work while increasing understanding of the project. The document provides a general overview and recommends a resource on making the most of both Kanban and Scrum methods.

1. @xabarx
abaranovskis
My everyday work
ScrumBan in practice
Armands Baranovskis

2. Business as usual
• What to tell?
• Why?
• There’s nothing interesting about
it…

3. My feelings in a typical project

5. Typical maintenance project
Maintenance Changes
Kanban Scrum
Team

6. Best tool for everything

7. General overview

8. Maintenance

9. Changes

10. Changes/Improvements
• Maintenance and changes are organized
differently (according to specifics)
• Increased understanding about priorities and
sequence of work
• Visible bottlenecks
• People can concentrate on their work

11. Easy reading
Kanban and Scrum – making the most of both:
http://www.infoq.com/resource/minibooks/kanban-scrum-
minibook/en/pdf/KanbanAndScrumInfoQVersionFINAL.pdf

12. Thank you
eBIT
www.ebit.lv
e-mail: armands.baranovskis@ebit.lv