You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Team BTR,
This retro was concluded as an inspect and adapt event so we could address any lapses and
Inspect and adapt as a team for better efficiency.
As we reflected on this sprint progress with the team and on this project, we identified action points.
how we can get better and become a high performing team.
During the Retrospective Session we agreed on the following Action Points as an action point for the team .
Positives?
• Sprint Planning.
• Each team member helping others.
• Meeting with PIA
• Accessibility Plan
• Meeting with Dev for refinement.
• Focusing on the right things.
What didn’t go well :
• PO sign off.
• Capacity planning
• Not enough time for sprint completion
Actions to take.
• check with PO before closing tickets. ( PO)
• SM For the planners to know the calendar (e.g., stat holidays) (SM)
• Monitoring Capacity (PO, SM)
• PO to get a new Laptop. (PO)
• Factor in time for Ops support (SM)
• Info and sharing with Policy (PO)
These are our action points and have been assign owners, as we
improve as a team we will adapt to these suggestions and check its effects on our next iteration.
Thank you for being part of the journey so far.
We do appreciate any feedback and any other opinion that was not captured.
Festus Odiley
Scrum Master RTR
“ Agile is simple-It is just not easy”
The text was updated successfully, but these errors were encountered:
Hi Team BTR,
This retro was concluded as an inspect and adapt event so we could address any lapses and
Inspect and adapt as a team for better efficiency.
As we reflected on this sprint progress with the team and on this project, we identified action points.
how we can get better and become a high performing team.
Mural Link
19.4 Retrospective • CITZ – ServiceBC – BCROS (mural.co)
Attendance
During the Retrospective Session we agreed on the following Action Points as an action point for the team .
Positives?
• Sprint Planning.
• Each team member helping others.
• Meeting with PIA
• Accessibility Plan
• Meeting with Dev for refinement.
• Focusing on the right things.
What didn’t go well :
• PO sign off.
• Capacity planning
• Not enough time for sprint completion
Actions to take.
• check with PO before closing tickets. ( PO)
• SM For the planners to know the calendar (e.g., stat holidays) (SM)
• Monitoring Capacity (PO, SM)
• PO to get a new Laptop. (PO)
• Factor in time for Ops support (SM)
• Info and sharing with Policy (PO)
These are our action points and have been assign owners, as we
improve as a team we will adapt to these suggestions and check its effects on our next iteration.
Thank you for being part of the journey so far.
We do appreciate any feedback and any other opinion that was not captured.
Festus Odiley
Scrum Master RTR
“ Agile is simple-It is just not easy”
The text was updated successfully, but these errors were encountered: