Sprints can be anywhere from two to twelve weeks long. In this Project, I'm using two week Sprints. That is, 10 working days. To keep the number of Sprint work days consistent it's important to tell Project about holidays and other non-working time. Well how do you set your working time in Project? 

Project needs a little coaxing to display features, sprints, and releases the way you probably want to see them. Tracking and communicating progress also works differently in agile projects, compared to traditional project management. Custom fields are the key to making Project agile-friendly. To get to Custom Fields, on the Project tab, click the Custom Fields button. The basic fields you need are really simple. The first custom field we're going to create is one to designate a task as a backlog feature.

As you manage the product backlog, it's helpful to see the releases and sprints that features are assigned to. That way, you can take their feature points and priorities into account when you assign features to sprints. We're gonna create this new view using the feature list view as a foundation.

You can use a custom field to track the sprint velocities a team achieves. We're going to set up a custom field with the formula to do just that. 

Project initiation and planning are just as important in Agile
projects as they are to traditional waterfall projects. In addition to defining
the project vision you define the release strategy and duration. In Microsoft
Project you can set up these tasks the way you would in waterfall projects,
with task dependencies and assigned resources, and let Project calculate the
schedule for you.

 Like releases, sprints also have brief planning and wrap-up tasks. And
they're also linked and scheduled like traditionally scheduled tasks. In
Project you can copy the tasks from your first sprint to set up additional
sprints.

As you manage the product backlog, it's helpful to see the releases
and sprints that features are assigned to. That way, you can take their feature
points and priorities into account when you assign features to sprints. We're
gonna create this new view using the feature list view as a foundation.

The product backlog isn't set in stone for the duration of an Agile
project. Requirements evolve as work progresses which means you might add
features to or remove features from the backlog. In addition you have to
estimate feature points and priorities before you can figure out which features
to assign to each sprint. To manage the backlog we're going to use the Product
Backlog view

During sprint planning, the team decides who's going to work on which
features. In Microsoft Project, you don't have to assign resources to featured
tasks if you don't want to. One reason to do that, though, is if you wanna track
burndown for work hours. Let's assign resources to the features

Because you don't plan an entire Agile project up front, you don't
baseline the entire project at once either. Initially, you can set a baseline
for tasks through the end of the first sprint. When that sprint is done, you
can baseline the next one. Once the baseline is in place, you can update
feature tasks to reflect the progress the team has made. Let's baseline this
project t

Sprints don't take extra time if a feature isn't quite done. When a
feature isn't complete at the end of the sprint, it doesn't get partial credit
for its points. Instead, the feature gets moved to the next sprint. However,
you might reduce the points to reflect the fact that some portion of the work
is already done.

Project comes with several built-in reports that show overall project
performance. Agile projects also use what's known as a Burndown Report to see
how work is going. You can customize Project 2013 graphical reports to show
burndown and sprint velocity. To set up a report in Project 2013 we're gonna
head to the Report tab, then click Dashboards and choose Burndown on the
dropdown menu. The built-in Burndown Report has a chart for work burndown and
task burndown. We're gonna use this report as a basis for our custom report. To
create our custom report, on the Design tab click Manage and then choose Rename
Report. We're not actually renaming the report, we're really creating a copy
with a new name

While we recognize that there are allot of creative, non-repetitive, variable work in agile development projects, many work items, ceremonies, and activities can benefit from systematic, reproducible and standardized tasks test and options that can be captured in customizable checklists prepared and used by empowered agile teams.

The Tracking Gantt  contains vital information on the health of your project and it’s progress.