Share
Explore

Sprint 1.31 Applications retrospective

Lets's Reflect on our last sprint and brainstorm ways to improve your team's performance.
What did we propose last Retro?
0
Done
Experiment
Author
Vote
Comments
1
Count bugs and tasks in the planning
DD
5
2
Try a sprint without subtasks (only stories, tasks and bugs)
DD
3
3
Practice Technical Design
LS
2
4
Document ticket dependencies and review them in the end of the planning
GB
2
5
Leave a day after all stories and bug fixes of stories are done for qaing
MB
2
There are no rows in this table

Sprint Statistics:

Start Date: 05 April, 2021
Finish Date: 26 April, 2021
FE: 8.4
BE: 9.45


Completed Stories
15
(vs 9 last sprint)

un Completed Storied:
6
(vs 7 last sprint)

Completed Bug:
19
(vs 13 last sprint)

Un Completed bug:
6
(vs 19 last sprint)


What/How do we want to track?

How much in % did we deliver what we planned?
How accurate are we in estimations?
What’s our velocity regarding bugs and “quality of life” tasks?
Personal tracking - how much did we actually spend on X, Y, Z?
Bugs
How many bugs were created after the planning? how much time did we spend on them?



Complete Stories
4

UnComplete Stories
4

Complete Bugs
4

UnComplete Bugs
4

Retrospective

What did we do well?
Add things you think we did well and should continue doing
Clear template

Topic
Who
Like
1
We’ve achieved our sprint goals
IN
5
2
Released version 1.31 on time
SB
4
3
qa-ux collaboration
MB
2
4
Good Communication during testing → Comments for QA are helpful → Meeting in office for closures
GB
3
5
(More or less) accurate time est. on tasks
HS
6
Good distribution of tasks between components
HS
2
7
sort of tech design for backend tasks
GB
1
There are no rows in this table


What should we have done better?

Add things we didn't do so well or didn't do at all and we should reflect on to try and correct them
.
Clear template

Topic
Who
Agree
1
need to implement the action items from last retro
MB
9
2
Close feature design before delivering the feature to QA
SB
6
3
We need one more day to perform regression testing
SB
4
4
CR bottleneck
GB
3
5
Estimations were not accurate enough
SR
3
6
some stories don’t have a clear “end condition”
GB
2
7
Missed edges on stories (i.e. name duplication in external dashboards, auto-refresh when excluding runs)
HS
2
8
No time for Small UX Items and Bugs backlog
IN
1
9
No feature review before QA or sync with all product
IN
1
10
no enough models to test
GB
1
11
no enough time for tech debt
GB
1
12
hard to track pipeline dependencies
GB
There are no rows in this table

Experiments

Let’
s choose together
two
things we want to do differently next sprint
Clear template

Add Idea
Done
Idea
Author
Vote
DownVote
Comments
1
Consider ux qa time in estimation of features that require it
SR
6
Let’s Do!
include in planning estimations
2
Split stories and mark what’s a “blocker” or “important”
SR
4
Let’s Do!
1. Split Stories + Prioritize
2. Aim for 70% commitment of Plan
3
#ux-qa channel, communicate what is ready asap
3
Let’s Do!
4
Create a “Pre-Prod” lookalike environment so we can test on prod-like data instead of relying on DEV
GB
3
Let’s check if feasible
5
Estimations vs Actual and Buffer “pressure”: 1) Adhere to pre-planning and discovery 2) Adhere to 70% stories commitment out of the total stories, so we can mitigate the 30% risk of estimations.
IN
2
6
Arrive to office later, and take Daily’s from home and save time on traffic
LS
2
7
Create “Technical Docs” for peer review - mostly BE / architecture
GB
2
8
Postpone release to Monday morning so we can have more time for regression testing.
SB
2
Let’s Do!
9
“Break the CR wall between FE and BE” - to mitigate CR bottleneck, maybe for specific components?
GB
2
2
There are no rows in this table


Sprint Issues
4


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.