Below is the Agile Manifesto , according to http://www.agilemanifesto.org/,
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
If you notice the 3rd sentence of the 2nd paragraph, it highlights the fact that customer collaboration is more important & valued compared to contract negotiation. Contract negotiation in this context refers to waterfall project type of contracts whereby every features (requirements & scope ) are expected to be discussed, agreed and signed.
Once signed the client is bounded by the agreement even though as the project progresses, the customer may get more insight into what he really needs. If he wants to modify the requirements, he needs to go through another negotiation process as part of change request so that his "new" requirements is added into the project. Guess what !! The client have to pay for it.
Agile contract works in such way that as the customer gets more insight into his requirements, he can continuously modify the requirements accordingly.
So how does the contract look like? How do you as the client engage the agile software developer or vice-verse ? How do you incorporate the manifesto in your contract ? What should be contents on the contract ? And most importantly what are skill sets that the client should have so that their interest is protected as well to ensure smooth and successful negotiation and eventually the project implementation ?
Do connect with us for more information.
Once signed the client is bounded by the agreement even though as the project progresses, the customer may get more insight into what he really needs. If he wants to modify the requirements, he needs to go through another negotiation process as part of change request so that his "new" requirements is added into the project. Guess what !! The client have to pay for it.
Agile contract works in such way that as the customer gets more insight into his requirements, he can continuously modify the requirements accordingly.
So how does the contract look like? How do you as the client engage the agile software developer or vice-verse ? How do you incorporate the manifesto in your contract ? What should be contents on the contract ? And most importantly what are skill sets that the client should have so that their interest is protected as well to ensure smooth and successful negotiation and eventually the project implementation ?
Do connect with us for more information.
RSS Feed
