Agile:-The agile model is a project management approach that breaks projects into phases and

emphasizes collaboration and improvement. It's based on the idea of delivering a project in small parts
over time, rather than waiting until the entire project is complete.

epic:- it is the collections of user stories

it is the large body of the requirement when it will break down into smaller task called as user-
stories.

user story:- It is the collections smaller task

epic:An agile epic is a large body of work that's broken down into smaller tasks, called user stories, to
help manage and organize work in agile and DevOps teams.

sprint:-A sprint is a short, time-boxed period when a scrum team works to complete a set amount of
work. Sprints are at the very heart of scrum ,this set amount of work should be delivered within a
given sprint.

Agile methodology:
===================

1. Scrum method
2. Extreme programming(Xp)
3. Crystal
4. lean
5. FDD(feature driven development)
6. ASDM(Adaptive software development method)
7. DsDm(Dynamic Software development method)
8. Kanban

Scrum:-Scrum is a project management framework that helps teams work together to achieve a
common goal. It uses a set of tools, roles, and meetings to help teams deliver projects efficiently.

A scrum master is a role in agile that ensures the scrum framework is followed and the team is
effective:
Facilitator: A scrum master helps the team understand and apply scrum theory and practice. They also
help the team work more effectively by removing obstacles and distractions.
Coach: A scrum master coaches the team to understand scrum better and continuously improve.
Liaison: A scrum master acts as a liaison between the scrum team and people or teams outside the
scrum team.
Organizer: A scrum master helps the team self-organize and focus on outcomes.
Keeper of the process: A scrum master ensures the team follows the processes and practices that the
team agreed to use.
Meeting facilitator: A scrum master facilitates team meetings like the daily scrum, sprint planning,
and sprint retrospectives.

Product owner:-
In an Agile organization, the Product Owner (PO) is responsible for ensuring that the product
development team delivers maximum value to the business. The PO acts as a liaison between the
product's strategic and tactical plans, and is the primary customer advocate for the team.

Formation of scrum team:

Formation of product backlog

Formation of sprint planning meeting

Design ,coding& testing

Sprint review meeting

Acceptance testing(uAt):

Production

Retrospective meeting

Agile Scrum is a widely used framework for developing, delivering, and sustaining complex products,
particularly in software development. It promotes an iterative, incremental approach to project
management, focusing on flexibility, team collaboration, and continuous improvement. Here's a
detailed breakdown:
Key Concepts in Scrum
1. Agile Mindset: Scrum is based on Agile principles, which emphasize flexibility, customer
collaboration, and the ability to adapt to changing requirements.
 2. Iterative Development: Work is done in small, manageable increments called "Sprints,"
which typically last 2-4 weeks. This allows teams to continuously build and deliver a product,
with regular reviews and adaptations.
Scrum Roles
1. Product Owner:
o Represents the stakeholders and is responsible for maximizing the product’s value.

o Manages the Product Backlog (a prioritized list of work to be done).

o Ensures that the team is working on the most valuable features.

o Makes decisions about priorities but does not micromanage the development team.

2. Scrum Master:
o Facilitates Scrum processes, ensuring that the team follows Scrum practices.

o Acts as a servant leader, helping to remove impediments that block progress.

o Coaches the team in Agile principles, helping them self-organize and improve.

3. Development Team:
o A cross-functional group of professionals (e.g., developers, testers, designers) who
deliver the product increment.
o They are self-organizing, meaning they decide how to accomplish the work.

o Responsible for delivering a potentially shippable increment of the product at the end
of each Sprint.
Scrum Events
1. Sprint:
o A fixed time-boxed period (2-4 weeks) during which work is completed and made
ready for review.
o At the end of each Sprint, the team should deliver a potentially shippable product
increment.
2. Sprint Planning:
o The meeting at the start of the Sprint where the team and the Product Owner decide
what work will be done during the Sprint.
o The team selects items from the Product Backlog (high-priority features) and creates
a Sprint Goal, a concise statement of what the Sprint will achieve.
3. Daily Scrum:
o A 15-minute meeting held every day for the Development Team to synchronize their
work.
o Team members discuss what they did yesterday, what they will do today, and any
impediments blocking progress.
 4. Sprint Review:
