Skip to main content

The Agile Manifesto Values and Principles


Agile manifesto refers to the set of rules or values used in an agile project. It contains mainly 4 values:

  1. Individual and Interactions
  2. Working software
  3. Customer collaboration
  4. Responding to change
Over (in traditional project):
  1. Processes and Tools
  2. Comprehensive documentation
  3. Contract negotiation
  4. Following a plan
Let's discuss these four values in details:

Individual and Interactions: Agile development follows a whole team approach and is very people centered. Development team builds software through communication and interaction among different teams and people instead of depending on tools and processes. Individual team member offers a specific skill set and whole team involves in planning the development and testing strategies. 

Working software: It is always beneficial to see the working software instead of heavy documentation. It also helps developers in getting early feedback from the clients which in turn cuts down the cost of accommodating changes. It brings transparency to the project where everybody can see the progress and contribute to it. 

Customer collaboration: In agile, customers are involved in every stage which gives a clear idea about their expectations and what exactly they want to see in the product. Working with customers regularly helps in building the right product and helps in project success. 

Responding to changes: This is the real beauty of Agile development. Project plan should be flexible enough to embrace frequent changes. Both development and testing should be able to respond to the changes in the given time frame.

Here are 12 principles which capture above 4 values of agile manifesto:
  1. Early and continuous software delivery
  2. Accommodating changes even in later stages
  3. Delivering working software at regular intervals
  4. Whole team approach
  5. Support team members and give them the motivational environment to work
  6. Have face to face conversation whenever possible
  7. Maintaining constant pace and sustainable development
  8. Pay attention to technical excellence 
  9. Simplicity (Art of maximizing the amount of work NOT done)
  10. Self organizing team
  11. Regular retrospective meetings
  12. Progress is measured by working software
This data outline is taken from the ISTQB syllabus for Agile certification.
Labels:

Comments

Post a Comment

Share your feedback

Popular posts from this blog

Remove Blanks from Excel Sheet when Excel doesn't recognize field as blank

This is one of the tricks which always helped me in removing the blank fields from an Excel sheet especially when the values are copied from other sources. I have added screenshots of a sample data to show you all the actions step by step. Here are the steps to remove blanks by using one of the special functions in excel: 1. Select your data-set (Select the column which has blank values) 2. Press F5 3. Select "Special". You will see below screen: 4.Select Blanks and click Ok as shown 5. All the blank fields are now selected, you can proceed and delete all of them by selecting "delete" from the home menu.   Here is the final result: I hope this was helpful. Share this with your colleagues and friends to help them out.
Post a Comment
Read more

Benefits of Early and Frequent Feedback in Agile development

One of the reasons why Agile is preferred over traditional development method is "Early and Frequent Customer Feedback". This is not only helps customer to get what he wants but also helps development team to understand the requirement better. There is no room for misunderstandings and delays. so no BAD CUSTOMER SERVICE! In this post, I am going to discuss about some of the major benefits of early and frequent feedback in Agile. One way to get the early feedback is "CI" or Continuous Integration. There are many tools available in the market like Jenkins which help in running automated tests when a change is introduced in the build and give the feedback on the build performance or quality. Below are some of the advantages of early and frequent feedback: Early and regular feedback helps in clearing out the misunderstanding of the requirements. Unlike in traditional method, fixing the issues or requirements change is a lot less expensive. Customer get to see the...
Post a Comment
Read more

Role of a Tester in an Agile Team

Tester in agile is no different from that of traditional tester but in agile, he has to play multiple roles apart from just testing the software. In this post, we are going to discuss about the role of a tester in a project following a scrum life cycle. To make a project successful, testing plays a vital role. In agile, the main idea is whole team approach where testers, developers and business representatives work together as a team. Below are some of the main roles or best practices followed by team members in an agile (Scrum) environment: Cross-Functional: Every team has team members with a specific skill set which they bring to the table. The team work together on Test strategy, Test plan, Test execution and evaluation. Quality is a shared responsibility.  Self-Organizing : There are no leads in Agile. Team is self organized, meaning every team member knows and understands his responsibility and work accordingly.  Co-located : In most of the cases, testers, de...
Post a Comment
Read more