Agile Business Analysis Templates

<aside> <img src="/icons/stars_gray.svg" alt="/icons/stars_gray.svg" width="40px" /> In Agile / Scrum..

each ceremony has a specific purpose and produces different types of meeting notes, which help track progress, decisions, and actions.

Sprint Planning

• Purpose: To define the work to be done in the upcoming sprint and set the sprint goal.
• Notes:
  • Sprint Goal: A concise statement describing what the team aims to achieve in the sprint.
  • Selected Product Backlog Items: A list of user stories / tasks pulled from the product backlog into the sprint backlog, prioritized for the sprint.
  • Task Breakdown: Details on how each PBI will be broken into smaller tasks, including estimated effort and assignments.
  • Capacity Planning: An assessment of team capacity and availability, considering factors like vacations or other commitments.
  • Dependencies and Risks: Identification of any potential blockers, dependencies, or risks associated with the planned work.

Daily Stand-up

• Purpose: To provide a quick status update and synchronize the team’s work.
• Notes:
  • Yesterday’s Work: A summary of what each team member accomplished since the last stand-up.
  • Today’s Plan: An outline of what each team member intends to work on before the next stand-up.
  • Impediments: A list of any blockers or issues preventing team members from making progress.
  • Coordination Needs: Notes on any coordination required between team members, including collaboration on specific tasks.

Sprint Review

• Purpose: To demonstrate the completed work to stakeholders and gather feedback.
• Notes:
  • Demonstrated Features: A summary of the work completed during the sprint, including any product increments or features demonstrated.
  • Stakeholder Feedback: Notes on feedback provided by stakeholders, including suggestions, concerns, and new requirements.
  • Unfinished Work: A list of any PBIs that were not completed and reasons for non-completion.
  • Next Steps: Actions or decisions made based on the feedback, including adjustments to the product backlog.

Sprint Retrospective

• Purpose: To reflect on the sprint process and identify areas for improvement.
• Notes:
  • What Went Well: A list of things that the team feels went well during the sprint, contributing to success.
  • What Could Be Improved: Identified areas where team could improve, including processes, communication, or tools.
  • Action Items: Specific actions the team will take to address the identified improvements.
  • Acknowledgements: Recognition of individual or team efforts that contributed positively to the sprint.

Backlog Refinement

• Purpose: To refine and prioritize the product backlog, ensuring t hat PBIs are ready for future sprints.
• Notes:
  • Updated PBIs: Notes on any updates made to existing PBIs, including clarification, re-estimations, or re-prioritization.
  • New PBIs: A list of newly created PBIs based on stakeholder input, user feedback, or team suggestions.
  • Prioritization Decisions: Decisions made about the order of PBIs, including reasons for any changes in priority.
  • Preparation for Sprint Planning: Identification of PBIs that are ready for the next sprint planning session, ensuring they are well-defined and understood by the team.

</aside>