Team talk about Agile Development

Today on Ken´s Class we talked about Agile Development.

Image result for agile

Agile Development is a methodology that was presented in the Agile Manifesto wrote in 2001. Gerardo Juarez and me discussed about the main principles about Agile Development presented in the manifesto. Agile Development was made to make the process of developing a software faster with only the functionla part, it is also about group collaboration and open communication with the customer.

The Agile Manifesto propose 12 principles to follow this methodology:

  1. Customer satisfaction by early and continuous delivery of valuable software
  2. Welcome changing requirements, even in late development
  3. Working software is delivered frequently (weeks rather than months)
  4. Close, daily cooperation between business people and developers
  5. Projects are built around motivated individuals, who should be trusted
  6. Face-to-face conversation is the best form of communication (co-location)
  7. Working software is the principal measure of progress
  8. Sustainable development, able to maintain a constant pace
  9. Continuous attention to technical excellence and good design
  10. Simplicity—the art of maximizing the amount of work not done—is essential
  11. Best architectures, requirements, and designs emerge from self-organizing teams
  12. Regularly, the team reflects on how to become more effective, and adjusts accordingly 
It is also very important to say that Agile Development works in cycles. There is a time set for accomplishing short goals, after the time has ended the team shows their work to the customer so that him/she can give feedback. This cycle repeats until the job is done.

We think that Agile Development is very useful because it is about delivering only the functional part of the software, the design comes later, the simpliest the better. It is also useful when the customer is not sure about what he/she wants because it allows the team to change constantly during the elaboration of the program. Some disadvantages that some people
flickr photo by cote https://flickr.com/photos/cote/63914774 shared under a Creative Commons (BY) license
Continue reading "Team talk about Agile Development"

Team talk about Agile Development

Today on Ken´s Class we talked about Agile Development.

Image result for agile

Agile Development is a methodology that was presented in the Agile Manifesto wrote in 2001. Gerardo Juarez and me discussed about the main principles about Agile Development presented in the manifesto. Agile Development was made to make the process of developing a software faster with only the functionla part, it is also about group collaboration and open communication with the customer.

The Agile Manifesto propose 12 principles to follow this methodology:

  1. Customer satisfaction by early and continuous delivery of valuable software
  2. Welcome changing requirements, even in late development
  3. Working software is delivered frequently (weeks rather than months)
  4. Close, daily cooperation between business people and developers
  5. Projects are built around motivated individuals, who should be trusted
  6. Face-to-face conversation is the best form of communication (co-location)
  7. Working software is the principal measure of progress
  8. Sustainable development, able to maintain a constant pace
  9. Continuous attention to technical excellence and good design
  10. Simplicity—the art of maximizing the amount of work not done—is essential
  11. Best architectures, requirements, and designs emerge from self-organizing teams
  12. Regularly, the team reflects on how to become more effective, and adjusts accordingly 
It is also very important to say that Agile Development works in cycles. There is a time set for accomplishing short goals, after the time has ended the team shows their work to the customer so that him/she can give feedback. This cycle repeats until the job is done.

We think that Agile Development is very useful because it is about delivering only the functional part of the software, the design comes later, the simpliest the better. It is also useful when the customer is not sure about what he/she wants because it allows the team to change constantly during the elaboration of the program. Some disadvantages that some people
flickr photo by cote https://flickr.com/photos/cote/63914774 shared under a Creative Commons (BY) license
Continue reading "Team talk about Agile Development"

A methodology for team work

Agile Software Development is a group of principles created on the idea of collaborative effort and self-organized cross-functional teams.The purpose of creating this set of principles was to make development an evolving process where the teams could improve continously and deliver the product earlier. The main idea is to develop software while helping others, that way everyone limproves and learn new skills.

The methodology was formulated in 2001 in the Manifesto for Agile Software Development. Before setting the principles, they thought about the main ideas wrapping these principles. The first one is about individuals and interactions, everone has to be self-organized, this means that nobody tells you what to do, you control your work. The second one is about working software, when you are presenting your product to the clients it´s more useful if you show them the software working instead of just documents that say how it will be. The third one is about customer collaboration, it´s very important that you have open communcation with the customer so that the final product fulfill their requirements, for that is very important that the customer can participate in the developing process of the product. The fourth and last one is about responding to change, non stopping developing and quick responses. 

Now that the main ideas are set, we can start dictating the 12 principles:
  1. Customer satisfaction by early and continuous delivery of valuable software
  2. Welcome changing requirements, even in late development
  3. Working software is delivered frequently (weeks rather than months)
  4. Close, daily cooperation between business people and developers
  5. Projects are built around motivated individuals, who should be trusted
  6. Face-to-face conversation is the best form of communication (co-location)
  7. Working software is the principal measure of progress
  8. Sustainable development, able to maintain a constant pace
  9. Continuous attention Continue reading "A methodology for team work"

A methodology for team work

Agile Software Development is a group of principles created on the idea of collaborative effort and self-organized cross-functional teams.The purpose of creating this set of principles was to make development an evolving process where the teams could improve continously and deliver the product earlier. The main idea is to develop software while helping others, that way everyone limproves and learn new skills.

The methodology was formulated in 2001 in the Manifesto for Agile Software Development. Before setting the principles, they thought about the main ideas wrapping these principles. The first one is about individuals and interactions, everone has to be self-organized, this means that nobody tells you what to do, you control your work. The second one is about working software, when you are presenting your product to the clients it´s more useful if you show them the software working instead of just documents that say how it will be. The third one is about customer collaboration, it´s very important that you have open communcation with the customer so that the final product fulfill their requirements, for that is very important that the customer can participate in the developing process of the product. The fourth and last one is about responding to change, non stopping developing and quick responses. 

Now that the main ideas are set, we can start dictating the 12 principles:
  1. Customer satisfaction by early and continuous delivery of valuable software
  2. Welcome changing requirements, even in late development
  3. Working software is delivered frequently (weeks rather than months)
  4. Close, daily cooperation between business people and developers
  5. Projects are built around motivated individuals, who should be trusted
  6. Face-to-face conversation is the best form of communication (co-location)
  7. Working software is the principal measure of progress
  8. Sustainable development, able to maintain a constant pace
  9. Continuous attention Continue reading "A methodology for team work"