Notre avis
Documente les résultats des sessions de raffinement du backlog, y compris les histoires affinées, les estimations, les questions soulevées et les décisions prises.
Points forts
- Capture structurée des décisions et des questions en suspens
- Utile pour les membres d'équipe absents et l'historique du projet
- S'assure que les histoires bloquées sont clairement identifiées
- Facilite la planification des sprints suivants
Limites
- Nécessite une saisie en temps réel pour être efficace
- Peut devenir obsolète si les histoires sont re-raffinées
- Dépend de la rigueur de l'équipe pour être tenu à jour
Pendant ou après une session de raffinement pour capturer les résultats et les partager avec l'équipe.
Pour un suivi détaillé des tâches quotidiennes, préférez un outil de gestion de projet dédié.
Analyse de sécurité
SûrNo execution commands, external data fetching, or destructive operations are instructed. The skill is purely a documentation template and guidance for writing refinement notes.
Aucun point d'attention détecté
Exemples
Create refinement notes for our backlog grooming session held today. Attendees: Alice, Bob, Charlie. Duration: 1 hour. Stories discussed: US-101 (estimated 5 points, ready for sprint), US-102 (deferred, needs more research). Questions: 'What is the expected response time for the API endpoint?' – assigned to Bob, due by Friday. Decisions: We agreed to use REST instead of GraphQL for the new module. Blockers: US-103 cannot proceed until UX mockups are approved (owner: Charlie).I missed today's refinement session. Can you generate a summary from these notes? Date: 2025-03-25. Stories refined: US-201 (8 points, accepted), US-202 (split into two stories). Questions: 'What database to use for analytics?' – owner: Dev team, due next Tuesday. Decisions: Sprint length stays at 2 weeks. Action items: Alice to update the architecture diagram.name: refinement-notes description: Documents backlog refinement session outcomes including stories refined, estimates, questions raised, and decisions made. Use during or after refinement to capture the results and share with absent team members. license: Apache-2.0 metadata: category: coordination frameworks: [triple-diamond, lean-startup, design-thinking] author: product-on-purpose version: "1.0.0"
Refinement Notes
Refinement notes capture the outcomes of backlog refinement (grooming) sessions—what was discussed, what was estimated, and what decisions were made. They serve as a quick reference for team members who missed the session and a historical record of how stories evolved from idea to ready-for-sprint.
When to Use
- During refinement sessions to capture decisions in real-time
- After refinement to share outcomes with absent team members
- When onboarding new team members to explain backlog context
- Before sprint planning to review what's been refined
- When stories need re-refinement due to time elapsed
Instructions
When asked to document refinement notes, follow these steps:
-
Record Session Metadata Note the date, attendees, and duration. This helps track who was part of decisions and when discussions happened.
-
List Stories Discussed For each story, capture the outcome: estimated points, refined status, key discussion points, and any modifications made to the original scope.
-
Document Questions Raised Questions that couldn't be answered in the session need owners and due dates. Don't let them disappear—they often block sprint planning.
-
Capture Decisions Made Record any scope decisions, technical approaches agreed upon, or priority changes. These decisions are valuable context that gets lost without documentation.
-
Note Action Items Any follow-up work needed before stories are sprint-ready: mockups to create, technical spikes to run, stakeholders to consult.
-
Flag Blocked Stories Clearly identify stories that can't proceed until blockers are resolved. Include what the blocker is and who owns resolution.
-
Plan Next Session Note what should be refined next and any preparation needed.
Output Format
Use the template in references/TEMPLATE.md to structure the output.
Quality Checklist
Before finalizing, verify:
- [ ] All discussed stories have outcomes recorded
- [ ] Open questions have owners assigned
- [ ] Decisions are captured with enough context
- [ ] Blocked stories are clearly flagged
- [ ] Notes are understandable to someone who wasn't there
Examples
See references/EXAMPLE.md for a completed example.
Priorisation de Tâches
Productivite
Priorise vos tâches avec les frameworks Eisenhower, ICE et RICE.
Generateur de Rapport Hebdomadaire
Productivite
Generez des rapports de statut hebdomadaires structures et concis.
Rapport de Daily Standup
Productivite
Génère des rapports de daily standup structurés et concis.