- 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
- 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
February 21, 2018
Transformation approach using the enterprise services view, balancing system demand with capability, planning and prioritization using a visual decision framework, using decision support analytics like probabilistic forecasting and cost of delay.
January 5, 2018
Why this critical visual data integration can fail, tooling and features that need to be built in for success.
December 19, 2017
What are the merits of a Kanban visual integration layer and the necessary capabilities to deliver on this integration.
August 20, 2017
Solving the Insulation Challenge of Managed Transformation
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 25, 2013
There is a lot of attention given to Lean/ Agile product development teams around the work done and the (Lean/ Agile) processes adopted in by the Dev team once a set of features (backlog items) have been identified for a set of sprints (scrums) and/ or Releases.