Scrum and Kanban are both project management methods, based on splitting the work load into small, easily manageable tasks.
Scrum subdivides Sprints (a couple week long work plan) into items, it also subdivides the team into cross-divisional workgroups and it works on the idea that the job (usually software, as that's the business that Scrum has been perfected for) is usable after each iteration (sprint).
Kanban, in turn, puts focus onto visualization of the work load on limiting work in progress at any time. It makes no rule of splitting the team. Kanban utilizes each step of the work process as an opportunity to improve. With the analytical functions that can be extracted from the task data, this continuous improvement is in fact easy to achieve.
As Scrum works best for larger teams and is somewhat restricted to the business type that it can be applied to (because of the iterating mode), it seems like a fine idea to marry it with more uniform Kanban.
What you take from Scrum is the sprint idea (planning work for some defined amount of time), the stand-up meetings and all else artifacts (perhaps a whiteboard). On top of this you'd add WIP limits, applied for any point in time (not per sprint, like in Scrum), a simple visualization of workflow and the determination to review progress and therefore allow for continuous improvement.
Try for free now. A free trial is available for all types of accounts, with no credit card details required.
Sign up now for a free trial »
Český
Deutsch
Español
Française
Italiano
Polski
Portuguese
Русский