sprint-planner

Generate structured sprint plans with Modified Fibonacci estimates and capacity alignment.

132k|19.4k|Updated Apr 29, 2024
One-click install
npx skills add https://github.com/Shubhamsaboo/awesome-llm-apps --skill sprint-planner-shubhamsaboo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planner
Source: https://github.com/Shubhamsaboo/awesome-llm-apps/tree/main/awesome_agent_skills/sprint-planner
Command: npx skills add https://github.com/Shubhamsaboo/awesome-llm-apps --skill sprint-planner-shubhamsaboo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies agile sprint planning by providing a structured approach to estimating stories, defining sprint goals, and balancing backlog capacity.

Core Features & Use Cases

  • Story Estimation: Apply a Modified Fibonacci scale (1, 2, 3, 5, 8, 13, 20) for consistent sizing.
  • Capacity & Velocity: Compute team capacity and velocity to plan realistic sprints.
  • Sprint Goals & Backlog: Define sprint goals and align backlog items; identify risks and dependencies.
  • Use Case: A product team planning a 2-week sprint can generate a sprint backlog with estimates and capacity.

Quick Start

Plan Sprint 1 for a two-week period with a capacity of 20 points and a backlog of 5 stories.

Frequently Asked Questions about sprint-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a sprint with capacity planning and story point estimates?

Sprint planning with capacity planning and story point estimates involves generating a structured sprint backlog by applying a Modified Fibonacci scale (1, 2, 3, 5, 8, 13, 20) to size stories and balancing them against computed team velocity and capacity limits.

What is the Modified Fibonacci scale for story point estimation in scrum?

The Modified Fibonacci scale for story point estimation in scrum is a sequence of numbers (1, 2, 3, 5, 8, 13, 20) used to size backlog items, providing consistent relative estimates that reflect increasing uncertainty as story complexity grows.

How do I calculate team velocity and capacity for a two-week sprint?

Calculating team velocity and capacity for a two-week sprint requires evaluating historical sprint data and available team hours, then aligning the prioritized backlog items until the total story points match the calculated capacity limit.

Can I use this for backlog grooming and defining sprint goals?

Yes, you can use this for backlog grooming and defining sprint goals, as the process includes aligning backlog items with articulated sprint goals and identifying risks and dependencies during the grooming session.

What's the best way to articulate a definition of done for sprint deliverables?

The best way to articulate a definition of done for sprint deliverables is to explicitly list the completion criteria for each backlog item during sprint planning, ensuring all team members agree on the expected quality and scope before work begins.