Agile and Traditional Methodologies

Agile Software Development is a software development method in which requirements and solutions evolve through collaboration between the users and IT specialists in a progressive manner in a highly responsive atmosphere to change.  In the traditional software development method, like Waterfall approach, the general perception is that the software development teams are averse to change and they try to avoid the user groups once the requirements are finalised.

How to make Agile work ?

Since Agile program methodology is primarily around software development, the introduction of this methodology starts from the IT team or IT specialists. While IT teams try their best to push the methodology in their respective organisations, many times, it fails to take off, as the perception on the IT teams remain as people not wanting to respond to changes.  However, if the introduction of the Agile Methodology starts from the user groups or business, then the probability of success is likely to be higher, as the business teams are known for taking calculated risks and succeed, as against the IT teams, who are traditionally risk-averse.

Throughout the project life cycle, the business owners participation and commitment are required for the success of Agile methodology.  This will come more naturally, if the methodology is promoted from the business owners within the organisation.

The KPIs of the business team is very different than that of the IT teams in many organisations.  The KPIs of the business teams are around creating and developing opportunities, revenue and business whereas the KPIs of IT teams, are around delivering the projects on time, within budget for the agreed scope. The business teams have the ability to overcome the misalignment in KPIs quickly, by making necessary changes to the scope, timeline and budget.

In fact, both the methods have their own advantages when deployed in the right opportunity;   both are capable of delivering maximum benefits to the organisations.  The IT teams in the same organisation can follow both the methodologies under two different groups, keeping in mind the right priorities, in terms of

• INTERACTIONS over Process and Tools
• WORKING SOFTWARE over Documentation
• CUSTOMER RELATIONSHIP over Contract
• RESPONDING TO CHANGE over Plan and finally
• BUSINESS VALUE over everything else …..

Simply, keeping the customer or business in front will increase the probability of success for the project team.

For more information kindly contact rv@bizintek.com.my