Agile Value



Agile manifesto


The proper relationship between the clients and the customers is one that follows the principles of agile management. This is because it mainly focuses on customers, which is an ongoing process.
Contract negotiations could tend to change during a project life span due to different reasons.This tends to increase customer satisfaction. However, this makes customers prefer agile projects due to the fact that it can control change which eventually produces high value to the projects.
The developer needs to be in constant communication with the customer in order to know the there needs to be a change in the contract i.e. Having a good collaboration with the customers.


Collaboration is that the developer and the customer they both talk and listen to each other. Before there used to be times when the developers negotiated with the customers that what services would be delivered and what won’t be provided. Agile methodology is not this. Agile methodology makes the customer as a part of the project on a constant basis. The pioneers of agile methodology recognized that collaboration creates better and more suitable products.When we talk about agile methodology, we cannot proceed further if we don’t take into account the ‘Agile Manifesto’. On February 2001, a group of 17 methodologists created the Agile Software Development Alliance, or simply Agile Alliance. It was established to tackle the problems faced by software developers. The group also formed a manifesto to encourage improved ways of developing software, and on the basis of this manifesto they also developed some principles that defined the software development processes. The manifesto included four values and twelve principles that formed the basis for the agile movement. One of the four values of the agile manifesto is ‘Customer collaboration over contract negotiations’.
In an agile project, the review by the customer is always built as a part of the project and at the end of each phase the customers get to inspect the product. Even when customer’s minimum money is invested, agile methodology ensures that maximum output is delivered. Agile methodology handles project and product changes in an efficient way.

Links to other agile principles or practices

Communication - Communication is a process of getting messages, ideas, information from one party to the other and thereby getting a feedback in return. There has to be a proper communication link between the customer and the developer in order to achieve the main goal of the project. As seen in the image above, the developer has to keep updating his data with the customer in case there are changes in the contract.

Feedback - This practice is highly linked to the customer collaboration with the developer. Basically, it helps the developer more because, developers tend to need contact, feedback from the customer so as to know if they are on the right track with the project requirements.There has to be a feedback mechanism which would be used to exchange ideas between the stakeholders involved in case there happens to be a change in contract.

Iteration - Developers enjoy working iteration because the delivery of software or milestones can be made to the customers every other week.

Links to PMO knowledge areas (KAs)

Collaboration management - This entails various process to enhance teamwork and partnership between team members and stakeholders involved in the successful delivery of the project.
Contract management - This relates to the agreement made between the developers and the customers. The developers should welcome change at any time and put change ahead of any financial benefits in the project.
Negotiation - Every business deal needs proper contract negotiation between the stakeholders involved, this will allow the deliverables to set according to time and cost which will eventually be financially to the contractor and the customer would end up being a happy customer.

External links

ICN: Driving the deal
European Journal of information systems : Exploring agile values in method configuration
Contract negotiation:Agile development and defining requirement upfront
Pratice for scaling lean & Agile development : Agile contracts primer
Abmysoft, (2014) [Online] Available At: [Accessed: 4 February, 2014].

Thinkinginagile, (2012) [Online] Available At: [Accessed: 4 February, 2014].

Dzone, (2014) [Online] Available At: [Accessed: 4 February, 2014].

John Wiley & Sons, (2014) [Online] Available At: [Accessed: 4 February, 2014].