Exercise - Plan a sprint using Delivery Plans

  • 10 minutes

Now you can create a delivery plan and use it to plan a sprint in Azure DevOps.

The Tailspin team is eager to see how Delivery Plans is going to work. They already have two teams with sprints set up in Azure DevOps, so now they can review and optimize the work schedules.

To do this, you:

  • Create a delivery plan.
  • Add team sprints and milestones.
  • Rearrange work items to fit the overall schedule.

Create a delivery plan

You create a delivery plan from the Delivery Plans tab of Azure Boards. You can create as many delivery plans as you need to manage different aspects of your organization.

  1. From Azure DevOps, navigate to your project.

  2. Under Boards, select Delivery Plans.

    Screenshot of the delivery plans option in the dropdown menu.

  3. Select New plan.

  4. In the form, enter these fields:

    • Name: Space Game Delivery Plan.
    • Select the Backlog items backlog for the Space Game Web Team.
    • Add the Space Game Engine Team's Backlog items backlog using the Add team option.

    The Web team and the Engine team share a common set of backlog items.

    Screenshot of the final delivery plan settings.

  5. Select Create.

    Note

    The team project generated for this module uses the Scrum process, not the Basic process used in other modules in this learning path. While the Basic process uses Issues, the Scrum process uses Backlog items, which are functionally the same for the purposes of this module. You can use Delivery Plans with either process.

Add schedule milestone markers

Milestone markers can be added to the delivery plan as reference points. They help you plan work within the context of significant or external dates. Let's add a few markers now. To do so:

  1. Select your delivery plan.

  2. In the top right toolbar, select Settings, and then, on the Plan settings pane, select Markers.

    Screenshot of selecting the Markers tab from the delivery plan settings.

  3. From the Markers tab, select Add marker.

  4. In the form, enter these fields:

    • Date: Select a date one week from now
    • Label: Cliffchella
    • Color: Red

    Screenshot of adding the milestone marker for the Cliffchella event.

  5. Repeat the process to add markers with labels, dates, and colors:

    • Beta: five weeks from today (blue)
    • Annual company party: six weeks from today (green)

  6. Select Save.

  7. Use the Scroll calendar and Zoom out controls to bring all markers into view.

    Screenshot of bringing all four markers into view.

  8. Select the Beta marker at the top of the design plan. A solid line shows the boundary of the beta milestone.

    Screenshot of selecting the Beta milestone to show the boundary of the beta milestone.

Optimize the work schedule

  1. Notice that there's a work item for the Web team to Integrate with beta DB. It's scheduled for completion before the beta will be ready. This is a problem because this work item is dependent on that beta.

  2. Drag the integration work item from Sprint 3 to Sprint 4 to ensure that its dependency will be available.

  3. This change opens a significant amount of bandwidth in Sprint 3. Because that time is now available for productive work, drag the two Fix work items from Sprint 4 back into Sprint 3.

    Screenshot of the direction in which to move work items.

Your final sprint plan should look similar to this:

Screenshot of the optimized work schedule.

Although the team has made some adjustments, they haven't addressed all the dependency issues that are identified in the delivery plan. In the next unit, they learn more about dependencies and how to resolve the issues that can occur in the schedule.