Table of contents
No headings in the article.
The Agile Manifesto consists of four key values:
1 Individuals and interactions over processes and tools. 2 Working software over comprehensive documentation. 3 Customer collaboration over contract negotiation. 4 Responding to change over following a plan. . Agile software development is a value-driven discipline. At its root, agile values human creativity and ingenuity over all else.
It also calls for individuals and interactions to be valued equally, or even more than processes and tools. . Agile Value 1: Individuals and interactions over processes and tools.
This principle is about valuing people before valuing processes and tools.
The focus in this core value is on interactions between people when doing work – to create better products. We can increase productivity if we work together on building better products, not only for individuals. . Agile Value 2: Working software over comprehensive documentation.
This principle values working software more than comprehensive documentation.
The main focus of this core value is on how to build better products with an agility that can rapidly respond to change.
Documentation sometimes does not help in responding to change efficiently. Instead it slows the process down. . Agile Value 3: Customer collaboration over contract negotiation.
Collaborate with customers before doing work.
The focus of this core value is on building better products with an agility that can rapidly respond to change. Contract negotiation sometimes limits the ability of organizations to be able to work in agile ways. . Agile Value 4: Responding to change over following a plan.
This final principle values responding to change more than following a plan.
The focus of this core value is on the purpose of agile which is to respond to change. . Cons of Incorporating Agile values
There aren’t many obvious con agile values. However, over time some of the drawbacks that have been acknowledged are as follows.
Cons of customer collaboration: Customer collaboration can lead to a slow product development process and a high project risk, if the customer, who is also the product owner, does not have a good understanding of what they want or how it should be developed. On larger projects with multiple user groups, this becomes an even more significant problem. In this case, there is a need for an effective product owner.
Cons of responding to change: Responding to change can also slow down the process. For example, it could be very difficult for the team to plan and estimate the work if no one knows what they will be doing until just before they do it. The inability to plan the work causes the iteration to end up with a lot of unfinished work.
Cons of working software: Not all code is created equal. It takes a long time to hand off working software from one group to another. Without an effective team, it could end up taking more resources and time to create the working software than if the work were done within one team. The slow down in development can lead to high costs for both teams.
Cons of individuals and interactions: In order to work as a team, the team needs to know how the individuals work. In agile development, teams are defined by who they are made up of instead of what they do. This leads to groups that don’t understand how others think and work which leads to less effective communication.
. Guidelines to Keep In Mind While Employing Agile Values
Agile values are not a strict process or methodology that order specific ways of creating or developing a product like rules, rather they are the underline, guiding ethos, or the way of working.
Agile values should be interpreted by teams in a way that works for them, values should not be implemented as a set of rules.
Agile values work best when teams decide which value is applicable to them and how they should use it. Teams should continuously learn and improve.
Agile values are not rules, if teams feel that one of the values can hamper their progress then they should ignore or change it.
Agile values are not a strict process or methodology order, Agile teams can follow processes and methodologies as long as they also work according to the values.
Agile values should be interpreted by teams in a way that works for them value’s should not be implemented as a set of rules.
Agile values work best when teams decide which value is applicable to them and how they should use it.
. Resources: 1-questionpro.com/blog/agile-values/amp 2-productboard.com/glossary/agile-values