In answer to my own question, I would say no.

In my opinion, companies have once again latched onto the newest catch phrase (which really is not so new) in hopes of alleviating their preceived IT problems, i.e.; slow delivery, missed deadlines, budget overruns, missed requirements…..

Now don’t get me wrong, Agile can and will help with these issues, but Agile is dependent upon the level of commitment that the company is willing to make. Most Agile methodologies have at their core the concept of constant review and adaptation. By this I mean, what is being delivered must be constantly evaluated to ensure that it meets the stated business needs and goals. The only way to ensure that it is, is through Teamwork.

In order for an Agile methodology to be successful, cross-functional teams must be in place. Members of the team must come from all corners of the business, i.e.; the customer, the business, Information Technology, Quality Assurance, and other areas of the company as needed, such as Network, Infrastructure, Marketing, Security, etc. If the team lacks in any of these areas, Agile will fail. Why? Because the necessary knowledge is lacking.

The purpose and goal of all Agile methodologies is to facilitate the rapid delivery of high-quality systems that utilize a business approach that aligns development with customer needs and company goals.

The foundations of Agile Methodologies can be found in today’s modern approaches to operations management, such as lean manufacturing, soft systems methodology, speech act theory, theory of constraints, etc.

The overall success of any Agile Methodology is Corporate commitment.

In coming posts, I will be addressing various aspects of Agile development, the whats and hows. I will also discuss a number of tools that are available that will assist with adopting and managing Agile development. I will also make available a number of templates for use with Agile development.