juni 24, 2019 • 5 minutes read

Agile: What you need to know [Part 1]

Agile - History And Core Values 

 1. History 
The-history-of-Agile-software-development

Agile was disseminated from the Manifesto for Agile Software Development. According to Jim Highsmith, Agile was released as a method for the Software Development Life Cycle (SDLC) which allows teams to respond to changing requirements, customer unpredictability, and to satisfy customers expectations. The method based on incremental and iterative project work. Agile project management methodology for software development has been around since the 1990s.

Up to now, Agile methodologies have been added to the study program of some universities, for example, universities in the Netherlands, Australia, websites offering online courses such as Future learn, Edx, Coursera, etc.

 2. Agile Manifesto Core Values 

The Core values of Agile Manifesto are:

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

 a.  Individuals and interactions over processes and tools

Agile-Individual-interaction-over-processes-and-tools-sioux-high-tech-software

Software development involves the cooperation of multi-parties: developers, customers, QA, business analysts, project managers, business sponsors, etc. Smooth and effective communication between these parties enhance the understanding of the project, thus help providers to bring out the product closest to customer expectations. Correct understanding makes the use of tools and process progresses effectively in terms of effort, time spending, and costs.

 b.  Working software over comprehensive documentation

Agile-Working-software-over-comprehensive-documentation-Sioux-software-development-company-vietnam

Before Agile, SDLD spent an enormous amount of time on documenting the project process and for one ultimate deliverable. The focus was on documentation to such an extent because the teams wanted to end up with a finished product which was 100% as per the specifications.

While Agile catches up with customer’s expectations and enables flexibility by updating changes and revising the project process in every meeting - mostly referred as Sprint, documentation methodology keeps track of the process based on sources given at the beginning of the project - which is resistant to changes. 

Furthermore, product quality is tested during Sprints to detect flaws at an early stage, which ultimately, reduces cost and time spending. Failure to detect flaws during Sprints causes manifold costs and effort in the next sprint.

 c.  Customer collaboration over contract negotiation

Agile-Customer-collaboration-over-contract-negotiation-Sioux-software-development-company-vietnam

Traditional methodology limits changes in the product design after negotiation, which is a negative point for product development. Agile removes traditional negotiation by engaging customer collaboration during the project.

Collaboration means that discussion is still open during the project. This enables the project team to do a course correction if needed at an earlier stage, to save cost and effort, and helps the clients to re-define their requirements - adjust to market changes for the best outcome.

 d.  Responding to change over following a plan

Customer collaboration over contract negotiation

It can be said that documentation methodology is resistant to changes and perceives them as expensive and time taking. The reason is, this way of management closes negotiation at the beginning of the project. The ongoing process is based on specifications which were documented from the agreement at the beginning. 

Agile, whereas, accepts changes as a normal interfere. It is welcome feedback to improve the project work, a valuable element for the software development project.

Part 2: Agile Methodology Overview (coming soon)

Sioux High Tech Software - with strong competencies in multi aspects in the technological industry, bring you innovative solutions and ultimate products. See our Service site for more information.
Should you have any question regarding technology, feel free to
contact us. 

Reference: 
- Stephen Haunts. (2015). Agile software development succinctly. Syncfusion, Inc. USA.
     Retrieved from www.syncfusion.com
- Jim Highsmith, (2001). History: The Agile Manifesto
     Retrieved from https://agilemanifesto.org/history.html
- Miller, G. J. (2013). Agile problems, challenges, & failures. Paper presented at PMI® Global Congress 2013—North America, New Orleans, LA. Newtown Square, PA: Project Management Institute.
     Retrieved from https://www.pmi.org/learning/library/agile-problems-challenges-failures-5869
- Software testing help (April 23, 2019). Agile Manifesto: Understanding Agile Values And Principles
     Retrieved from https://www.softwaretestinghelp.com/agile-manifesto/


Response