Content Comparison

Comfortable work load - BS

Ran out of tickets a couple of times - JK

Sprint goals were very clear - JK

Ticket estimations were very long for me - JK

All tickets moved to testing - LR

Work progress reflected on the sprint board - LR

solid focus on the tasks - JM

Could we do team fibonacci estimates? - JK

Review after Oct 3rd

great communication/collab by the team - KK

Ran out of time to test all tickets, was able to test only few tickets- SR
Testing effort could be estimated

Jira tickets could have better description
I should write testing notes on Jira ticket as well - SR

Discuss Kareem, Shruthi, Dean, Lukas how to accomodate testing in the sprint process.
JK suggestion to do deploy with a week delay. Justin. a week later takes your mind of the thing you were working on.

Make sure tickets have a description.

discussion tickets created worked nicely – KK

more time laid out for design before implementation -JM

When laying out funciton.

All tickets seemed to have large estimates - JK

Try to avoid scope creep on tickets, break the down and understand expectations as much as possible - BS

• spread out work better, better estimates so there’s no mad rush on Wed/Thurs

• review estimates to see what was over/under estimated. – KK

Lots of decisions made about new features + improvements to existing features- KM

• Having an end to the discussion + brainstorming phase (items keep growing in size and become too large to complete in 1 sprint) - KK

• For KM: Plan more feedback time on designs

• Agreeing on what will make it into V1 and what will be held off for future versions - KK