What is Scrum in Software Development?

Scrum is a popular framework that is used whenever we want to develop complex products, Ken
Schwaber and Jeff Sutherland are known as the people who developed Scrum. Scrum is a type
of Agile framework.

Scrum is a framework that helps agile teams to work together. Using it, the team members can
deliver and sustain the complex product. It encourages the team to learn through practice, and self-
organize while working on the problem. Scum is a work done through the framework and
continuously shipping values to customers.

It is the most frequent software that is used by the development team. Its principle and lessons can
be applied to all kinds of teamwork. Its policy and experiences is a reason of popularity of Scrum
framework. The Scrum describes a set of tools, meetings, and roles that help the teams structure. It
also manages the work done by the team

What is a scrum in software development?

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.

Silent features of Scrum

 Scrum is a light-weighted framework

 Scrum emphasizes self-organization

 Scrum is simple to understand

 Scrum framework helps the team to work together

Lifecycle of Scrum
  Sprint: A Sprint is a time box of one month or less. A new Sprint starts immediately after the
completion of the previous Sprint. Release: When the product is completed, it goes to the
Release stage.

 Sprint Review: If the product still has some non-achievable features, it will be checked in this
stage and then passed to the Sprint Retrospective stage.

 Sprint Retrospective: In this stage quality or status of the product is checked. Product
Backlog: According to the prioritize features the product is organized.

 Sprint Backlog: Sprint Backlog is divided into two parts Product assigned features to sprint
and Sprint planning meeting.

SCRUM AND AGILE ARE NOT THE SAME THING BECAUSE SCRUM FOCUSED ON
CONTINUOUS IMPROVEMENT, WHICH IS A CORE FOUNDATION OF AGILE. SCRUM
FRAMEWORK FOCUSES ON ONGOING GETTING WORK DONE.

SPRINTS
With Scrum, a product is built in a series of repetitions called sprints. It breaks down big complex
projects into bite-size pieces. It makes projects more manageable and allows teams to ship high
quality, work faster, and more frequently. The sprints give them more flexibility to adapt to the
changes.

Sprints are a short, time-boxed period for a Scrum team that works to complete a set amount of
work. Sprints are the core component of Scrum and agile methodology. The right sprints will help our
agile team to ship better software.
SPRINT PLAN
Sprint plan is an action in Scrum that kicks off the sprint. The primary purpose of a sprint plan is to
define what can be delivered in the sprint. It also focuses on how the work will be achieved. It is
done in combination with all the Scrum team members.

The sprint is a set of the period where all the work is to be done. Before we start the development,
we have to set up the sprint. We need to describe how long time is required to achieve the sprint
goal and where we will start.

Factors affecting Sprint's planning

o The What: The product owner describes the goal of the sprint and the backlog items which
contribute to achieving that goal.

o The How: Agile development team plans its necessary work on how to achieve and deliver
the sprint goal.

o The Who: The product owner defines the goal based on the value that the customers seek.
And the developer needs to understand how they can or cannot deliver that goal.

o The Inputs: The product backlog provides the list of input stuff that could potentially be part
of the current sprint. The team looks over the existing work done in incremental ways.

o The Outputs: The critical outcome of sprint planning is to meet described team goal. The
product set the goal of sprint and how they will start working towards the goal.
Advantage of Scrum framework

 Scrum framework is fast moving and money efficient.

 Scrum framework works by dividing the large product into small sub-products. It’s like a
divide and conquer strategy

 In Scrum customer satisfaction is very important.

 Scrum is adaptive in nature because it have short sprint.

 As Scrum framework relies on constant feedback therefore the quality of the product
increases in less amount of time

Disadvantage of Scrum framework

 Scrum framework does not allow changes into their sprint.

 Scrum framework is not a fully described model. If you wanna adopt it you need to fill in the
framework with your own details like Extreme Programming(XP), Kanban, Dynamic Systems
Development Method (DSDM).

 It can be difficult for the Scrum to plan, structure and organize a project that lacks a clear
definition.

 The daily Scrum meetings and frequent reviews require substantial resources.

Conclusion
In Conclusion, Scrum is an Agile framework for product development, improving self-organization
and capabilities. It improves productivity and customer satisfaction but it may cause challenges in
handling changes in the mid-sprint and requires additional changes for implementation.

DIFFERENCE BETWEEN AGILE AND SCRUM (AGILE VS SCRUM)

Agile is an iterative approach of software development methodology using short iterations of 1 to 4
weeks. Due to the agile methodology, the development process is aligned to deliver the changing
business requirement. Using Agile methodology, the software is distributed with fasterand fewer
changes.

Scrum is a framework of agile that helps agile teams to work together. Using it, the team members
development, deliver and sustain the complex product. It encourages the team to learn through
practice, self-organize while working on the problem. Scum is a work done through the framework
and continuously shipping values to customers.

Agile

1. Agile is an iterative and incremental approach to software development methodology.

2. In this approach, the leadership plays an important role.

3. Agile software development is highly suitable for the medium or large project.

4. Flexibility is the most significant advantage of agile as it quickly reacts to changes.

5. Agile involves face-to-face communication and collaboration between the members of

various cross-functional teams.

6. Agile development needs frequent delivery to the end user for their feedback.

7. In this development, each step like requirements, analysis, design, are continually
monitored during the lifecycle.

8. The project leader takes cares of all the tasks in the agile method.

9. End-user may give their feedback during the development process. So, the end product will
be more useful.

10. Delivery and update of the software are taking place regularly.

11. Design and execution should be kept simple.

12. The priority of agile development is always to satisfy the customer by providing continuous
delivery of valuable software.

13. Working software is the most fundamental measure of progress.

14. It is best to have face-to-face communication to get as close to the project goal as possible.

Scrum

1. Scrum is a framework of agile methodology. In which incremental builds are delivered to end
user in every two to three weeks.
2. Scrum's team is self-organized, cross-functional team.

3. Scrum is used in the project where the requirement rapidly changes. v

4. A compared to agile it is more rigid. So that there are no chances of frequent change.

5. In daily stand up meeting the teamwork is achieved with a fixed role assigned to team
members, scrum master, and product owner.

6. No need to change many more while implementing scrum process.

7. In this process, a build is delivered after each sprint to the client for their feedback.

8. After every sprint a demonstration of functionality is provided. So that the regular

feedback can be taken before next sprint.

9. There is no team leader, so the entire team handles the issues or problems.

10. When the team completes the current sprint activity, then the next sprint is planned.

11. Design and execution can be innovative and experimental.

12. The daily sprint meeting is organized to review the feedback to decide the future progress of
the project.

13. Working software is not a fundamental measure.

14. The target of the Scrum team is to deliver maximum business value.