Hello, and welcome to Scrum 101. Scrum is a very simple, empirical
process that’s characterized by many feedback loops. Scrum starts with the
roll of the product owner. When the product owner brings to the team a
vision, and some budget, also funding with some ROI. The product owner
then goes away and compiles a list of everything that he or she wants to
see as part of the final product. And that’s known as the product backlog.
The product owner then orders the product backlog in a single rank order,
often from highest priority to lowest priority. Once the product owner has
that product backlog, he or she will then meet with a team as part of the
script animating [sounds like] part one.
As part of script animating part one, the team commits to a certain amount
of work on the product backlog in priority order. So they will start at
the top of the product backlog, and keep committing to work until they have
sufficient work for the duration of a script.
The team will then proceed to script animating part two, which is really a
design station for the team, by the team. And the team will get together
and talk about how it is that they’re going to achieve what they’ve
committed to do.
Now to [inaudible 0:01:34] script animating part two will come a list of
tasks that the team needs to achieve, and this little part is called the
sprint backlog. The team will then go away for the duration of the sprint.
A sprint is a time box period of time, typically anywhere between one to
four weeks. Every day is part of that sprint. The team will have a daily
scrum, or daily stand up.
The team will talk about three things: They’ll talk about what they did
yesterday, what they’re going to do today, and any impediments that they
might have. It’s important to keep the daily stand up, or daily scrum
short. It needs to be no more than 15 minutes in duration. Near the end
of the sprint, the team will have achieved something. They will then meet
with the product owner as part of the sprint review meeting. They will
demonstrate to the product owner what it is that they have achieved. The
product owner can either accept there work, or reject there work.
And finally, at the end of the sprint, the team will have a retrospective.
During the retrospective, the team will talk about what went well, and what
could be improved.
There are a couple of other rolls within scrum, apart from the product
owner. They are the scrum master, and scrum team. The scrum master is
responsible for the scrum process, and making sure that the team are
adhering to the scrum framework. The scrum master is also responsible for
removing any impediments that the team might have. The scrum team are
responsible for any work that they might need to do in order to achieve
The ideal size for a scrum team is seven people, plus or minus two. Scrum
teams are self organizing and cross functional. There are a number of
different charts and graphs that we will use within scrum.
The sprint rundown chart is often drawn as a simple line chart. There is
also the product rundown graph which is typically drawn as a bar chart with
If you’d like to know a little bit more about scrum and understand how we
use the simple framework to build complex products, then please follow on
with this website.
Scrum, Process, Scrum, Agile, Agile, Software, Project, Management, Agile, PM, Agile, Project, Management