o A meeting held at the end of the Sprint where the team presents the completed work
(the product increment) to the Product Owner and stakeholders.
o Feedback is gathered, and adjustments can be made to the Product Backlog based on
that feedback.
5. Sprint Retrospective:
o A meeting held after the Sprint Review where the Scrum Team reflects on how the
Sprint went.
o The team identifies what went well and what can be improved, and plans for
improvements in the next Sprint.
Scrum Artifacts
1. Product Backlog:
o A prioritized list of all the work needed to complete the product. It is dynamic and
can evolve as new requirements emerge or priorities change.
o Items in the backlog are usually written in the form of user stories.

2. Sprint Backlog:
o A subset of the Product Backlog that the team commits to delivering in the current
Sprint.
o Contains all the tasks the team needs to complete during the Sprint to meet the Sprint
Goal.
3. Increment:
o The sum of all Product Backlog items completed during a Sprint, plus the value of
previous increments.
o Each increment must be usable and potentially shippable, even if not all planned
work is completed.
Scrum Values
1. Commitment – Teams commit to achieving the goals of the Sprint.
2. Courage – Team members have the courage to take on difficult challenges.
3. Focus – Teams focus on the work of the Sprint and its goals.
4. Openness – Team members and stakeholders must be open about the work and any
challenges.
5. Respect – Everyone respects each other and the contributions they bring to the team.
Benefits of Scrum
1. Adaptability: Since Scrum promotes iterative development and regular feedback, teams can
quickly adapt to changes in customer requirements or the market.
 2. Transparency: Scrum ceremonies, like Sprint Reviews and Daily Scrums, ensure that
everyone involved has visibility into the progress of the project.
3. Customer Satisfaction: Continuous delivery of product increments allows stakeholders and
customers to see progress frequently, and provide feedback, ensuring that the final product
meets their expectations.
4. Reduced Risk: Regular reviews of progress and work done in small increments help reduce
the risk of failure, as issues are caught and addressed early.
Scrum Workflow Example
1. The Product Owner prioritizes the Product Backlog.
2. During Sprint Planning, the Development Team selects items from the top of the Product
Backlog to work on during the Sprint.
3. The team works in a time-boxed Sprint, delivering a working increment at the end.
4. Each day, the team meets for a Daily Scrum to track progress and address blockers.
5. At the end of the Sprint, a Sprint Review is held to demonstrate the work done.
6. The Sprint Retrospective follows to identify improvements for future Sprints.

The Agile Manifesto was created in 2001 by 17 software developers who sought a better, more
efficient way to manage software development projects. The manifesto outlines the key values
and principles that define the Agile methodology, focusing on flexibility, collaboration, and
delivering working software quickly.
The 4 Values of the Agile Manifesto:
1. Individuals and Interactions over Processes and Tools
o Agile values people and their interactions as the most important part of the
development process.
o Effective communication and teamwork are prioritized over strict adherence to
processes or the reliance on tools.
2. Working Software over Comprehensive Documentation
o Agile focuses on delivering functional software that provides value, rather than
creating extensive documentation.
o While documentation is important, the primary goal is to deliver working software
that meets customer needs.
3. Customer Collaboration over Contract Negotiation
o Agile emphasizes close, continuous collaboration with the customer or end user.

o Instead of rigid contracts, the customer is involved throughout the project, providing
feedback to ensure the product aligns with their expectations.
4. Responding to Change over Following a Plan
 o Agile welcomes changing requirements, even late in the project, to ensure the product
remains relevant and useful.
o Instead of strictly adhering to an initial plan, Agile teams adapt to new information
and evolving customer needs.
The 12 Principles of Agile (from the Manifesto)
1. Customer satisfaction through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development.
3. Deliver working software frequently, with a preference for shorter timescales.
4. Business stakeholders and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Trust them to get the job done.
6. Face-to-face communication is the most effective way to convey information.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. Teams should be able to maintain a
constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity—the art of maximizing the amount of work not done—is essential.
11. Self-organizing teams produce the best architectures, requirements, and designs.
12. Regular reflection on how to become more effective and adjust behavior accordingly.