At Digité/ Swift-Kanban, we had a great visit to the LeanSSC (now Lean Systems Society) last week in Boston. Having been in the market for just about a year, it is heartening to be recognized and even be told that we are considered one of the top 2-3 Kanban tools that are out there.
An exciting part of the conference was our announcement of our support for Scrumban (or Scrum features) besides our support for both iOS and Android tablets. Those who came to the booth and saw a demo really loved our embedded support for release/ iteration planning, time capture, burn-down/ burn-up charts and all of the other new features we demonstrated during the show. Someone from a competitor’s booth next to us in fact said we were pretty much the first Scrumban tool in the market, a possibility we had considered and talked about, although somewhat hesitantly!
The labeling of Scrumban was a matter of some discussion – both at the booth but more interestingly at the Monday (or Tuesday) morning Lean Coffee session organized by Jim Benson, where I posed the question – Scrum --> Kanban = Scrumban or Kanban? In other words, when a Scrum team uses Kanban to improve their processes, is the end-result that they begin using a combination of Scrum and Kanban (Scrumban) or do they essentially start using just Kanban for software development? Luckily for me, this question got the most votes and ended up being discussed for quite some time.