¿Qué es Kanban y que utilidad tiene en la gestión de proyectos?
1075 items found
Agile methods have the capability to transform IT-business relationships and positively impact value delivery. But IT leaders must be dedicated to the culture change necessary for success. Here are 10 guiding principles you need to know about agile development.
Agile practitioners generally agree that regular retrospectives throughout the project are a good practice; however, many are not seeing the full benefits from the practice. This article shares a number of tips on how to perform retrospectives effectively—getting the maximum value from this important agile process.
A new research report from Software Advice sheds light on which functionalities of agile project management software have the greatest impact on efficiency, and the extent to which agile methods are used in teams beyond software development.
Programs (collections of projects with one business objective) can encounter all kinds of problems. Here are three that you may have seen, and what you can do as an agile program manager.
What does “scaling agile” mean to you? There are two ways to think about scaling: one is moving from one project to a program, the other is sharing agile across the business. Here we talk about moving from a one-team project to agile programs.
Are your project retrospectives getting a bit stale, diluting their effectiveness? Keeping retrospectives fresh for your team requires diligence on your part, but the rewards from continuous improvement are worth it. Here are three fun, simple retrospective techniques that can help get your teams re-engaged.
While there are many governance data points that can be gathered and analyzed to help make go/no-go decisions, there are three in this writer's experience that stand out as being the most important.
Agile approaches allow us to offer ways to manage investment, deliver value and deliver for the organization in various ways. Before you estimate, consider three questions and what they might buy you...
When you’re operating in an Agile environment — or any other software development scenario, for that matter — three factors almost always make the difference between success and failure: domain knowledge, dialogue and deadline pressure. Here, Cutter Consortium consultant and researcher Michael Mah presents his anatomy of a failed project.