---
Video Title: Scrum Development Model
Description: Scrum Development Model
Watch more Videos at https://www.tutorialspoint.com/videotutorials/index.htm
Lecture By: Mr. Arnab Chakraborty, Tutorials Point India Private Limited
---

In this particular video session,
we are discussing Scrum Development Model,

which is a very contemporary development
model.

The meaning of Scrum means, actually
whenever the group of people, they are

exerting their force, they are exerting
their initiatives towards the common goal

is known as a Scrum.

So, now what are the main features of this
Scrum Development Model?

So, originally it was proposed by Swarble
and Biddle.

And this
Scrum distinguishing features are that

development work
is partitioned into packets.

So, whatever is going to get developed, so
they will be divided into certain packets.

And testing and documentation are ongoing
as a product is getting constructed.

It is not like that.

The documentation
and testing will be done at the

end of the, at
the end of the product development.

Allowing with
the product development, this testing and

documentation
will be also in the simultaneous process.

Work occurs in sprints and is derived from
a backlog of existing requirements.

So, there will be one backlog.

So, there is one pile of features which
are unimplemented.

So, that is known as the Feature Backlog
or the Task Backlog.

So, from there you will be taking one of
the, one of the features which is now

supposed to get implemented and sprint
will be exerted on it.

Meetings are very short and sometimes
conducted without chairs.

So, the team members of the scrum team
members or sprint team members,

they used to have one standing meeting
each and every day.

And during the taking the coffee or tea,
they used to go for the meeting.

And during this particular meeting,
they used to discuss what they have done

yesterday, what they will be doing today
and what they are going to do tomorrow.

And demos are delivered to the customer
with the time box allocated.

So, within the time box, within the time
frame, the demos will be given to the

customers on those features who have got
implemented.

And this demonstration and meeting with the
customer will be

done either in the
post-launch session or pre-launch session.

And that is the half
of the day, the corresponding meeting

duration is the
typical duration in our Scrum model.

So, let us discuss this using one diagram
here.

So, here we are having a diagram.

Here you see, we are having this feature
list, which are unimplemented,

and this is known as product backlog.

This is the product owner, and this
product owner will get continuous inputs

from clients, customers, and the team and
other stakeholders.

We know that those people will be known,
those people will be known as a

stakeholder who are
getting positively or

negatively
affected by the execution of a project.

So, this is the product owner,
and he or she will be getting inputs

continuously from end users, customers,
team, and other stakeholders.

So, team selects how much to commit to do
by sprint's end.

So, from here, one
of the product backlog will get

selected, and there is a team who will be
working on that.

So, this is a sprint backlog.

So, whenever this
feature is going to get

implemented,
so there will be certain number of steps.

So, here we are having this tasks,
and which are the task actually,

and it is denoting the sprint backlog.

So, sprint planning meeting will be done
for that.

And this is a sprint backlog from here,
this task will get selected, and sprint

will have a typical duration of 1 to 4
weeks' time.

So, this is a sprint, and it is associated
with two things.

One is the product backlog refinement,
another one is our daily scrum meeting,

that is the artifacts update.

So, I told you earlier, this daily scrum
meeting will be the standing meeting,

and this is a scrum master who will be
supervising with to this, all these scenarios.

So, here we are having this review.

At the end of this particular sprint,
the potentially shippable product will be

obtained in the incremented fashion,
and there is a retrospective is there.

We will be judging the previous history of
different products, whatever the different

tasks and features have got implemented.

So, this is our scrum development model.

We have discussed this one using this
respective very popular diagram,

this one, and it depicts different aspects
of scrum development model.

Thanks for watching this video.

TutorialsPoint.com.

Simply easy learning.