Agile Manifesto

From agile manifesto we come to know about the importance of executing the
assigned task in a software with agile/fast methods. Earlier the problem was that
companies are so focused on excessively planning and documenting their
software development cycles that they completely lost sight of what really
mattered pleasing to the quality customers. Companies may have mastered and
inherited excellence and integrity but these values do not add to the efficiency
and proficiency which they could use to bring the best out of the company they
can change the life of the people and the clientSo later the need of agile
manifesto emerged in which proper discussions were made in the software
development life-cycle that how we can execute or working in small duration
which is known as sprints so that we can be more effective with our product

What is scrum?
Scrum is a type of a framework that helps us to work together for
example if your team is playing volleyball then they need to work in
coordination and they must play as a teamScrum is most frequently
used by the software development teams they have their own
principles and lessons which can be applied to all kinds of framework
this is the only reason that today is so useful and has become very
popular scrum describes a set of meetings use and rules that work in
concert to help teams structure and manage their work

What are sprints?

It makes projects more manageable allow teams to shift high-quality
work faster and more frequently, and teach them more flexibility to
adapt to change. A sprint is a short time boxed well a scrum team
works to complete asset or amount of work in order to achieve it and
fast. In layman language well make builds in a software life-cycle
then it is recommended to break down the work into small Sprints so
that we can easily manage our work if I talk in a layman language
then springs are nothing but setting a fixed time period for an
assigned work to be completed in order to check and test it if any
mandatory changes or updates required to be implemented with this
we can say what time we can save the production cost we can save the
label on we can come up with the product in the given time at the end
user can easily use it without any problem

Sprint planning
1- Sprint planning is an event in scrum that kicks off the sprint.
The purpose of sprint planning is to define what can be
delivered in the sprint and how that work will be achieved.
Sprint planning is done in collaboration with the whole scrum
team.
2- It can be very much related with sports. Scrum always
encourages sprinting so that we can deliver working software
with an agile pace while learning and improving.
3- In scrum, the sprint is a set period of time where all the work is
done. However, before you can leap into action you have to set
up the sprint. You need to decide on how long the time box is
going to be, the sprint goal, and where you're going to start. The
sprint planning session kicks off the sprint by setting the agenda
and focus. If done correctly, it also creates an environment
where the team is motivated, challenged, and can be successful.
Bad sprint plans can derail the team by setting unrealistic
expectations.

Agile Sprint Reviews

A sprint review is about demonstrating the hard work of the entire
team: designers, developers, and the product owner. It’s a time to ask
questions, try new features, and give feedback. Sharing in success is
an important part of building an agile team.
The three important steps are:
 1- Define done
2- Celebrate team
3- Reach across geographies

This picture of McD is the best example to prove my point.

We love sprint reviews because they protect the health and morale of
the team. Sprint reviews are all about team building. The review it’s
not an exam—it’s a collaborative event across the team in which
people demo their work, field questions, and get feedback.

If a sprint review doesn’t become a positive activity across the team,

it may be indicative of:

 The team taking on too much work and not completing it during
an iteration
 The team struggling with existing technical debt

 Features not being developed sustainably to ensure new bugs are

not introduced into the codebase

 The team’s development practices aren’t as tuned as they could

be
 The product owner is changing priorities within an iteration, and
the development team is sidelined by scope creep.

Scrum Master

1. Standups - Facilitate daily standups (or the daily scrum) as

needed.
2. Iteration/sprint planning meetings – Protect the team from
over-committing and scope creep. Aid in estimation and sub task
creation.
3. Sprint reviews – Participate in the meeting and capture
feedback.
4. Retrospectives – Note areas for improvement and action items
for future sprints.
5. Board administration – Work as the administrator of the scrum
board. Ensure that cards are up to date and the scrum tool, Jira
software or otherwise, is working well.
6. Internal Consulting – Scrum masters should be prepared to
consult with team members and internal stakeholders on how best to
work with the scrum team.
7. Reporting – Regular analysis of burndown charts and other
portfolio planning tools to understand what gets built and at what
cadence.
8. Blockers – The scrum master aids the team by eliminating
external blockers and managing internal roadblocks through process
or workflow improvements.
9. Busy work – If the scrum team isn’t humming, that’s the scrum
master’s problem. Maybe that means fixing broken computers,
moving desks around, or even adjusting the thermostat. Scrum
masters should be comfortable doing just about anything to help their
team and should be not slink away from grabbing coffees or some
snacks if that’s what the team really needs.