In the rush to complete a project, teams often make hasty decisions, including decisions about which features will be included when the product is released. Rather than making quick decisions, a team should defer a critical decision. Especially if they might learn more throughout the project that will help them make a better decision. In this week's column, Mike Cohn explains the importance of taking advantage of the new knowledge project teams acquire and how this allows them to make better decisions by deferring them.

Just because you have a problem does not mean you are the best person to solve it. In this issue's Technically Speaking, Mike Cohn recommends truly involving users as participants in the process instead of just asking them what they want.

When taking on a new job or even a new project, the sheer number of tasks can seem overwhelming. Find out how a few stacks and applied prioritization can help you cut through the clutter and clear a path to success.

Miracles seldom happen in the software industry, and that is what Big Bang transitions bank on. Utilizing such volatile quick-switch tactics often leave you with nothing more than a costly large crater, so why do some organizations still consider it an option? In this week's column, Peter Clark recognizes the potentially devastating effects of the approach and calls to disarm the process. But if you find yourself having to use the Big Bang, Peter gives tips on how to carefully avoid an accidental detonation.