One of the most difficult principles of Agile Software Development to actually implement is the principle of welcoming change. Two of the statements of values in the Agile manifesto are:

 

  1. Customer collaboration over contract negotiation
  2. Responding to change over following a plan

 

Both of these statements lead to the idea that Agile Software Development welcomes changes from customers and other stakeholders in the project. The Software Development team aims to gather feedback by developing frequent releases through developing the software in a series of iterations. A customer, changing their minds concerning the requirements of a project, isn’t viewed as a problem, which can be in sharp contrast to how a lot of methodologies approach the topic of requirements changing. This incorporation of feedback and customer involvement is an important contribution to the success of Agile methodologies as it leads to the development of software that customers really want. Following this principle is no easy task because the application of this principle needs to start at the very beginning of a project. Guides to implementing Agile Software Development frequently mention the role of the executive sponsor, and other business oriented roles within a company which need to buy-in and support an initiative to introduce Agile Software Development. But in a Software Development company that develops bespoke software directly for customers, the business people in the company need to understand and stick to the principles of Agile Software Development likewise.

There may be support for Agile Software Development in a project of all members but the general perception amongst the business people is that it is one area which the developers do, and does not directly concern them. As much of the material available on Agile Software Development does specifically concern Software Development teams, that is quite an understandable assumption to make. In a company developing bespoke software, the client needs to be made aware of the nature of an Agile Software Development project, and a contract needs to be negotiated that is compatible with the chosen methodology. And it’s the business people who are associated with a project that usually hold the responsibility of setting the customer’s expectations for a project and negotiating the contract. bespoke software development

Customers not really acquainted with Software Development expect that when negotiating a new project with a Software Development company that the process is quite like purchasing almost every other goods and services. The client explains what they need, they agree a price together with a delivery date, and the customer then waits for it to be achieved. The Software Development company will not want to challenge these expectations for the fear of making a customer uncomfortable, and potentially losing their business. This often leads to a binding agreement that mirrors these expectations. The customer continues to expect that the software, by the release date, is going to be ready and do everything the customer wants, and they only need to wait.

 

Leave a Reply

Your email address will not be published. Required fields are marked *