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 take from last retro?

Idea
Author
Vote
Comments
1
Consider ux qa time in estimation of features that require it
SR
Let’s Do!
include in planning estimations
2
Split stories and mark what’s a “blocker” or “important”
SR
Let’s Do!
1. Split Stories + Prioritize
2. Aim for 70% commitment of Plan
3
#ux-qa channel, communicate what is ready asap
Let’s Do!
4
Postpone release to Monday morning so we can have more time for regression testing.
SB
Let’s Do!
There are no rows in this table







Sprint Statistics:

Start Date: 27 April, 2021
Finish Date: 16 May, 2021
FE: 11.2
BE: 11.9



What/How do we want to track?

Value
: Are we meeting the customer’s needs? are we meeting the sprint goals?
Predictability
: The ability to plan and deliver
Productivity
: Getting more done in the same time or with the same resources
Quality
: A product free of defects and issues
Stability
: The organization can maintain this pace indefinitely
Growth
: Is the organization growing and learning?
Health & Satisfaction
Topic
KPI
Vote
DownVote
Comments
1
Predictability
Plan to done ratio % (completed stories / planned)
2
Productivity
Burndown velocity -
3
Productivity
Scope change - # of stories/tasks added in midst of sprint
There are no rows in this table



How much in % did we deliver what we planned?
Stories: 10/10
Analytics - infrastructure
Use model SPIKE
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?


Stories Statistics

Completed Stories
8
(vs 9 last sprint)

un Completed Storied:
6
(vs 3 last sprint)

Completed Bug:
22
(vs 16 last sprint)

Un Completed bug:
5
(vs 7 last sprint)


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
Column 4
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
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
KPI
Vote
DownVote
Comments
1
Plan to done ratio % (completed stories / planned)
2
Burndown velocity -
3
Scope change - # of stories/tasks added in midst of sprint
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.