agile-methodology

Automate agile ceremonies and backlog management for Scrum and Kanban teams.

111|18|Updated Dec 17, 2025

Search Tags:#planning #Scrum #Kanban #Agile

Ready to run

npx skills add https://github.com/dralgorhythm/claude-agentic-framework --skill agile-methodology

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agile-methodology
Source: https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/product/agile-methodology
Command: npx skills add https://github.com/dralgorhythm/claude-agentic-framework --skill agile-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides agile principles, Scrum ceremonies, and Kanban basics to improve team delivery.

Core Features & Use Cases

Ceremonies: Sprint planning, daily standups, reviews, and retrospectives.
Artifacts: Product backlog, sprint backlog, and increments.
Use Case: Run a 2-week sprint with defined backlog items.

Quick Start

Create a sprint plan and backlog items for a sample feature.

Frequently Asked Questions about agile-methodology

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

FAQPage Schema

How do I structure sprint planning and backlog management for my team?▼

Sprint planning organizes work into defined iterations with backlog items prioritized by value. Break your product backlog into sprint backlogs, assign story points or estimates, and plan ceremonies—planning, daily standups, reviews, and retrospectives—to coordinate delivery, track velocity, and iterate on process continuously.

What's the difference between Scrum and Kanban for team coordination?▼

Scrum uses time-boxed sprints with defined ceremonies and artifacts; Kanban uses continuous flow with WIP limits and lead-time metrics. Both reduce coordination inefficiencies. Choose Scrum for predictable iteration cycles and defined roles, or Kanban for steady-state delivery with flexible prioritization and faster feedback.

How do I measure team performance in agile—velocity, lead time, or cycle time?▼

Velocity tracks completed story points per sprint for capacity planning; lead time measures request-to-delivery duration; cycle time measures active work duration. Use velocity for sprint forecasting, lead and cycle time for bottleneck detection and process improvement across retrospectives.

Can I run agile ceremonies and backlog rituals without dedicated roles?▼

Agile ceremonies—sprint planning, standups, reviews, retrospectives—work best with defined roles: product owner prioritizes backlog, Scrum master facilitates ceremonies, and developers execute. Distributed roles reduce clarity and decision speed; even small teams benefit from explicit ownership to improve coordination and continuous improvement.

What agile metrics should I track to improve sprint execution?▼

Track velocity for capacity trending, WIP limits for flow efficiency, lead time and cycle time for delivery speed, and sprint burndown for progress visibility. Retrospectives analyze these metrics to identify process friction and plan incremental improvements across planning, standups, and reviews.