Skip to content
Sprint Retro
April 28 2023
May 12 2023
May 26 2023
June 12 2023
June 26 2023
Share
Explore

May 12 2023

​ERP-23-Q2-S1
⁠

Team

⁠
@Don Boone
⁠
⁠
@krupali patel
⁠
Zahid

Sprint Goal

Complete the Landfill module- not done

Jira details

⁠
Sprint tickets
⁠
⁠

Sentiment

Better than last sprint.
Not outside influence, but more of our mistakes caught up.
Code review still needs to be implemented
Code review is a must.
Dont allow new stories to come in.
⁠
⁠
⁠

Peer review not now, at a later stage perhaps.
Productivity dropped for Zahid
Meetings are a factor
Bug fixes
Miscellaneous tasks

Team Highs and Lows
Add Your Highs/Lows
⁠
Clear Dummy Data
⁠
⁠

Team Member
Highs
Lows
Critical Bug fixes ftw.
Zahid and Krupali are doing great jobs, being really proactive.
Sprints goals are still getting missed .but still an amazingly productive sprint.
HOG import story, Docs were helpful in understanding the story.
Sprints goals are still getting missed .but still an amazingly productive sprint.
St Francis go live . Getting to know people were getting paid.
Ontario demo went really well, logic seemed to be correct
Felt a bit disorganized . Need to create stories
Working with Don to clarify on the roadmap was a good exsercise.
Coordinating with Wendy
​
​
There are no rows in this table
⁠

Start, Stop, and Continue?
Add Your Feedback
⁠
Clear Dummy Data
⁠
⁠

What should we...
Feedback
Raised By
Turn into Action Item
Notes
Got Work done, debatable if it led to busines outcome
Turn to AI
​
Create a process for implementation team reaching out to the Dev team.
Turn to AI
​
Estimating velocity of a sprint
Turn to AI
​
Making the database live without ensuring Data is ready.
Turn to AI
​
First QA passed story.
Turn to AI
​
Clearer Requirements- Feature tickets
Turn to AI
​
Make time for Code Review
Turn to AI
​
Keep the sprint goal in mind and work towards competing the tasks in the sprint.
Turn to AI
​
Perform more rigorous testing.
Turn to AI
​
Estimating story points
Turn to AI
​
Ask Implementation to include the product manager as well
Turn to AI
​
Regression testing needs to be after release
Turn to AI
Don we need to have a QA for regression.
QA needs to be part of Sprint
Turn to AI
​
Should Unit testing be a part of our build release ?
Turn to AI
​
Find out the downstream stakeholders.
Turn to AI
​
Taking direct request without going through the manager
Turn to AI
​
⁠


Action Items
Add Manual Action Items
⁠
Clear Dummy Data
⁠
⁠

Action Item
Select Owner
Make time for Code Review
Keep the sprint goal in mind and work towards competing the tasks in the sprint.
Create a process for implementation team reaching out to the Dev team.
Taking direct request without going through the manager
Estimating story points
Estimating velocity of a sprint
Ask Implementation to include the product manager as well
Regression testing needs to be after release
Should Unit testing be a part of our build release ?
There are no rows in this table
⁠


Team
Sprint Goal
Jira details
Sentiment
Team Highs and Lows Add Your Highs/Lows Clear Dummy Data
Start, Stop, and Continue? Add Your Feedback Clear Dummy Data
Action Items Add Manual Action Items Clear Dummy Data
Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.