- 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
- Visual Management
- Visualization
- Webinars
- WIP
February 7, 2018
Recently, there was an interesting problem posed on a project management discussion board. The questioner asked -
January 21, 2018
In a recent post on a technical forum, a Dev manager had the question (paraphrased here) - My organization wants to operate in a Kanban way but maintain the structure of sprints and burn down charts to keep track of progress. Is it ok to do? Is Scrumban the correct methodology? If so, what is the best way to implement it?
January 14, 2018
It has been abundantly clear that in the last 3-4 years, the world of Agile has gradually come to be occupied by Kanban. While there has been a fair bit of the religious battle about Scrum vs. Kanban - which, while doing injustice to both Scrum and Kanban, has certainly helped to keep Kanban under the spotlight - the fact is that most consultants, coaches, and practitioners have been far more pragmatic and sanguine about it.
January 2, 2017
Since the arrival of Scaled Agile Framework in the world market, there have been comparisons ad nauseum between the Scrum and SAFe® frameworks.
