Skip to content

Sprint Planning #49

Description

@scottpdo

Purpose

Sprint Planning is a collaborative meeting where the team selects priorities from the Sprint Backlog and pulls them into it the Sprint Backlog. Only tickets in which the team agrees they are well-defined enough to be ready for development (the task is clearly defined, estimated, and approved) should be pulled into the sprint. Once the Sprint Planning meeting completes, the sprint work begins.

Outcome

A set of tickets and/or user stories which define the scope of the goal the team has set for the sprint. Remember that the sprint is defined by the amount of time vs. the work to be done because size estimation is exactly that - an estimate.

Duration

Up to 8 hours (often 1.5 - 2 hours)

Team needed

Full project team + client

Best in class examples

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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