Lean, Agile, Visual Management from the Trenches
Essential SAFe 4.0 was launched by Scaled Agile Inc. in 2016 as a method to help organizations scale up their existing agile practices. But isn’t that also the reason behind organizations adopting Scaled Agile framework in its glorious entirety?
Usually, the New Year comes with lots of new wishes and resolutions! The January edition of SwiftKanban brings joy and happiness by fulfilling some of your long pending wishes. Read on!
A genuine fear lurks while putting final changes to this article a few weeks before the 45th President of the United States takes office. Becoming the most powerful man on the planet is a fine example of a huge and successful project and his phenomenal success flies in the face of some key takeaways in this article. So, reader’s discretion is advised!
This release introduces several enhancements and new features. Some highlights of this update include, separate Kanban board for To-Do’s, Updated Mobile app and a Simple I-Form Editor.
Many industry experts have come out and pointed possible flaws in the Scaled Agile Framework. For instance, Ron Jeffries has expressed reservation over SAFe®’s approach to resolve inter-team dependencies by holding a multi-team meeting comprising of over 250 people.
With the December update, we have made a huge breakthrough in 2 major areas which have been in our backlog for a long time and have been repeatedly requested by customers across the globe. “Visualization” is the primary goal of Kanban and the Kanban board is the heart of any Kanban system. Any team working with Kanban follows one key principle – to have all the work items visualized on the board. But over a period of time, as more and more item-types get added, it can become difficult for team members to keep track of important work items and their status as they are spread across the board. In large team Kanban systems, this can be a significant issue.
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”.
Hi folks, we hope you are enjoying our previous update with enhancements such as Enterprise Services Planning updates, Upstream Kanban, Portfolio Management and conveniences such as Common Custom fields in the card view in our previous release! We are confident that these powerful functionalities will help accelerate product and services delivery with a clear understanding of customer priorities and your system’s capabilities.
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.
In this update the SwiftKanban team introduces several enhancements and new features. Here are the highlights of this update: Filtering Cards As Per Common Field Values, Analyzing Inactive Cards, Alternative Navigation for Burndown Chart, Filtering Cards Using Multiple Conditions.
Try SwiftKanban Enterprise Plan FREE for 30 days.
