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 RTR,
Congratulations on hitting the 6 months cycle on Team RTR.
As we reflected on 6 months on the team and on this project it
was great brainstorming with you how we can get better and
become a high performing team.
During the Retrospective Session we agreed on the following Action Points as a takeaway from our six months as a team .
What went well?
• Director search delivered without a hitch!
• Each team member pulling their weight and helping others.
• Better DOR and grooming
• Team is getting better at understanding each other.
What didn’t go well :
• Not enough design cycles available
• Having tickets ready to groom (design/reqs flushed out etc.)
• Better estimation on story points
• Consistent and timely direction
• Understanding the Domain/ Business flows
• Unclear about certain requirements.
• Architecture/technical frameworks are not clear
Actions to take.
• Watch other teams for innovations we can use.
• regular check-ins with Kaine.
• Learn to deliver in increments of value.
• Make sure requirements are "cooked" before serving them.
• Understanding requirements better before grooming
• Define flow of requirements more clearly Stakeholders -> UX -> tech
These are our takeaways from the 6-month retrospective sessions we had, we will work on these takeaways as we
Improve as a team. Thank you for being part of the journey so far.
Hi Team RTR,
Congratulations on hitting the 6 months cycle on Team RTR.
As we reflected on 6 months on the team and on this project it
was great brainstorming with you how we can get better and
become a high performing team.
Mural link
RTR 6 MONTHS RETRO 19.1 • CITZ – ServiceBC – BCROS (mural.co)
Attendance
Absent
During the Retrospective Session we agreed on the following Action Points as a takeaway from our six months as a team .
What went well?
• Director search delivered without a hitch!
• Each team member pulling their weight and helping others.
• Better DOR and grooming
• Team is getting better at understanding each other.
What didn’t go well :
• Not enough design cycles available
• Having tickets ready to groom (design/reqs flushed out etc.)
• Better estimation on story points
• Consistent and timely direction
• Understanding the Domain/ Business flows
• Unclear about certain requirements.
• Architecture/technical frameworks are not clear
Actions to take.
• Watch other teams for innovations we can use.
• regular check-ins with Kaine.
• Learn to deliver in increments of value.
• Make sure requirements are "cooked" before serving them.
• Understanding requirements better before grooming
• Define flow of requirements more clearly Stakeholders -> UX -> tech
These are our takeaways from the 6-month retrospective sessions we had, we will work on these takeaways as we
Improve as a team. Thank you for being part of the journey so far.
Kind Regards
Festus Odiley
Scrum Master RTR
“ Agile is simple-It is just not easy”
@trishreimer @Kaineatthelab @lmcclung
The text was updated successfully, but these errors were encountered: