Sprint 1.31 Applications retrospective
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
Let’s Do!
include in planning estimations
2
Split stories and mark what’s a “blocker” or “important”
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.
Let’s Do!
There are no rows in this table
Sprint Statistics:
What/How do we want to track?
Topic
KPI
Vote
DownVote
Comments
1
Predictability
Plan to done ratio % (completed stories / planned)
3
Productivity
Scope change - # of stories/tasks added in midst of sprint
There are no rows in this table
Stories Statistics
Completed Stories 8(vs 9 last sprint)
8
un Completed Storied: 6(vs 3 last sprint)
6
Completed Bug: 22(vs 16 last sprint)
22
Un Completed bug: 5 (vs 7 last sprint)
5
Complete Stories
UnComplete Stories
Complete Bugs
UnComplete Bugs
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)
3
Scope change - # of stories/tasks added in midst of sprint
There are no rows in this table
Sprint Issues
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.