Our Kanban journey began early in 2010 when we decided that we would build a product in the Kanban space that would address some of the basic issues we saw our prospects face in adoption of Agile methods such as Scrum and XP within their organizations that were historically used to doing waterfall or iterative or some hybrid Agile method that combined more than one type of processes. While the presence of established competitors was a strong reason to look beyond the ‘popular’ Agile methods, we also felt a strong appeal for Kanban existed because of its focus on 3 key fundamentals.
I recently participated in a local Scrum event in Bangalore and shared my experience in trying to implement Scrum and later Scrumban within my current organization. I have shared the slides below.The event was hosted by SAP in their campus and had a keynote speaker who shared the information about Lean/ Scrum implementation @ SAP and how they are trying to transform the entire organization to a newer or “lean” way of software development.
It was a great experience for me. The conference had a varied set of topics from Lead development, Kanban, CMMi (1 day), Risk Management, Systems Design, Kanban games etc. It was amazing to see this level of change, innovation and creativity in the Lean community and adoption in the industry. Companies and individuals are continually making effort to apply new and improved techniques and tools to the way they have been working and bring about greater productivity, quality and efficiency.
There is an enormous amount of discussion and literature (in the Software/ Application Development circles?) about different processes (or methodologies), their pros and cons, their challenges, etc. While these articles are right in their own way, in most cases, they preach adoption and acceptance of one process. However, the fact is that rarely does a “one size fits all” approach work for anything – why would software be any different?
It has been an exciting 3 weeks since we launched the GA release of SwiftKanban. Clearly, Kanban for software development and IT teams is being seen as the elusive weapon that promises to take Agile to the enterprise. From the volume of queries and the common themes of the inquiries, it is clear Agile practitioners know what they are looking for and will be demanding the right solution to help them make the transition to being an Agile enterprise.
Digité, Inc., a leading Agile ALM vendor, announced the GA release of Swift-Kanban, the first in their Swift line of products. Swift-Kanban is out of
I am often asked by conference attendees whether Kanban can be used with distributed and offshore teams. It seems that those newer to Kanban concepts are fascinated with pictures of white boards covered in sticky notes, or walls with index cards pinned to them representing work-in-progress (WIP). There seems to be a common assumption that Kanban started with collocated teams doing Agile software development. While some people can see the benefits of limiting WIP even for offshore or distributed teams, it isn’t obvious how it is achieved.
For long, we have heard complaints about Waterfall, CMMI, etc. The complaints vary from too much process to too much documentation to too much overhead, etc. The fact is that like everything else that has been around for a while, the spirit behind these standards/ certifications/ methodologies has been diluted over time. I know of instances where tons of backdated documentation is generated before the day of the CMMI audit! Much worse, we have all heard of instances where certificates are “bought” out.
In the last 2 years, Software-as-a-Service (SaaS) as a delivery model for corporate applications has found a significant amount of support. In the aftermath of the 2008 economic crash worldwide, there has been a surge of interest in exploring the SaaS model for a variety of reasons – mainly around reducing up-front investment typically associated with on-premise license purchases (operating expenses vs. capital expenses), ease of getting up and running, the ability to opt-out if you didn’t like the software, and several others.
Try SwiftKanban Enterprise Plan FREE for 30 days.