Come together as a team, hear what others are working on, communicate challenges and/or major activities, and determine how to assist others. Status on #dev-scrum is not comprehensive but provides collaboration/interaction info and Jira issue numbers.
11:00
12:00
Development Availability Time
Team available via Slack huddle on #back-office-gang for discussion with anyone in the company. Message ahead if you have a specific topic.
Welcome to Sprint X Pre-Planning
Our main goal today is to ensure the team is well prepared for the upcoming sprint.
We'll collaborate to assist the Product Owner and Stakeholders with refining the
backlog, and we'll review the highest-priority Epics with a focus on a few key
objectives:
- Informing our sprint planning decisions
- Building shared context across the team
- Improving the structure of our Epics where possible
If any developers are unable to contribute directly to the highest-priority Epics,
we should use the Dashboards Sprint Planning report as a guideline to ensure their
work still aligns with the company's broader priorities. This is our opportunity to
identify and pursue the work that will provide the greatest value to the team, and
to Path2Response as a whole.
Welcome to the Sprint X Review
Our primary objectives today are twofold:
First, to gather actionable feedback from our Stakeholders to continuously improve
our products.
Second, the Development team will help set clear expectations by showcasing the
work completed and discussing progress made.
As we walk through the deliverables, feel free to provide feedback that can guide
future improvements and ask questions or clarify any concerns that arise. This is
our opportunity to ensure that our work is meeting the needs of our Stakeholders
and remaining aligned with the broader goals of Path2Response as a whole.
Welcome to the Sprint Retrospective.
This is our opportunity to discuss Sprint X, with a specific emphasis on process.
We should discuss things like what we did well, what we should start doing, stop
doing, and any actions we should be taking to improve our process going forward.
Feel free to call out anything that we can do to improve our communications and
processes, as this is our primary opportunity to be the catalysts for change.
Also, we should be calling out our accomplishments made during this sprint so that
we can support the end of quarter and board meetings.
This is a blameless meeting, except for the scapegoat of the sprint [who is...]