Better Agile Drupal Sprints: leverage Jira for good
summary
Practical checklist for running Drupal sprints with Jira: use JQL queries and saved filters to produce the same sprint lists for everyone; tag demo tickets with a demo label; use Components for site areas (homepage, navigation, content) and a custom developer field to track who actually built work; measure reopen rates (example progression given: ~84% → 60% → 20%) and export via JIRA REST API into Google Sheets for trend reports; templates and a CSV of recommended components live on the referenced GitHub.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 1:18What is Jira
- 3:57About me
- 5:19Agile Development
- 9:57Problems
- 11:20What to focus on
- 12:26Have you used Jira
- 13:00Queries
- 13:54Query language
- 14:44Advanced search
- 16:12Simpler search
- 19:43Sharing filters
- 21:18Show me all tickets
- 22:12Project name
- 22:56Dashboards
- 24:28Labels
- 24:41Demo Labels
- 26:25Demo Components
- 26:35Why Components
- 29:57Shortlist
- 30:40Multiple teams
- 36:29Confluence JIRA
- 41:20Subtasks
- 48:25Spring Planting
- 49:51Burning
- 51:12How does it really work
- 51:35How are you planning
- 56:06Stop ranks
- 58:22Copy and paste
- 59:34Outro
related talks
49mBaking Boards: Tweak the Recipe for Agile Development
26mAgility Works Only If You Are Truly Agile...
06m"Small Changes for Big Wins"
45mThe Agile Architecture Roadmap
46mYour Personal Tech-Writing Agile Manifesto (or: Scrum is not a 4-character word)
35mBuilding and Growing an Agile Team
39mWhen Agile Fails: Working on Large Documentation Projects
12mDelivery metrics - the good, the bad and the utterly ridiculous