There is a new (well, maybe not that new) methodology being used in IT to develop applications called “agile.” Agile promises to deliver usable applications quicker and exactly the way the users need them. It has been around for more than 15 years and now seems to be gaining acceptance as a valid approach to IT development.

I learned about agile years ago, and there was something about it that I liked immediately: When business users needed something changed in a project, the developer made the changes. No muss, no fuss; the change got made, and without a lot of time or effort spent documenting the change request, getting multiple approvals, and revising the project timeline. It all might sound like a recipe for catastrophe, but agile has its own set of rules and processes to keep things under control. Without the bureaucracy, IT projects under agile are completed quicker and with higher satisfaction ratings from both the business users and the IT team.

Register or login for access to this item and much more

All Digital Insurance 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