- All
- Agile
- Agile ALM
- Agile Marketing
- Agile Metrics
- Agile Tool
- AI
- ALM
- ALM Tools
- Application Lifecycle Management
- Application Portfolio Management
- Artificial Intelligence
- Blogs
- Bytes
- Capacity Planning
- Collaboration
- Essential SAFe
- Everyday Kanban
- Hybrid Agile
- Kanban
- Kanban board
- Kanban cycles
- Kanban for Distributed Teams
- Kanban Tool
- Leadership
- Lean
- Lean ALM
- Lean Software Development
- Lean SSC
- Lean/ Kanban
- Management
- Modern Management
- News and Events
- Newsletter
- Portfolio Kanban
- Portfolio Management
- PPM
- Process Maturity
- Product Updates
- Product Webinars
- Project Management
- Remote Working
- Requirements Management
- SAFe
- Scaled Agile ALM
- SwiftEnterprise
- SwiftEnterprise Updates
- Uncategorized
- Upcoming Webinars
- Visual Management
- Visualization
- Webinars
- WIP
December 18, 2016
One of the important aspects of The Kanban Method is Class of Service (CoS). CoS is a risk categorization mechanism for any work item. We identify 4 Classes of Service – Standard, Fixed Date, Expedite, and Intangibles – depending on customer expectation, value and loss of business value identified as cost of delay. For this blog, cards that are classified as Intangible CoS will be referred to as “Intangibles”.
November 30, 2016
Enterprise/ Portfolio Kanban has for some time provided a visual method of defining and managing portfolios in a much easier manner compared to traditional PPM tools. Kanban Boards can be set up at different levels of the organization to track a portfolio of initiatives, programs, or product releases and their underlying projects or work items can be visualized and tracked far more easily than ever possible traditionally. (To learn more about SwiftKanban’s existing Portfolio Kanban capability, please click here.)
October 27, 2016
Most projects and business activity have a ‘flow’ or a ‘process’, comprising adjacent steps or phases, to produce a product or to deliver a service, to internal customers or external customers. Kanban is the way many teams and organizations visualize their work, identify and eliminate bottlenecks and achieve dramatic operational improvements. Kanban is an evolutionary approach to change and improvement irrespective of the method or framework currently in use.
October 12, 2016
This question comes up not only in Personal Kanban but also for teams and enterprise (portfolio) kanban boards as well. It is a great question – and quite often tricky to answer!
August 21, 2016
David J Anderson's book on Kanban shows us that a way to handle ticket issues is by attaching a color tag to a ticket to make it visible. An issue is a ticket-related event that becomes an impediment to its value flow, such as a defect, insufficient definition, unresolved dependency, etc. What I encounter often is, people have a natural tendency to move the ticket to where the dependency lies.
July 21, 2016
Many teams adopting Kanban come from Agile background. Agile thinking has discouraged the use of Due Dates. Due Dates breed undesirable behavior. Focus on Due Dates results in teams working under significant pressure. Quite often, that translates into short cuts in Design/ Testing activities. The net effect is that work quality is compromised and technical debt piles up.
April 10, 2015
I was in Bangalore for a few days, in part to attend the Agile India 2015 conference. The Sunday morning after the conference got done, I decided to go for a walk. Instead of the picturesque Cubbon Park close by, I decided to go exploring the city. In keeping with the Lean/ Kanban principles discussed at the conference, I decided to maximize flow – and turn in whichever direction the pedestrian crossings were open. That immediately put me on Kasturba Road. I thought fleetingly, “Of course, Kasturba Gandhi (Road) had to be next to her husband Mahatma Gandhi (MG) Road!”