Quite often software development projects are set up to execute work using agile methodology, like Scrum, but not setting things up in the right fashion often leads to chaos.

Although there is ample information on Scrum (and it’s not exactly rocket science), there are cases where projects have been paralyzed. This article discusses common reasons for such failures and how to avoid them.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access