| 36 | | ^(Describe and link the implementation results here (from the wiki or the repository).)^ |
| | 36 | * After the feedback from Nick and Ludmil, the content of the mail for the mail list is the following: |
| | 37 | {{{ |
| | 38 | With the completion of our fourth iteration comes the summary of what we've accomplished. We launched our second release on schedule and with all of its planned functionalities. We also managed to catch up with our analyses from previous iterations, and have analyzed all tasks through iteration 04 |
| | 39 | |
| | 40 | The new functionalities in the 13 February release are: |
| | 41 | |
| | 42 | |
| | 43 | * Selecting multiple page objects |
| | 44 | * Page object alignment |
| | 45 | * Frame bounding properties; for example margins |
| | 46 | * Basic audio and video support |
| | 47 | * Undo manager: |
| | 48 | * Undo/Redo of the insert frame action now works without exceptions |
| | 49 | * Undo/Redo of the move frame action now works |
| | 50 | * Create book action is now no longer un-doable |
| | 51 | * Undo/Redo of page re-size action now works |
| | 52 | * A book does not re-size with its title change action anymore |
| | 53 | * Selecting the current frame is no longer considered as change |
| | 54 | |
| | 55 | * Undo/Redo text editing in text frames now works |
| | 56 | * The "Redo" item in the edit menu has been fixed to show "Can't redo" when the user cannot redo an action |
| | 57 | |
| | 58 | * Improved Halos and HUDs |
| | 59 | * Initial plug in support |
| | 60 | * Build Server |
| | 61 | |
| | 62 | Additionally, many bugs were fixed. Other things worth mentioning are the branding discussions with Robert Abbot, leading to an upcoming update of the Website look. |
| | 63 | |
| | 64 | The results of our most recent "postmortem", are separated in the three usual categories (What went well; What could be better; and, How to improve): |
| | 65 | |
| | 66 | What went well: |
| | 67 | * Improved overall quality - for most of this iteration we focused on refactoring and improving the existing logic |
| | 68 | * Functionality - the release team managed to implement many new functionalities that covered all requirements for the current release |
| | 69 | * Analyses - we caught up on the analyses for the previous iterations as well as completing them for the next one |
| | 70 | * Discussions - we had many useful discussions concerning Sophie's design and overall ideas for the project, including marketing and Sophie adoption. Videos of these discussions are available here |
| | 71 | * HR and recruitment - we've refined the process for recruiting new team members |
| | 72 | * Improved Site - we refactored our old Website and we believe it is now more attractive and useful |
| | 73 | |
| | 74 | What could be better: |
| | 75 | * Not all tasks in the iteration were completed. |
| | 76 | * Discipline and process - it is improving, but we are striving for even higher standards |
| | 77 | * Better documented discussions - we need to improve the documenting of our discussions; this will help members of our staff who are working remotely people to be even more productive |
| | 78 | |
| | 79 | * More tested tasks - not enough tasks were tested during this iteration |
| | 80 | |
| | 81 | How to improve: |
| | 82 | * Spread global vision - our new team members need to better understand the fundamental concepts behind the project and to have an overall view of the global picture behind Sophie |
| | 83 | * Discuss - our staff members need to constantly ask themselves the questions: "Why?" and "How?" |
| | 84 | * Specification explanations – a more formal specification skeleton will improve consistency |
| | 85 | * Never accept code that is not 100% as it needs to be - we must fix less than perfect code, not to reproduce it |
| | 86 | |
| | 87 | |
| | 88 | Best regards from the Sophie team! |
| | 89 | }}} |
