| 82 | The new functionalities in the 13 February release are: |
| 83 | |
| 84 | |
| 85 | * Selecting multiple page objects |
| 86 | * Page object alignment |
| 87 | * Frame bounding properties; for example margins |
| 88 | * Basic audio and video support |
| 89 | * Undo manager: |
| 90 | * Undo/Redo of the insert frame action now works without exceptions |
| 91 | * Undo/Redo of the move frame action now works |
| 92 | * Create book action is now no longer un-doable |
| 93 | * Undo/Redo of page re-size action now works |
| 94 | * A book does not re-size with its title change action anymore |
| 95 | * Selecting the current frame is no longer considered as change |
| 96 | |
| 97 | * Undo/Redo text editing in text frames now works |
| 98 | * The "Redo" item in the edit menu has been fixed to show "Can't redo" when the user cannot redo an action |
| 99 | |
| 100 | * Improved Halos and HUDs |
| 101 | * Initial plug in support |
| 102 | * Build Server |
| 103 | |
| 104 | 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. |
| 105 | |
| 106 | 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): |
| 107 | |
| 108 | What went well: |
| 109 | * Improved overall quality - for most of this iteration we focused on refactoring and improving the existing logic |
| 110 | * Functionality - the release team managed to implement many new functionalities that covered all requirements for the current release |
| 111 | * Analyses - we caught up on the analyses for the previous iterations as well as completing them for the next one |
| 112 | * 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 |
| 113 | * HR and recruitment - we've refined the process for recruiting new team members |
| 114 | * Improved Site - we refactored our old Website and we believe it is now more attractive and useful |
| 115 | |
| 116 | What could be better: |
| 117 | * Not all tasks in the iteration were completed. |
| 118 | * Discipline and process - it is improving, but we are striving for even higher standards |
| 119 | * 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 |
| 120 | |
| 121 | * More tested tasks - not enough tasks were tested during this iteration |
| 122 | |
| 123 | How to improve: |
| 124 | * 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 |
| 125 | * Discuss - our staff members need to constantly ask themselves the questions: "Why?" and "How?" |
| 126 | * Specification explanations – a more formal specification skeleton will improve consistency |
| 127 | * Never accept code that is not 100% as it needs to be - we must fix less than perfect code, not to reproduce it |
| 128 | |
| 129 | |
| 130 | Best regards from the Sophie team! |
| 131 | }}} |