Scribd
Upload
16 views

Agile_Scrum Methodologies

Agile methodologies focus on iterative and incremental development, emphasizing flexibility, collaboration, and customer satisfaction, with major companies like Facebook and Google utilizing these approaches. Key stages include requirement gathering, design, development, testing, deployment, and maintenance, with frameworks like Scrum facilitating self-organization and adaptability. Tools such as sprint backlogs, product backlogs, and story points help teams manage tasks and measure progress effectively.

Uploaded by

Jai
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
16 views

Agile_Scrum Methodologies

Agile methodologies focus on iterative and incremental development, emphasizing flexibility, collaboration, and customer satisfaction, with major companies like Facebook and Google utilizing these approaches. Key stages include requirement gathering, design, development, testing, deployment, and maintenance, with frameworks like Scrum facilitating self-organization and adaptability. Tools such as sprint backlogs, product backlogs, and story points help teams manage tasks and measure progress effectively.

Uploaded by

Jai
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

AGILE METHODOLOGY

Agile methodologies are iterative and incremental, which means it’s known for breaking a project into smaller parts and adjusting to
changing requirements.
1. They prioritize flexibility, collaboration, and customer satisfaction.
2. Major companies like Facebook, Google, and Amazon use Agile because of its adaptability and customer-focused approach.

1. Requirement Gathering
In this stage, the project team identifies and documents the needs and expectations of various stakeholders, including clients, users,
and subject matter experts. It involves defining the project’s scope, objectives, and requirements. Establishing a budget and schedule.
Creating a project plan and allocating resources.

2. Design
Developing a high-level system architecture. Creating detailed specifications, which include data structures, algorithms, and interfaces.
Planning for the software’s user interface.

3. Development (Coding)
Writing the actual code for the software. Conducting unit testing to verify the functionality of individual components.

4. Testing
This phase involves several types of testing:
Integration Testing: Ensuring that different components work together.
System Testing: Testing the entire system as a whole.
User Acceptance Testing: Confirming that the software meets user requirements.
Performance Testing: Assessing the system’s speed, scalability, and stability.

5. Deployment
Deploying the software to a production environment. Put the software into the real world where people can use it. Make sure it works
smoothly in the real world. Providing training and support for end-users.

6. Review (Maintenance)
Addressing and resolving any issues that may arise after deployment. Releasing updates and patches to enhance the software and
address problems.

SCRUM
Scrum is a management framework that teams use to self-organize tasks and work towards a common goal. It is a framework within
which people can address complex adaptive problems while the productivity and creativity of delivering products are at the highest
possible value. Scrum is a management framework that teams use to self-organize and work towards a common goal.
 Scrum allows us to develop products of the highest value while making sure that we maintain creativity and productivity.
 The iterative and incremental approach used in scrum allows the teams to adapt to the changing requirements.

SPRINT BACKLOG
A sprint backlog is a subset of the product backlog and lists the work items to complete in one specific sprint. The purpose of the sprint
backlog is to identify items from the product backlog that the team will work on during the sprint. This occurs during the sprint planning
process. These items move from the product backlog into the sprint backlog and shouldn’t change once the sprint begins

PRODUCT BACKLOG
A product backlog tracks what the product team works on. Depending on the size of your organization, you may have one central
product backlog or multiple product backlogs for different teams. The product owner will refine the product backlog periodically to make
sure the most important initiatives are at the top and each initiative has all of the information needed to execute against it.

SPRINT
In software development, a sprint is a fixed period of time when a team works on a product increment. Sprints are typically one, two, or
four weeks long, and are part of an agile testing process. During a sprint, a team will:
 Take items from the sprint backlog and mark them as "in progress" or "done"
 Hold daily stand-up meetings, also known as daily scrums, to discuss progress and brainstorm solutions
 Perform testing activities such as planning, test script updates, and test execution

SPRINT RETROSPECTIVE
The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of
Done. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were
solved. During the Sprint Retrospective, the team discusses:
 What went well in the Sprint
 What could be improved
 What will we commit to improve in the next Sprint

STORY POINT
A story point in Scrum is the unit for the estimation of total efforts that are required to perform or complete a particular task.
USER STORIES: They provide the team with simple explanations of the business’ requirements created from the end user's
perspective.
EPIC: An epic is a collection of related user stories. They are usually large and complex.
TASKS: Tasks are used to break down user stories further. They’re the smallest unit in Scrum that is used to track work. A person or a
team of two people usually work on a task.

VELOCITY
Velocity is the average number of points from last 3-4 sprints. It is measured by the summation of the all approved estimates of the
stories. It gives an idea of the capacity, progress etc.

BEHAVIOR DRIVEN DEVELOPMENT


Behavior Driven Development is a software development approach that allows the tester/business analyst to create test cases in
simple text language (English). BDD is an approach in software development that emphasizes the behavior of an application for
business needs. It was conceived to address issues arising from ill-defined requirement specifications and to align business and QA
professionals. BDD brings together key stakeholders in the Software Development Process, often called the “Three Amigos” – the
Business, Development, and QA teams. Using tests written in plain English allows all stakeholders to understand and agree on the
software’s expected behavior, ensuring that the “right product” is being developed.

The simple language used in the scenarios helps even non-technical team members to understand what is going on in the software
project. This helps and improves communication among technical and non-technical teams, managers, and stakeholders.

You might also like