Documentation
SolutionDeveloperComplianceProjects
  • Introduction
  • Gitbook Guidelines
  • PRELIMINARY ANALYSIS
    • Project Initiation
    • Business Goals
    • Information Analysis
    • Solutions Evaluation
    • Risk Assessment
  • APPLICATION DEVELOPMENT
    • Scrum Framework
      • Scrum Values
      • Scrum Roles
      • Scrum Compliance
    • User Requirements
    • Product Backlog
      • User Story
      • Story Mapping
      • Grooming
      • Roadmap
      • Best Practice
    • Sprint Planning
      • Planning Inputs
      • Task Definition
      • Task Sizing
      • Sprint Backlog
      • Best Practice
    • Sprint Execution
    • Sprint Review
    • Sprint Retrospective
    • Process Control
      • Sprint Burn-Up
      • Sprint Burn-Down
      • Sprint Velocity
      • Source Control
    • Risk Assessment
      • Data Privacy & Security
      • Postpone the release
      • Lack of participation or engagement
      • Incomplete backlog items
      • Project Scope Creep
      • Third-Party Dependency
      • Integration Issue
      • Outdated Technology
      • Budget & Time Constraints
      • Inadequate Testing
    • User Acceptance
    • Release and delivery plan
    • Literature
  • SERVICE MANAGEMENT
    • Service Lifecycle
    • Receiving Ticket
    • Ticket Management
      • Maintain Attributes
      • Ticket Assignment
    • Troubleshooting
    • Escalation
    • Monitoring
    • Evaluation
    • Risk Assessment
      • Support and Maintenance
      • Insufficient information
      • Misinterpretation of attributes
      • Insufficient Testing
      • Delayed deadline
      • Lack of continuous improvement
      • Lack of Stakeholder involvement
  • REVIEW & IMPROVEMENT
    • Dashboard Analysis
Powered by GitBook
On this page
  1. APPLICATION DEVELOPMENT
  2. Sprint Planning

Planning Inputs

PreviousSprint PlanningNextTask Definition

Last updated 2 years ago

A number of inputs are used in sprint planning to help the development team decide what value it can reasonably offer within the sprint. These inputs for sprint planning are as follows:

  • Product Backlog: The tasks in the Product Backlog have been correctly sized, estimated, and prioritized. They also should meet acceptance criteria.

  • Team Velocity: The amount of work that the team can realistically finish in a single sprint may be estimated in part by looking at its past velocity.

  • Constraints: Any business or technological constraints that might significantly affect the team's ability to deliver should have been highlighted by the team.

  • Team Capabilities: The team should be aware of who is available (and when they are available) for this specific sprint, as well as the skill sets of each team member.

  • Initial Sprint Goal: The business goal that the product owner should have wish to accomplish during the sprint should have been indicated.

(Chapter 19 of “Essential Scrum”,n.d.)