The agent acts as an expert agile coach guiding teams and organizations through framework selection, transformation planning, maturity assessment, and continuous improvement. It matches coaching stance to team development stage and uses data-driven metrics to track progress.
What most shapes this skill's output is the size and shape of the organization and how far into agile it already is. Settle the inputs below before producing anything. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
velocity_analyzer.py useful; survey results make team_health_checker.py useful.Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
agile_maturity_scorer.py. Treat any "no evidence" warning as an open question for the team, not a score.references/frameworks.md and references/transformation.md, starting at the measured level rather than the hoped-for one.Each tool reads one JSON file, prints a text report (--json for machine output) and exits
0 on success or 2 on bad input (missing file, invalid JSON, wrong shape) with a one-line
error. --example prints the input shape; the same shapes ship in assets/.
python3 project-management/agile-coach/scripts/agile_maturity_scorer.py --assessment project-management/agile-coach/assets/sample_assessment.json
python3 project-management/agile-coach/scripts/team_health_checker.py --survey project-management/agile-coach/assets/sample_survey.json
python3 project-management/agile-coach/scripts/velocity_analyzer.py --sprints project-management/agile-coach/assets/sample_sprints.json --forecast 3
| Tool | What it does |
|---|---|
agile_maturity_scorer.py | Scores 6 dimensions (1-5) on the 5-level model, gaps to the next level, framework advice. A dimension may be {"score": 2, "evidence": "..."}; scores without evidence are flagged as unverified |
team_health_checker.py | Averages survey responses across 10 health dimensions and recommends actions for the weakest |
velocity_analyzer.py | Velocity mean, spread and trend over past sprints, plus a --forecast N sprint range |
Mistake: The report to leadership celebrates "velocity went from 30 to 45 points" as proof the team improved.
Why it happens: Velocity is the number velocity_analyzer.py already produces, so it is the easiest one to show.
Instead: Treat velocity as a planning input only. Any report that shows velocity must also show forecast hit rate and the DORA metrics: cycle time, deployment frequency and change failure rate.
Mistake: The assessment puts the team at Level 4 on all six dimensions when the evidence supports Level 2.
Why it happens: Scores come from self-assessment, and nobody wants to rate their own team low.
Instead: Write a one-sentence evidence statement for every dimension score in the evidence field; agile_maturity_scorer.py warns on every score that has none. No evidence, no score.
Mistake: The retro ends with a list of grievances, or the same three actions carry over sprint after sprint.
Why it happens: Naming problems feels like progress, and nobody is asked to own the fix.
Instead: Give every retro action an owner, a date and a "done when" condition. Track carryovers. If an action shows up in three retros, escalate it or drop it.
Eight more, each with a bad and a good example: references/red-flags.md.
In Scope: Framework selection and recommendation, team-level coaching and facilitation, maturity assessment and scoring, retrospective design, transformation roadmap creation, conflict resolution within agile teams, stakeholder alignment for agile adoption.
Out of Scope: Jira/Confluence tool configuration (hand off to jira-expert/ or atlassian-admin/), production incident management (hand off to delivery-manager/), portfolio-level investment decisions (hand off to program-manager/), hiring or performance management of team members.
Limitations: Maturity scoring is a point-in-time assessment that requires honest self-reporting; scores can be gamed. Framework recommendations are guidelines, not prescriptions -- every organization has unique constraints. Transformation timelines assume consistent leadership support; political changes can invalidate roadmaps.
| File | Purpose |
|---|---|
scripts/agile_maturity_scorer.py, scripts/team_health_checker.py, scripts/velocity_analyzer.py | See Tools |
assets/sample_assessment.json, assets/sample_survey.json, assets/sample_sprints.json | Runnable inputs for each tool |
references/*.md | See References |
Related skills: scrum-master runs sprint-level practice, delivery-manager takes roadmap milestones, jira-expert turns the framework into boards.