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

May 26 2023

​ERP-23-Q2-S1
⁠

Team

⁠
@Don Boone
⁠
⁠
@krupali patel
⁠
Zahid
Yasin

Sprint Goal

Complete the Landfill module- Not done
Complete the testing of Ontario module- Not done

Jira details

⁠
Sprint tickets
⁠
⁠

Sentiment

Stories were being worked on multiple time .
Demoralizing
Slowed down
We have implemented steps to mitigate this next sprint.
Allocate for QA rework.
I should have been more involved in the sprint - Pankaj.
Code review should be done for next sprint.
Code review still needs to be implemented
Code review is a must.
Dont allow new stories to come in.
Productivity dropped for Zahid
Panic moment, no isolation.

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

Team Member
Highs
Lows
Working together with Zahid and Kurpali, we managed to clean up a lot of stuff including HOG code.
At one point we felt we were slipping .
Marking the HOG story was a definite high.
Landfill completioet
Expecations setting with sales and implmenation
sometimes work felt hazy with requirements come from different stakeholders.
Working together with Don, we managed to clean up a lot of stuff.
Learning was ther
Mordern data conversion was not completely done .
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
Create a process for implementation team reaching out to the Dev team.
Turn to AI
​
Making the database live without ensuring Data is ready.
Turn to AI
​
QA needs to be part of Sprint
Turn to AI
​
First QA passed story.
Turn to AI
​
Perform more rigorous testing.
Turn to AI
​
Make time for Code Review
Turn to AI
​
Ask Implementation to include the product manager as well
Turn to AI
​
Taking direct request without going through the manager.
Turn to AI
​
Estimating velocity of a sprint
Turn to AI
​
Clearer Requirements- Feature tickets
Turn to AI
​
Keep the sprint goal in mind and work towards competing the tasks in the sprint.
Turn to AI
​
Estimating story points
Turn to AI
​
Regression testing needs to be after release
Turn to AI
​
Get stories done, and get it done right
Turn to AI
​
Got Work done, debatable if it led to busines outcome
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.