- 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
August 17, 2017
David Anderson is a thought leader and pioneer in the field of Lean/ Kanban for Software Development and managing effective software teams. (View David’s profile) We are honored to publish this blog post from David where he compared Enterprise Services Planning (ESP) with Kanban.
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.)
September 18, 2014
How do you design your first Kanban board? This thought was triggered by a question posted by someone who works at an agency and were trying to figure out the best way to set up their Kanban board. The agency appears to be a small team working on multiple customer assignments and they wanted to use Kanban to track all of the work they do.
February 11, 2014
This is a common dilemma for teams wanting to use Kanban for 'fixed price, fixed cost" projects. On the one hand, you have a business demand to commit up-front to a timeline and scope (and cost) to deliver a product; on the other hand, you have a promising tool – Kanban – that completely does away with any concept of time (or scope) bucketing but yet promises higher value and better quality to the customer.
February 10, 2014
Hello again! We've improved our card search capabilities with this update and you now have the ability to track throughput for every Smart Lane!
February 6, 2014
Sometime back, we published a blog post Due Dates in Kanban Systems – which drew some flak from some folks who objected to the line of reasoning in that post. However, one of the commenters made a good point – that it made sense to have Due Dates in a Kanban system if in fact the process being visualized on the Kanban board already needed Due Dates.
January 20, 2014
Projects are often executed by dynamic teams. They start with a small core team and as the project gains momentum, add resources over time. This is commonly seen in IT service organizations that do fixed price projects. Fixed price projects have a defined scope that needs to be delivered within a contracted budget and within a negotiated timeline. For the purpose of this experience report, “Dynamic teams” or “Fixed Price projects” will be used interchangeably.
December 31, 2013
Energetic, responsive, trying harder - those were some of the best compliments we received from our customers. As one of them, who switched from a competing product to us, said, "It looks like you guys are always trying harder and better than the rest of them." Absolutely!
