- 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
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.
October 26, 2009
I have spent a lot of time over the last 20 years discussing or working with a large number of our customers who have moved away from the ‘traditional’ methods of managing software projects to a more centralized and “institutional” method. An overwhelmingly large number of these companies have evaluated Project Portfolio Management (PPM) tools as their first option for moving away from their disparate solutions, which usually would be a combination of MS Project on the desktop, email, spreadsheets and a lot of hand-waving!