agile

Assess Agile team maturity and diagnose health to fix anti-patterns.

Updated Jun 19, 2023
One-click install
npx skills add https://github.com/JeroenJochems/modelwise --skill agile-jeroenjochems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agile
Source: https://github.com/JeroenJochems/modelwise/tree/main/.claude/skills/agile
Command: npx skills add https://github.com/JeroenJochems/modelwise --skill agile-jeroenjochems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams improve their Agile software development practices by focusing on core technical disciplines and diagnosing common anti-patterns that hinder productivity and quality.

Core Features & Use Cases

  • Assess Team Maturity: Evaluate technical practices, ceremony effectiveness, and velocity integrity.
  • Diagnose Health: Identify root causes of common Agile issues like declining velocity or production bugs.
  • Fix Anti-Patterns: Provides actionable steps to improve TDD, CI/CD, Definition of Done, and estimation.
  • Use Case: A team is struggling with unpredictable sprint outcomes and frequent production bugs. This Skill can be used to analyze their current Definition of Done, identify missing technical practices like TDD, and guide them on how to implement them iteratively.

Quick Start

Use the agile skill to assess the Definition of Done for a team currently using Scrum.

Frequently Asked Questions about agile

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

FAQPage Schema
How do I fix unpredictable sprint outcomes and frequent production bugs in Scrum?

Unpredictable sprint outcomes and production bugs are fixed by analyzing your Definition of Done and implementing missing technical practices like TDD and CI/CD. This Skill diagnoses root causes and provides actionable steps to iteratively improve estimation accuracy and technical discipline.

Why does declining velocity indicate Agile anti-patterns in my software team?

Declining velocity often indicates Agile anti-patterns such as compromised velocity integrity or unsustainable pace. This Skill assesses team maturity by evaluating technical practices and ceremony effectiveness to diagnose the root causes of declining productivity and fix underlying issues.

What is the best way to assess Agile team maturity for technical practices like TDD and CI/CD?

Assessing Agile team maturity involves evaluating the effectiveness of technical practices like TDD and CI/CD alongside Scrum ceremonies. This Skill diagnoses team health by checking velocity integrity and identifying missing technical disciplines to generate actionable improvement steps.

How do I optimize Scrum ceremonies like standups and retrospectives for better software delivery?

Optimizing Scrum ceremonies requires assessing standups, demos, and retrospectives for anti-patterns that hinder productivity. This Skill guides improvements by diagnosing ceremony effectiveness and providing actionable steps to ensure ceremonies drive technical discipline and sustainable pace.

Can I use this approach to diagnose Agile health for a team struggling with estimation accuracy?

Yes, you can diagnose Agile health by analyzing estimation accuracy, Definition of Done, and velocity integrity. This Skill evaluates technical practices and ceremony effectiveness to identify root causes of estimation issues and provides iterative steps to fix common anti-patterns.

When should I not use Agile practices for software engineering teams?

Agile practices may not suit teams unable to adopt core technical disciplines like TDD and CI/CD, which ensure quality and sustainable pace. This Skill focuses on diagnosing anti-patterns and fixing technical practices, requiring commitment to continuous improvement.