In: Computer Science
Agile Manifesto has Twelve principles and Four Values.
Outline three Principles or Values and show how they apply to either Scrum or Kanban.
4 values of Agile Manifesto
That is, while there is value in the items on
the right, we value the items on the left more.
1. Individuals and interactions over processes and tools
This value of the Agile manifesto focuses on giving importance to communication with the clients. There are several things a client may want to ask and it is the responsibility of the team members to ensure that all questions and suggestions of the clients are promptly dealt with.
2. Working product over comprehensive documentation
In the past, more focus used to be on proper documentation of every aspect of the project. There were several times when this was done at the expense of the final product. The Agile values dictate that the first and foremost duty of the project team is completing the final deliverables as identified by the customers.
3. Customer collaboration over contract negotiation
Agile principles require customers to be involved in all phases of the project. The Waterfall approach or Traditional methodologies only allow customers to negotiate before and after the project. This used to result in wastage of both time and resources. If the customers are kept in the loop during the development process, team members can ensure that the final product meets all the requirements of the client.
4. Responding to change over following a plan
Contrary to the management methodologies of the past, Agile values are against using elaborate plans before the start of the project and continue sticking to them no matter what. Circumstances change and sometimes customers demand extra features in the final product that may change the project scope. In these cases, project managers and their teams must adapt quickly in order to deliver a quality product and ensure 100% customer satisfaction.
12 Principles of Agile Manifesto
1. Customer satisfaction through continuous delivery of the product
In the case of traditional management methodologies, customers get to see the product only after completion and when several tests and quality checks have been performed. This not only keeps the customers in dark but also makes it problematic for the team members to introduce any changes in the product.
In order to keep the customers happy, it’s important to continuously engage them with a working version of the product. Show small increments every sprint planning and make changes as required.
2. Divide large chunks of work into smaller and achievable tasks for quicker completion and easier integration of changes
Handling a huge and complex task would be both time and energy-consuming while managing project tasks. A better way is to divide the task into smaller parts that can be easily completed. The customers would always be kept in the loop and it would be easier for the team members to identify potential bottlenecks and handle any potential delays.
3. Adhere to the decided timeframe for the delivery of a working product
The Agile philosophy favors a smaller time frame and delivers working software frequently. This iterative process requires team members to continuously improve their performance.
4. All stakeholders must frequently collaborate to ensure that the project is going in the correct direction
A major problem associated with traditional project management methodologies is that the project stakeholders are often oblivious to the development stages of the project. The Agile principles encourage all stakeholders to remain involved in all stages of the project in order to ensure constant feedback and a valuable end product.
5. Create a supportive environment to motivate team members and encouraging them to get the job done
It is the responsibility of the project manager to create a motivating environment and support where members are not afraid to voice their opinions and give suggestions for the betterment of the team’s performance. Giving the team members the confidence and motivating them would cause their overall performance to improve significantly which will ultimately be better for the project.
6. Prefer face-to-face communication over other methods
In the Agile manifesto, a lot of importance is given to effective communication between the involved parties. For effective communication, methods like memos and email are not preferred and more importance is given to face-to-face communication. This is now easier because of the advances in communication technologies. All stakeholders can now have a meeting through video conferencing rather than coming to the office for a short meeting.
7. Working software is the primary measure of progress
The only factor to measure success is the delivery of a working product that satisfies the customer. Before Agile, there were many measures of success and that resulted in a drop in the quality of the final product.
8. Try to maintain a constant pace of development
A repeatable and iterative pattern should be established where sustainable development of the project takes place at a constant rate. This prevents the team members from being overwhelmed and over-stressed, while the project keeps on progressing at an acceptable rate.
9. Maintain the quality of the product by paying attention to technical details
Providing value to the customer is the primary objective of any Agile team. It’s extremely important to have a multi-skilled team that can handle all the technical aspects of the project and provides the opportunity for continuous improvement.
10. Maintain simplicity
In each time box, the tasks at hand should be the main focus of all team members. Too much planning and adding extra features to the product should be avoided during the development.
11. Promote self-organization in the team
A self-organized team with decision-making powers would simply perform better because the responsibility of satisfying the customers will on the team members, rather than a single project manager.
12. Regularly reflect on your performance for continuous improvement
Agile methodologies stand on the concept of iteration, where teams learn from their past mistakes and continuously improve their performance. Project managers should promote sessions where the whole team reflects on their performance and discuss ways to improve their technical and management skills.