Lean, Agile, Visual Management from the Trenches
Organizations new to Kanban that have no experience with Agile usually find it easier to design their boards than those with Agile background because Kanban recommends the board to reflect the actual process rather than an abstraction. This is a good start. As we all know, a project’s behavior changes over time. This means the Kanban board should keep up with those changes, but unfortunately many Kanban organizations…
Just like everything else, translating a book using Kanban methodology is about the mindset, good communication and good team work. The bulk of the work was performed by the Spanish team, while we acted mainly as advisers committed to give early feedback when required. The initial draft was done extremely quickly, and the final version was approved a few days later.
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.
We are happy to announce a new Swift-Kanban release, ver 1.4.3 that we pushed out over the weekend with several minor yet meaningful features and
We are back with some new and exciting feature updates to Swift-Kanban. In this release, we have strengthened the support of SCRUM in Swift-Kanban with
One of the key benefits that David Anderson, the renowned Kanban thought-leader and father of the Kanban Method for software development (as well as Advisor to Digité) highlights about Kanban is that it is evolutionary and not revolutionary. That is to say, it does not introduce a humongous new set of processes in an organization and cause massive disruption like traditional methods have tended to do.
It’s always exciting to be back with some great updates for you in our releases! In this release v 1.4.4, we have added several features
By now you have heard about Kanban and you think that it is applicable to your work – Being simple to implement and being very visual are attributes of Kanban that make it easy to adopt and use. And we all like the fact that Kanban makes a team self-directing – so the team takes responsibility on itself for timely deliverables, quality and overall communication. But how does Kanban enable teams to make this magical transformation from finger pointing to self-directing, right in front of our eyes?
The term Lean Software Development was first coined as the title for a conference organized by the ESPRIT initiative of the European Union, in Stuttgart Germany, October 1992. Independently, the following year, Robert “Bob” Charette in 1993 suggested the concept of “Lean Software Development” as part of his work exploring better ways of managing risk in software projects. The term “Lean” dates to 1991, suggested by James Womack, Daniel Jones, and Daniel Roos, in their book The Machine That Changed the World.
Lean Kanban University accredited Kanban training program there has been some commentary questioning whether I and LKU have the right to assert ourselves with such authority. These issues are worth addressing. The questioners suggest whether I invented Kanban or own it and if not then what gives LKU legitimacy to trade as we intend to do, offering standardized accredited training delivered by accredited trainers? While these questions are coming from outside the community and it would be easy to dismiss them as coming from disgruntled people with an axe to grind or sour grapes to squash, I believe the questions are worth addressing.
Try SwiftKanban Enterprise Plan FREE for 30 days.
