Going the Agile way! Are you ready for it?

The majority of IT Organizations boast that now they are agile in some manner. Not every organization is ready to adopt to Agility as it requires time and patience to deliver result.

Agile can also put pressure on individuals and teams to deliver. Agile sprints typically last two to three weeks, and working code and demonstrations are staples at the end of those sprints. But performing one or more demos of the results may not be realistic.

Agile! It’s cool; It delivers BUT it’s not for everyone

Agile has the flexibility to adapt to a wide variety of projects, and it is certainly what your team should do under most circumstances. However, due to training or cultural issues, or because the technical aspects of a project don't easily lend themselves to many of the accepted agile practices, agile may not be the best fit.

If a software system requires a lot of infrastructure, it won't be possible to deliver working software at the end of every sprint.

Projects that include a substantial amount of behind-the-scenes code, such as embedded systems, may not be amenable to having buildable and working code at the end of each sprint. Code for safety-critical systems, such as modern automobiles or airliners, can involve many teams whose code isn't functional until it has been integrated into the operational system.

Don't fall in the trap of trend! think and decide what works for you.