approaches to product development that are aligned with the values and principles described in the Agile Manifesto for software development.
Agile Methodology
- Is about being responsive to the market and to the customer by responding quickly to their needs and demands and being able to change direction as the situation demands.
- Be it Information Technology or software development or any other field where there is a flow of work and delivery of work products, Agile methods are applicable.
-Attempt to maximize the delivery of value to the customer and minimize the risk of building products that do not - or no longer - meet market or customer needs.
Application of Agile
is a statement of core values and principles for software development. It is for software development was set up in 2001 and it is a declaration of 4 vital rules and 12 principles that serve as a guide for people in agile software development. It was created by 17 professionals gathered in the snowy mountains of the US state of Utah, convened by Kent Beck.
Agile Manifesto
The first value emphasizes teamwork and communication. We must understand that software development is a human activity and that the quality of interaction between people is vital. Tools are an important part of software development, but making great software depends much more on teamwork, regardless of the tools team may use.
Individuals and Interactions over processes and tools
Documentation has its place and can be a great resource or reference for users and coworkers alike. The main goal of software development, however, is to develop software that offers business benefits rather than extensive documentation.
Working software over comprehensive documentation
Development teams must work closely and communicate with their customers frequently. By listening to and getting feedback, teams will understand what all stakeholders really want.
Customer collaboration over contract negotiation
Changes are a reality in Software development, a reality that your Software process should reflect. A project plan must be flexible enough to change, as the situation demands.
Responding to change over following a plan
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
- Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
- Business people and developers must work together daily throughout the project.
- Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done.
- The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
- Working software is the primary measure of progress.
- Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity-the art of maximizing the amount of work not done -is essential.
- The best architecture, requirements, and designs emerge from self-organizing teams.
- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
12 Agile Principles
What are the Agile Methodologies?
- Scrum
- Extreme Programming (XP)
- Adaptive Software Development (ASD)
- Dynamic Software Development Method (DSDM)
- Feature Driven Development (FDD)
- Kanban
- Behavior Driven Development (BDD)
- A simple framework for working with complex projects, and it was created by Ken Schwaber and Jeff Sutherland.
- Are iterative, meaning the work is divided into iterations, which are called Sprints in this case. It is executed by small teams of between 7-9 people, including a Scrum Master and a Product Owner.
- projects are divided into cycles (typically 2- or 3-week cycles) called Sprints. The Sprints represents a timebox within which a set of features must be developed. Multiple sprints might be combined to form a Release - where formal software/product delivery is made to the customer/market.
SCRUM Methodology
The overall product functionality is broken down by the PRODUCT OWNER into smaller features typically described as:
Epics, User stories - or just Stories.
The Scrum method is characterized by specific ceremonies such as:
Daily Standup meeting, Sprint Review Meeting, Demo to the Product Owner and the Sprint Retrospective meeting.
- A methodology developed by Kent Beck in the early 90s.
- Focuses on enhancing interpersonal relationships as a key to success in software development. It also focuses on promoting teamwork, caring for the learning of developers, and fostering a good working environment. It is characterized by developers working in pairs where one developer programs while the other developer observes; and they switch these roles on a regular basis throughout the Sprint.
- Promotes continuous feedback between the client and the development teams, fluid communication between all participants, simplicity in the implemented solutions and the readiness to face changes. It is especially suitable for projects with indistinct and highly changing requirements and where there is high technical risk.
Extreme Programming (XP) or Paired Programming
Developed by Jim Highsmith and Sam Bayer in the early 1990s. It incorporates the principles of continuous adaptation, i.e., adapt to change and not fight against it. This software uses a dynamic development cycle known as SPECULATE, COLLABORATE, and LEARN. This cycle is dedicated to constant learning and intense collaboration between developers and customers due to the constant change in the business environment.
Adaptive Software Development (ASD)
This is the initiation phase of the project where it is necessary to establish the main objectives and goals of the project by understanding the limitations (risk areas) with which the project operates.
Speculate
This is the phase where most of the development is centered, maintaining coordination between teams that ensures what is learned by one team is communicated to the rest and does not have to be learned again by other teams from scratch.
Collaborate
The last stage ends with a series of collaboration cycles - the job is to capture what has been learned, both positive and negative. This stage is critical for the effectiveness of the project.
Learn
- It was developed in the year 1994 by a group of vendors and experts in the field of Software Development. It focuses on Software projects that are characterized by tight budgets and schedules. It focuses on frequent delivery of product cycles, and development is iterative and incremental.
- Is an agile model that can undoubtedly help organizations that are used to working on projects to change their mentality and way of working to improve their capacity to deliver value and reduce time to market.
Dynamic Software Development (DSDM)
- This methodology is mainly oriented for larger teams with more people than those to whom other agile methodologies such as Scrum are normally applied. It was developed by Jeff De Luca and Peter Coad in the year 1997. This methodology focuses on short iterations, which allow tangible deliveries of the product in a short period of time (2 weeks).
- Is a 5 - stage process, the first 3 of which are sequential and the final two stages are iterative. All agile methodologies follow a series of principles that make them resemble each other.
Feature Driven Development (FDD)
- Was defined by David Anderson in the early-to-mid 2000s, in response to some of the challenges of the various Agile methods, especially Scrum. These methods, while trying to solve the challenges of traditional/waterfall methods, became victim to some of the same challenges themselves.
-The 2-3 week sprint cycle became too long to wait for many business contexts, and the changes required in organization structure ( new roles and responsibilities) and project management/ planning processes put too much strain on organizations, and many teams found themselves not meeting event sprint-level commitments of scope and quality. For most organizations, implementing these methods became very disruptive
- Was defined as the opposite of that - a non-disruptive evolutionary method for improvement, that ultimately enables teams to deliver continuously instead of in time-buckets of 2-3 weeks, get feedback faster and reduce the lead time to deliver value to the customer
- Is a visual system for managing work as it moves through a process. It visualizes both the process (the workflow) and the actual work passing through that process. The goal of this methodology is to identify potential bottlenecks in your process and fix them, so work can flow through it cost-effectively at an optimal speed or throughput.
Kanban Method
Kanban is defined as as a highly effective and efficient production system. The origin of the Kanban methodology lies in the?
Just-in-time (JIT) - devised by Toyota
- Is a behavior-oriented agile development methodology.
- It was created by Dan North in 2003 as an evolution of the TDD (Test-Driven Development) methodology. Dan North aimed to bring non-technical people together in the process of creating the system’s technical functionality. It happens that when we develop software, we involuntarily fail to include business concepts present in the functionality, resulting in a possible flow for recurring and even serious bugs.
- It uses universal language concepts that encourage collaboration between people with or without technical knowledge in a software project. This development process is based on writing test scenarios and features.
Behavior Driven Development (BDD)
Agile and DevOps Compared
Is a philosophy about how to develop and deliver software.
Agile
Agile and DevOps Compared
Describes how to continuously deploy code through the use of modern tools and automated processes.
DevOps
