Skip to content
Gallery
2023 Sprint Retrospective
2023—Sprint 1-2 Feedback
Archive
Share
Explore

Archive

People

⁠
select your name...[[
@Slava Kim
][
@Garry Dik
][
@Alexander Panin
][
@Aaron Hong
][
@Chris Kim
][
@Tilegen Asankulov
][
@Han Schipper
][
@Elchibek Konurbaev
]​[
@Urmat Alybaev
][
@F Young
]]
⁠
⁠
Assignee:
⁠
⁠
Map Coda User to Jira Assignee
⁠
Test Table
⁠
➤ Ticket-specific Feedback (old Jira pack sync - private)
⁠
Sprint #12 ➤ Ticket-specific Feedback (old Jira pack sync - public)
⁠

People:
⁠
⁠

Prep

(
1
⁠
)

⁠
1
⁠
submitted with average sentiment of
3
⁠
⁠
Sentiment
Reflection
Author
Should be closing the previous sprint sooner so we can have a normal 2 week sprint, even if we don’t add new issues.
There are no rows in this table
⁠
Sprint #22
⁠
Sprint #23
⁠

Sprint #24

View of ➤ Ticket-specific Feedback
Status
Issuetype
Issue
Link
Story Points
Corrected Story Points (Sprint #24) (Sprint #24)
If ticket took MORE time, why? (Sprint #24)
Done
7
Task
2
Jira icon
maintenance: use fermium (gallium?) as node version when building the frontend, instead of lts, ANGULAR 13
ET-4241
2
​
​
Jira icon
Maintenance: Upgrade Node to the latest LTS version for the backend
ET-3491
3
​
​
Bug
2
Jira icon
sanity check: 'real' user has campusId on prod-au that does not belong to the school
ET-4865
​
​
​
Jira icon
unsafe replacement in raw Sequelize SQL queries, making ET more vulnerable for SQL injections
ET-4809
​
​
​
Improvement
3
Jira icon
Improve getExportMapping
ET-4925
0
​
​
Jira icon
Sequelize upgrade v6
ET-4807
3
​
​
Jira icon
APP FORMS>SETTINGS> Add Form Name to the screen
ET-4771
0.5
​
​
In Review
1
Improvement
1
Jira icon
Perfomance > Analytics geographic, enquiries, activity requests
ET-4910
​
​
​
⁠
View of ➤ Overall Feedback
Name
Sentiment
What went well? (in general and/or for you)
What improvements should be made?
fast responds from Antony, votes for story points are more correct than last sprint
before start ticket, developer should have correct description what to do and in related confluence
No results from filter
⁠

Sprint #25

Sprint 25 ➤ Ticket-specific Feedback
Status
Issuetype
Issue
Link
Story Points
Corrected Story Points (Sprint #25)
If ticket took MORE time, why? (Sprint #25)
Done
7
Task
2
Jira icon
maintenance: use fermium (gallium?) as node version when building the frontend, instead of lts, ANGULAR 13
ET-4241
2
​
​
Jira icon
Maintenance: Upgrade Node to the latest LTS version for the backend
ET-3491
3
​
​
Bug
2
Jira icon
sanity check: 'real' user has campusId on prod-au that does not belong to the school
ET-4865
​
​
​
Jira icon
unsafe replacement in raw Sequelize SQL queries, making ET more vulnerable for SQL injections
ET-4809
​
​
​
Improvement
3
Jira icon
Improve getExportMapping
ET-4925
0
​
​
Jira icon
Sequelize upgrade v6
ET-4807
3
​
​
Jira icon
APP FORMS>SETTINGS> Add Form Name to the screen
ET-4771
0.5
​
​
In Review
1
Improvement
1
Jira icon
Perfomance > Analytics geographic, enquiries, activity requests
ET-4910
​
​
​
⁠
Sprint 25 ➤ Overall Feedback
Name
Sentiment
What went well? (in general and/or for you)
What improvements should be made?
Sprint #
Discuss of final concept student transfer, we catch out mistake in time
Thinking wider how to implement new feature
25
No results from filter
⁠

Sprint #26

Sprint 26 ➤ Ticket-specific Feedback
Status
Issuetype
Issue
Link
Story Points
Corrected Story Points (Sprint #26)
If ticket took MORE time, why? (Sprint #26)
Map Coda User to Jira Assignee
Assignee
Done
7
Task
2
Jira icon
maintenance: use fermium (gallium?) as node version when building the frontend, instead of lts, ANGULAR 13
ET-4241
2
​
​
Alexander Panin
Jira icon
Maintenance: Upgrade Node to the latest LTS version for the backend
ET-3491
3
​
​
Alexander Panin
Bug
2
Jira icon
sanity check: 'real' user has campusId on prod-au that does not belong to the school
ET-4865
​
​
​
Alexander Panin
Jira icon
unsafe replacement in raw Sequelize SQL queries, making ET more vulnerable for SQL injections
ET-4809
​
​
​
Alexander Panin
Improvement
3
Jira icon
Improve getExportMapping
ET-4925
0
​
​
Alexander Panin
Jira icon
Sequelize upgrade v6
ET-4807
3
​
​
Alexander Panin
Jira icon
APP FORMS>SETTINGS> Add Form Name to the screen
ET-4771
0.5
​
​
Alexander Panin
In Review
1
Improvement
1
Jira icon
Perfomance > Analytics geographic, enquiries, activity requests
ET-4910
​
​
​
Alexander Panin
⁠
Sprint 26 ➤ Overall Feedback
Name
Sentiment
What went well? (in general and/or for you)
What improvements should be made?
Sprint #
Figure out the problem with transfer logic before release
Correct share my thoughts with manager
26
No results from filter
⁠

Sprint #2

Sprint 2 ➤ Ticket-specific Feedback
Status
Issuetype
Issue
Link
Story Points
Corrected Story Points (Sprint #2)
If ticket took MORE time, why? (Sprint #2)
Map Coda User to Jira Assignee
Assignee
Done
7
Task
2
Jira icon
maintenance: use fermium (gallium?) as node version when building the frontend, instead of lts, ANGULAR 13
ET-4241
2
​
​
Alexander Panin
Jira icon
Maintenance: Upgrade Node to the latest LTS version for the backend
ET-3491
3
​
​
Alexander Panin
Bug
2
Jira icon
sanity check: 'real' user has campusId on prod-au that does not belong to the school
ET-4865
​
​
​
Alexander Panin
Jira icon
unsafe replacement in raw Sequelize SQL queries, making ET more vulnerable for SQL injections
ET-4809
​
​
​
Alexander Panin
Improvement
3
Jira icon
Improve getExportMapping
ET-4925
0
​
​
Alexander Panin
Jira icon
Sequelize upgrade v6
ET-4807
3
​
​
Alexander Panin
Jira icon
APP FORMS>SETTINGS> Add Form Name to the screen
ET-4771
0.5
​
​
Alexander Panin
In Review
1
Improvement
1
Jira icon
Perfomance > Analytics geographic, enquiries, activity requests
ET-4910
​
​
​
Alexander Panin
⁠

Sprint 2 ➤ Overall Feedback
Name
Sentiment
What went well? (in general and/or for you)
What improvements should be made?
Sprint #
it’s ok
Prepare better
2
No results from filter
⁠
Aman:
Need to make sure feature branch matches master branch (the branch to which you will merge)
For request changes, better to have Han or Aaron on the ticket to review before merging
Create slack channel to reserve ids for firestore or mysql? (to prevent merge conflicts)
Perhaps discuss implementation approach during backlog refinement before estimating(?)
Add more info in pull request to explain why/how you’re approaching the solution you chose. (follow Aaron’s example which helps explain logic!) [esp useful for bug fixes]
when making a bigger, more fundamental change (not just isolated to one part of code)...should disseminate info to broader group
ET-4278...This should have been labeled as BUG
Elchibek:
ET-4315 (Han) this was more of a research ticket, still ongoing (lower priority)

Urmat/FuMing to look at Implemented/Review columns and prompt individuals to move them forward (to done)
If Antony has feedback not related to ticket, let FuMing/Urmat...
During standup, indicate whether there’s risk of not completing your tickets by end of sprint
ET-4182 (Sasha)
Garry: Bugs do take a lot of time which impacts progress on burndown chart (should we estimate them?) if not, reserve 30% bugger for bugs
Standup: stickers on board, can better visualize (can help one another vs just taking something new from backlog)
Add people from team for pull requests unless good reason to ask someone from other team (based on expertise, domain knowledge)
In smaller teams, get more focused on code reviews with someone other than Han/Aaron reviewing
Smaller teams will help us do more significant stories in a sprint (because of gains from team collaboration)
Han: Remove longer-term tickets (Slava and other tasks [investigative/dev-ops/etc] which take longer) from sprint...can just apply hour estimations for these instead

Sprint #6

Q: When devs don’t have tasks (waiting for previously assigned tasks in review), should the new tickets they pick up be added to the current sprint or just worked on from the backlog?
Sprint #12
⁠


Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.