Sprint Planning
Assist with sprint planning for Talosix EDC development teams, including pulling stories from Jira, estimating effort, assessing capacity, and generating sprint commitments.
Workflow
Gather Sprint Context: Ask the user for:
- Sprint number/name and dates
- Team name and composition
- Jira project key and board
- Any pre-committed items (carryover, urgent fixes, regulatory deadlines)
Pull Candidate Stories from Jira:
- Backlog items:
project = [KEY] AND sprint is EMPTY AND status = "Ready for Dev" ORDER BY priority, rank
- Carryover:
project = [KEY] AND sprint = [previous sprint] AND status != Done
- Bugs:
project = [KEY] AND type = Bug AND status = Open ORDER BY priority
- Use
getJiraIssue for details on top candidates
Assess and Plan: Apply the framework below.
Output: Generate sprint plan document.
Capacity Assessment
Team Capacity Template
| Team Member |
Role |
Available Days |
Ceremonies (days) |
Net Capacity (days) |
Story Points |
| [Name] |
Dev |
[X] |
1 |
[X-1] |
[X * velocity] |
| [Name] |
Dev |
[X] |
1 |
[X-1] |
[X * velocity] |
| [Name] |
QA |
[X] |
1 |
[X-1] |
[X * velocity] |
| Total |
|
|
|
[Sum] |
[Sum] |
Adjustments:
- PTO / holidays: subtract days
- On-call rotation: subtract ~20% for on-call engineer
- Interview duties: subtract 0.5 days per interview
- Sprint ceremonies: typically 1 day per 2-week sprint (planning, review, retro, standups)
Capacity Buffer
- Reserve 15-20% for unplanned work (production issues, support escalations)
- Reserve additional buffer if active customer UATs or validation activities are in progress
- For sprints near a release: reserve 10% for regression testing support
Story Point Estimation Guide (EDC-Specific)
| Points |
Complexity |
Example |
| 1 |
Trivial |
Config change, copy update, simple UI text fix |
| 2 |
Small |
Single-field addition to eCRF, simple API endpoint change |
| 3 |
Medium |
New edit check type, query workflow enhancement |
| 5 |
Moderate |
New report/dashboard, integration endpoint, form builder feature |
| 8 |
Large |
New module (e.g., lab data import), complex edit check engine change |
| 13 |
Very Large |
Major feature (e.g., ePRO module, randomization engine) |
| 21+ |
Epic-sized |
Break this down further before committing |
EDC Estimation Considerations
- Audit trail: Add 1-2 points for features requiring comprehensive audit logging
- Validation: Add 2-3 points for features requiring IQ/OQ/PQ documentation
- Migration: Add points for data migration scripts affecting live studies
- Multi-study impact: Add points for features that must work across study configurations
- Regulatory review: Add 1 point if regulatory/compliance team review is needed
Sprint Goal Template
A good sprint goal for Talosix EDC teams should:
- Be outcome-oriented, not task-oriented
- Connect to a user or business outcome
- Be achievable within the sprint
Format: "By the end of this sprint, [user/persona] will be able to [capability], enabling [outcome]."
Examples:
- "By the end of this sprint, Clinical Data Managers will be able to configure conditional edit checks using the visual builder, reducing setup time by 50%."
- "By the end of this sprint, the audit trail export will meet 21 CFR Part 11 requirements for customer X's upcoming FDA inspection."
Sprint Plan Output
## Sprint [Number]: [Name]
**Dates**: [Start] - [End]
**Team**: [Team name]
**Capacity**: [X] story points ([Y] available after buffer)
### Sprint Goal
[Sprint goal statement]
### Committed Stories
| # | Key | Title | Points | Assignee | Type | Notes |
|---|-----|-------|--------|----------|------|-------|
| 1 | [JIRA-123] | [Title] | [X] | [Name] | Story/Bug | [Notes] |
**Total Committed**: [X] points / [Y] capacity ([Z]% utilization)
### Carryover from Previous Sprint
| Key | Title | Points | Remaining Effort | Reason |
|-----|-------|--------|-----------------|--------|
### Not Committed (Stretch / Next Sprint)
| Key | Title | Points | Reason for Deferral |
|-----|-------|--------|---------------------|
### Risks and Dependencies
- [Risk/dependency and mitigation]
### Definition of Done Reminders
- Code reviewed and merged
- Unit and integration tests passing
- Validation test scripts written (if applicable)
- Audit trail logging verified (if applicable)
- Documentation updated
- QA tested in staging environment
- Product Owner accepted
Post-Planning Actions
Offer to:
- Update Jira stories with sprint assignment using
editJiraIssue
- Add sprint goal as a comment on the sprint epic
- Identify stories that need further refinement before development starts
1---2name: sprint-planning3description: Help plan sprints for Talosix EDC development with story point estimation, capacity assessment, sprint goal definition, and Jira integration.4---56# Sprint Planning78Assist with sprint planning for Talosix EDC development teams, including pulling stories from Jira, estimating effort, assessing capacity, and generating sprint commitments.910## Workflow11121. **Gather Sprint Context**: Ask the user for:13 - Sprint number/name and dates14 - Team name and composition15 - Jira project key and board16 - Any pre-committed items (carryover, urgent fixes, regulatory deadlines)17182. **Pull Candidate Stories from Jira**:19 - Backlog items: `project = [KEY] AND sprint is EMPTY AND status = "Ready for Dev" ORDER BY priority, rank`20 - Carryover: `project = [KEY] AND sprint = [previous sprint] AND status != Done`21 - Bugs: `project = [KEY] AND type = Bug AND status = Open ORDER BY priority`22 - Use `getJiraIssue` for details on top candidates23243. **Assess and Plan**: Apply the framework below.25264. **Output**: Generate sprint plan document.2728## Capacity Assessment2930### Team Capacity Template3132| Team Member | Role | Available Days | Ceremonies (days) | Net Capacity (days) | Story Points |33|-------------|------|---------------|-------------------|---------------------|-------------|34| [Name] | Dev | [X] | 1 | [X-1] | [X * velocity] |35| [Name] | Dev | [X] | 1 | [X-1] | [X * velocity] |36| [Name] | QA | [X] | 1 | [X-1] | [X * velocity] |37| **Total** | | | | **[Sum]** | **[Sum]** |3839**Adjustments**:40- PTO / holidays: subtract days41- On-call rotation: subtract ~20% for on-call engineer42- Interview duties: subtract 0.5 days per interview43- Sprint ceremonies: typically 1 day per 2-week sprint (planning, review, retro, standups)4445### Capacity Buffer46- Reserve 15-20% for unplanned work (production issues, support escalations)47- Reserve additional buffer if active customer UATs or validation activities are in progress48- For sprints near a release: reserve 10% for regression testing support4950## Story Point Estimation Guide (EDC-Specific)5152| Points | Complexity | Example |53|--------|-----------|---------|54| 1 | Trivial | Config change, copy update, simple UI text fix |55| 2 | Small | Single-field addition to eCRF, simple API endpoint change |56| 3 | Medium | New edit check type, query workflow enhancement |57| 5 | Moderate | New report/dashboard, integration endpoint, form builder feature |58| 8 | Large | New module (e.g., lab data import), complex edit check engine change |59| 13 | Very Large | Major feature (e.g., ePRO module, randomization engine) |60| 21+ | Epic-sized | Break this down further before committing |6162### EDC Estimation Considerations63- **Audit trail**: Add 1-2 points for features requiring comprehensive audit logging64- **Validation**: Add 2-3 points for features requiring IQ/OQ/PQ documentation65- **Migration**: Add points for data migration scripts affecting live studies66- **Multi-study impact**: Add points for features that must work across study configurations67- **Regulatory review**: Add 1 point if regulatory/compliance team review is needed6869## Sprint Goal Template7071A good sprint goal for Talosix EDC teams should:72- Be outcome-oriented, not task-oriented73- Connect to a user or business outcome74- Be achievable within the sprint7576**Format**: "By the end of this sprint, [user/persona] will be able to [capability], enabling [outcome]."7778**Examples**:79- "By the end of this sprint, Clinical Data Managers will be able to configure conditional edit checks using the visual builder, reducing setup time by 50%."80- "By the end of this sprint, the audit trail export will meet 21 CFR Part 11 requirements for customer X's upcoming FDA inspection."8182## Sprint Plan Output8384```85## Sprint [Number]: [Name]86**Dates**: [Start] - [End]87**Team**: [Team name]88**Capacity**: [X] story points ([Y] available after buffer)8990### Sprint Goal91[Sprint goal statement]9293### Committed Stories9495| # | Key | Title | Points | Assignee | Type | Notes |96|---|-----|-------|--------|----------|------|-------|97| 1 | [JIRA-123] | [Title] | [X] | [Name] | Story/Bug | [Notes] |9899**Total Committed**: [X] points / [Y] capacity ([Z]% utilization)100101### Carryover from Previous Sprint102| Key | Title | Points | Remaining Effort | Reason |103|-----|-------|--------|-----------------|--------|104105### Not Committed (Stretch / Next Sprint)106| Key | Title | Points | Reason for Deferral |107|-----|-------|--------|---------------------|108109### Risks and Dependencies110- [Risk/dependency and mitigation]111112### Definition of Done Reminders113- Code reviewed and merged114- Unit and integration tests passing115- Validation test scripts written (if applicable)116- Audit trail logging verified (if applicable)117- Documentation updated118- QA tested in staging environment119- Product Owner accepted120```121122## Post-Planning Actions123Offer to:124- Update Jira stories with sprint assignment using `editJiraIssue`125- Add sprint goal as a comment on the sprint epic126- Identify stories that need further refinement before development starts
nroze22