Fill in retro details in the table below. Type /date to quickly add the date and @mention participants to help them find the page.
|
Developer | Estimated Story Points | Actual Achieved |
7 | 10 | |
4 | 8 | |
2 | 5 | |
8 | 10 | |
Kelly Song | 8 | 8 |
2 | 2 | |
0 | 0 |
Notes:
Team felt full, (not overbooked) (average 4 of 1-5 scale where 5 is overbooked, 1 is too little)
Team is looking for steady state of 3, 3.5.
Xa says one of his tickets probably needed to be a larger story point estimate.
Nick/John: bug triage process on https://sagebionetworks.jira.com/browse/PLFM-6986 and https://sagebionetworks.jira.com/browse/PLFM-6999
Nick did the right thing in PLFM-6986, because he could timebox the solution. But if it is too large a fix, or if it is outside the expertise, to bring it to the team.
For PLFM-6972: Make sure that the accounting is done in Jira when a bug is triaged as it was (we should have set it to Ready For Team and put it to the top of the backlog for John to pick up.)
Add your Start doing, Stop doing, and Keep doing items to the table below. We'll use these to talk about how we can improve our process going forward. |
Start doing | Stop doing | Keep doing |
---|---|---|
|
Add 1-2 follow-up action items to help the team apply what they learned in the retro: