- Most Agile teams will deliver in a short iteration
that's typically called a Sprint.
The term Sprint is from Scrum,
which is the most popular Agile framework.
Now there's nothing in the Agile Manifesto
that says that a team should deliver in Sprints.
In Principle Three,
the Manifesto only suggests that you should deliver work
in a shorter timescale.
The reason that most Agile teams deliver in Sprints
is that they're a very well structured way
to deliver your product predictably and frequently.
Sprints take all of the phases in a Waterfall model
and compress it down to a much shorter timeframe.
This is usually a two week time box.
That's why you'll often hear Agile teams talk about
their two week Sprint.
You'll see a little bit more about Scrum later on.
For now, let's just think about some of the Scrum events.
These are the different things that happen
over the course of your Sprint.
On the very first day of your Sprint,
you'll have a Sprint planning meeting.
This is the time when your team will plan out all the work
you want to finish over the next few weeks.
This shouldn't be more than a two hour meeting.
The key thing to keep in mind
is that this is where you do all of your planning.
Remember that Agile teams don't eliminate planning,
they just focus on short-term planning.
Every morning, the Scrum team should stand up
for its daily Scrum.
This is a 15 minute meeting
where the team coordinates their work.
This is primarily a meeting between the different developers
about the progress they're making on the product.
At the end of the Sprint,
the team will have a Sprint review.
This is a two hour product review
so the customer can offer any feedback on the work
that was done during the Sprint.
Usually the last hour and a half of the Sprint
is dedicated to a team retrospective.
This is when the team reflects
on how they can work better together.
Now, as you can see,
there's a lot of stuff happening in this short Sprint.
You cover a lot of the same Waterfall phases
that you have in a long-term project.
You'll plan in Sprint planning,
then analyze during daily Scrums,
you'll deploy in your Sprint review,
and then you leave some time for process improvement.
It's certainly possible to be an Agile team
and not work in Sprints,
but Sprints have become very popular
because they have a great structure for delivering a product
in a much shorter timeframe.
One thing you want to keep in mind
is that even though you're doing a lot of the same work
as a Waterfall project,
you're not delivering the work in phases.
You might plan at the beginning and deliver at the end,
but most of the work in between is mixed together.
The team should be analyzing, developing
and testing all at the same time.