| | 8 | |
| | 9 | == Lessons Learnt from evaluation session of Sprint 2 on Mar. 3rd == |
| | 10 | |
| | 11 | * Sprint planning should be done more thoroughly, really think the stories through. Plan the stories in multiple iterations. |
| | 12 | * Tasks should be small and precise so you see progress. |
| | 13 | * We should have research stories and tasks (e.g.: investigate error handling). |
| | 14 | * Be careful with incoming tasks. |
| | 15 | * What to do with new tasks that pop up during the Sprint: add them to the board, including story point estimate, so they become visible. |
| | 16 | * Stories that cannot be broken down beforehand: give them number of story points you are willing to spend on them, then start designing and then break them down as it becomes clear how to do this. |
| | 17 | * Have a clear picture of the prerequisites of a task before you start on it. |
| | 18 | * Have sessions to get feedback on designs people made. |
| | 19 | * Have a history of how tasks moved: maybe write it down on the task post-it. |
| | 20 | * Keep Sprint statistics in spreadsheet to learn from. |
| | 21 | * Stories were too big. |
| | 22 | * 3 weeks may be too short... Suggestion: a month. Or sometimes merge two sprints. |
| | 23 | * Demo took to long. At least insert a break. Don't show off products, demo only what's been done. Install a parking lot for discussion items. |
| | 24 | * Don't discuss new plans during demo. Do it a day later, so you can think about them. Or do the demos in the morning and brainstorm in the afternoon. |
| | 25 | * Morris's role as acceptance guy wasn't properly used. When a task is considered done, ask him to try it, in life or through e-mail. Only when he accepts it, it's allowed to move to 'Done'. He will implement a daily testing slot. Just send him an e-mail and he will test it within 24 hrs (otherwise you may consider the task accepted). |
| | 26 | * Joeri feels he had tasks that were of no importance to the team. Actually, every task is a group effort. We should all adopt this mindset. |
| | 27 | * Joeri works on two locations which makes scrumming hard. We have to find practical solutions for his: do sprint planning at Zernike, use Skype for scrum sessions, have the scrum sessions really early so he can attend them every day. |
| | 28 | * People who work for other customers (LifeLines, GBIC) feel like that's interfering with our scrum. That shouldn't be the case, the scrums should be aligned. |
| | 29 | * Merge the Tuesday and Thursday LifeLines scrums better with ours, so also non-LL people can have a say on those days. |
