Please wait while the transcript is being prepared...
0:00
Hello. I'm Mike Clayton,
and I'm the founder
of Online PM Courses,
which is an online platform
for learning project management.
In this talk, we're
going to look at
how to manage projects with
the agile Scrum framework.
This isn't a formal
Scrum training process,
but for people who need to
understand how it works
or, perhaps, want an introduction
so that you can decide
whether formal training
is right for you,
this will give you the
overview that you need.
0:30
As an overview of
the Scrum process,
it has five steps.
It starts with a
Product Backlog,
which is an ordered
list of all the work
that the development
team might carry out,
to either improve the product
or to create new components
or new functionality.
I say "might" because Scrum
is an agile framework.
It needs to adapt
to circumstances,
so therefore it
might turn out that,
as events move forward,
some of the ideas we had
for things that we
might want to do
are no longer useful.
However, at the start
of the Scrum process,
the team commits
to a product goal.
The next step is called
Sprint Planning,
which initiates a Sprint,
which is the Scrum
term for an iteration.
This is the primary
event of Scrum,
and I think of it
as the heartbeat
because we have a
series of sprints,
one after another,
of constant duration.
The outcome of
planning each sprint
is a Sprint Backlog,
in which a team commits
to a sprint goal.
The sprint backlog
consists of items
that it draws down from
the product backlog,
and it draws down
only as much work
as they are confident
they can do
within that timeboxed
period, the sprint.
The fifth step is the Sprint,
the fixed length or
timeboxed period of time
where the development team
works on the product,
and this is most commonly
two weeks in duration.
During the sprint,
the team will hold daily scrums
where they check on their
progress towards the sprint goal,
and they ask for and offer help,
if anyone needs it.
At the end of the sprint,
but before the development team
can declare that the
Increment is done,
they need to expose
the work they've done
to inspection or scrutiny
by their users, their customers,
or by other stakeholders.
This is in an event
called the Sprint Review,
and it's the equivalent,
in more traditional
software development,
of user acceptance testing.
Finally, once the team has
delivered the Increment,
they will meet to review
their work, together,
in an event that's called
the Sprint Retrospective.
They'll look for ways that
they can work together
more effectively and more
efficiently in the next sprint.
