38 | | Because we didn't manage to finish ITERATION_02 in time and with desired result, we were compelled to schedule additional ITERATION_02b in order to finish all the tasks left from previous iterations and raise even more the quality of the product. |
| 38 | |
| 39 | Because we didn't manage to finish ITERATION_02 in time and with desired result, we were compelled to schedule additional ITERATION_02b in order to finish all the tasks left from previous iterations and raise even more the quality of the product. Because the lack of resources during ITERATION_02, we started and designed most of the task but few tasks were completely finished. On the other hand a lot of new people joined our team for ITERATION_02b and with collective effort we've finished it successfully. Most of the tasks were completely finished and the rest we intend to finish as soon as possible. Some of the things that need to be mentioned are the created overviews (project and development) and our progress in server related tasks (some demo pages are created). |
| 40 | |
| 41 | Results from the retrospection of ITERATION_02b: |
| 42 | What went well: |
| 43 | * There are more people integrated now |
| 44 | * Useful discussions were done |
| 45 | * Most tasks were finished |
| 46 | * Very good productivity at the end of the sprint |
| 47 | * Useful presentations in Sheraton Hotel |
| 48 | What could be better: |
| 49 | * We didn't finish all tasks |
| 50 | * Lack of machines |
| 51 | * The oragnization should be better (too much noise) |
| 52 | * There was no clear description to some tasks |
| 53 | How to improve summary: |
| 54 | * Make more design discussions |
| 55 | * Start hard tasks early |
| 56 | * Focus on PLATFORM_STANDARDS |
| 57 | * No new code last day |
| 58 | * Weekly task boxing |
| 59 | * More information about development tools in the wiki |
| 60 | |
| 61 | Another thing worth mentioning is the new team infrasrtucture. Because now we're more people working on more tasks, we decided to make team split in order to achieve better productivity and quality. Now all team members are |
| 62 | |
| 63 | |
| 64 | |