#agile

Create an agenda for an Agile Sprint Planning meeting. Steps: 1. Review previous sprint metrics (Velocity). 2. Define sprint goal. 3. Backlog refinement (Prioritize user stories). 4. Task estimation (Story points/Poker). 5. Capacity planning (Team availability). 6. Assign ownership of tasks. 7. Identify risks and dependencies. 8. Q&A and final commitment vote. Include timeboxing per section.

Facilitate a user story mapping session for product planning. Process: 1. Define user personas and their goals. 2. Map user activities (horizontal backbone). 3. Break down activities into tasks (vertical stories). 4. Prioritize stories into releases (MVP, V2, V3). 5. Identify dependencies and risks. 6. Estimate effort and value. Use collaborative tools (Miro, Mural). Output: visual story map with clear release plan. Include acceptance criteria for each story. Align team on product vision and roadmap.

Write clear user stories with testable acceptance criteria. Format: 'As a [persona], I want [functionality], so that [benefit].' Example: 'As a returning customer, I want to save my payment information, so that I can checkout faster on future purchases.' Acceptance criteria using Given-When-Then: Given I'm a logged-in user, When I reach checkout with previously saved payment methods, Then I should see my saved cards as options, And I can select one with a single click, And the form auto-fills payment details. Include edge cases: expired cards, declined payments, first-time users. Definition of Ready: story has clear acceptance criteria, designs attached, effort estimated, dependencies identified. Definition of Done: feature tested, documented, deployed, analytics tracking added.

Run effective sprint planning and backlog refinement sessions. Backlog grooming (weekly, 1 hour): 1. Review upcoming stories for clarity and completeness. 2. Add acceptance criteria and designs. 3. Estimate story points (Fibonacci sequence: 1, 2, 3, 5, 8). 4. Identify dependencies and blockers. 5. Split large stories (>8 points) into smaller ones. Sprint planning (every 2 weeks, 2 hours): 1. Review sprint goal and team velocity. 2. Select stories totaling team's capacity. 3. Discuss implementation approach for complex stories. 4. Confirm Definition of Ready for all selected stories. 5. Create tasks and assign owners. Velocity tracking: average story points completed over last 3 sprints. Buffer: reserve 20% capacity for bugs and urgent items. Tools: Jira, Azure DevOps, Linear for story management.

Implement Scrum framework. Elements: 1. Product backlog (prioritized list). 2. Sprint planning (2-4 week sprints). 3. Daily standups (15 min sync). 4. Sprint review (demo to stakeholders). 5. Sprint retrospective (team improvement). 6. Roles (Product Owner, Scrum Master, Team). 7. Burndown charts. 8. Definition of Done. Use tools like Jira. Focus on delivering value incrementally. Adapt based on retros.

I need to write a user story for our development team. The feature is a "password reset" function for our mobile app. Write a clear and concise user story using the standard format: "As a [user type], I want to [goal] so that [benefit]." Then, write a set of specific, testable acceptance criteria for this story.