Skip to content

Create guidance document for continuing sprints #151

@stevebrownlee

Description

@stevebrownlee

Continuing Your Sprints

After your first Sprint, follow the guidance in this document for all future sprints for a project.

Sprint Planning

  1. Move all remaining items in the To Do column to the Backlog and ensure the tickets remain in priority order.
  2. Take what you learned in your first sprint and adjust the weight of any tickets that are still in progress, and any ones that you want to commit to for the current sprint. Limit yourself to the next 15 tickets that haven’t been weighed.
  3. With each sprint, you will likely increase your capacity by a small amount. Use your completed tickets as your base, and make a commitment for the next sprint that is a few points higher. Over time, development teams realize what their true level of efficiency is and will try to hit that number every time.
  4. Move your newly re-pointed tickets into the To Do column until you have reached the number of points you feel you can achieve. Do them in priority order.

Action Items

  1. Review the Start/Stop columns from your retro board and discuss strategies to ensure your team’s success in implementing them this sprint.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions